My tales of woe are neverending, it seems. I am hoping my fellow Plexers can help me, despite this not being a plex-specific issue.
I rebooted my Ubuntu server today, and it failed to re-appear. After connecting a keyboard and monitor I discovered it timed out when mounting my Raid5 array.
I excluded the array from fstab and was able to boot.
When attempting to mount the array I get a bad superblock message.
froberg@master:~$ sudo fsck /dev/md0
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext4: Invalid argument while trying to open /dev/md0
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
I am dangerously afraid right now. I read something about pulling a 'good' superblock from one of the drives, but the guides I found didn't seem to be relevant to my setup.
Anyone feel like saving a life today?
Array is comprised of 4x6TB drives.
Disk /dev/sda: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 157B9049-B0C8-4CF7-B84D-B21842012564
Device Start End Sectors Size Type
/dev/sda1 2048 11721043967 11721041920 5.5T Linux filesystem
Disk /dev/sdb: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5C2275AA-8D0A-4579-9AD5-15C5B9C1D240
Device Start End Sectors Size Type
/dev/sdb1 2048 11721043967 11721041920 5.5T Linux filesystem
Disk /dev/sdc: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 21DD4D37-DEF9-499A-AD23-80275F8F1404
Device Start End Sectors Size Type
/dev/sdc1 2048 11721043967 11721041920 5.5T Linux filesystem
Disk /dev/sdd: 119.2 GiB, 128035676160 bytes, 250069680 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: gpt
Disk identifier: E5044C97-D8B3-4E67-A032-FFFA9ABFD9BB
Device Start End Sectors Size Type
/dev/sdd1 2048 1050623 1048576 512M EFI System
/dev/sdd2 1050624 1550335 499712 244M Linux filesystem
/dev/sdd3 1550336 250068991 248518656 118.5G Linux LVM
Disk /dev/sde: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 090B881C-090F-419B-9417-F901BEF5DAD2
sdd being my system drive.
I only updated Ubuntu and rebooted, as I've done countless times before. I really don't want to poke around too much for fear of ruining what may be a simple fix.