rw-r-r- 1 root root 38221312 kernel_factory.tarĭrwx- 3 root root 4096 Aug 1 18:11 this is just a SD card going bad? I’d think if the card was going bad I would see issues during operation versus just across a reboot? However, I ran “badblocks” on the SD card without errors: badblocks -vn /dev/sdfĬhecking for bad blocks in non-destructive read-write mode rw-r-r- 1 root root 38221312 kernel_current.tar Volumio_data: clean, 15597/5591264 files, 368675/7495361 after this it appears that the 2nd partition has gotten clobbered – most of the files are missing. Setting free blocks count to 7126686 (was 7315865) Setting free inodes count to 5575667 (was 5591253) Volumio: ***** FILE SYSTEM WAS MODIFIED ***** Pass 5: Checking group summary information Setting filetype for entry '.' in ? (2) to 2. Pass 1: Checking inodes, blocks, and sizesĭirectory inode 2, block #0, offset 0: directory corrupted Volumio contains a file system with errors, check forced. I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes Moving the card over to debian, it seems that the filesystems didn’t have a good time across that reboot: fdisk /dev/sdfĬhanges will remain in memory only, until you decide to write them.īe careful before using the write command.ĭisk /dev/sdf: 30.9 GiB, 33201061888 bytes, 64845824 sectors I upgraded from 2.443 to 2.444, and after the reboot – nothing: no video output, no networking - no blinky green LED light on the rpi3b+Īfter rebuilding my configuration, from the command line: I clicked on “upgrade” earlier today, and it hasn’t gone well since then!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |