Hi there,
I clicked on “upgrade” earlier today, and it hasn’t gone well since then!
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+
So, I rebuild.
After rebuilding my configuration, from the command line:
sync
sync
reboot
and here’s the result:
Moving the card over to debian, it seems that the filesystems didn’t have a good time across that reboot:
root@debian:~# fdisk /dev/sdf
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdf: 30.9 GiB, 33201061888 bytes, 64845824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0fb2c738
Device Boot Start End Sectors Size Id Type
/dev/sdf1 * 1 125000 125000 61M c W95 FAT32 (LBA)
/dev/sdf2 125001 4882812 4757812 2.3G 83 Linux
/dev/sdf3 4882813 64845703 59962891 28.6G 83 Linux
Command (m for help): q
root@debian:~# fsck -y /dev/sdf2
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
volumio: recovering journal
volumio contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? yes
Missing '.' in directory inode 2.
Fix? yes
Setting filetype for entry '.' in ??? (2) to 2.
Missing '..' in directory inode 2.
Fix? yes
Setting filetype for entry '..' in ??? (2) to 2.
Pass 3: Checking directory connectivity
'..' in / (2) is <The NULL inode> (0), should be / (2).
Fix? yes
Unconnected directory inode 11 (/???)
Connect to /lost+found? yes
/lost+found not found. Create? yes
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Inode 11 ref count is 3, should be 2. Fix? yes
Unattached inode 12
Connect to /lost+found? yes
Inode 12 ref count is 2, should be 1. Fix? yes
Unattached inode 13
Connect to /lost+found? yes
Inode 13 ref count is 2, should be 1. Fix? yes
Unattached inode 14
Connect to /lost+found? yes
Inode 14 ref count is 2, should be 1. Fix? yes
Unattached inode 15
Connect to /lost+found? yes
Inode 15 ref count is 2, should be 1. Fix? yes
Pass 5: Checking group summary information
Inode bitmap differences: +(1--15)
Fix? yes
volumio: ***** FILE SYSTEM WAS MODIFIED *****
volumio: 16/148960 files (12.5% non-contiguous), 164890/594726 blocks
root@debian:~# fsck -y /dev/sdf3
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
volumio_data: recovering journal
Setting free inodes count to 5575667 (was 5591253)
Setting free blocks count to 7126686 (was 7315865)
volumio_data: clean, 15597/5591264 files, 368675/7495361 blocks
root@debian:~#
Unfortunately, after this it appears that the 2nd partition has gotten clobbered – most of the files are missing.
root@debian:/media/swinokur/volumio# ls -l
total 74660
-rw-r--r-- 1 root root 38221312 Dec 31 1969 kernel_current.tar
-rw-r--r-- 1 root root 38221312 Dec 31 1969 kernel_factory.tar
drwx------ 3 root root 4096 Aug 1 18:11 lost+found
root@debian:/media/swinokur/volumio#
Maybe 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:
root@debian:~# badblocks -vn /dev/sdf
Checking for bad blocks in non-destructive read-write mode
From block 0 to 32422911
Testing with random pattern: Pass completed, 0 bad blocks found. (0/0/0 errors)
root@debian:~#