6.1.9,  unraid.

 

I have 10 drives showing mountable, 10 drives suddenly showing not mountable.

 

I had 1 drive show up bad yesterday so I rebooted the box to check if it was a false positive until I could get a replacement.

 

Machine came up.  BIOS missing, had to rebuild using backup bios.

 

UnRaid comes up, all the drive configurations are missing.

 

I bring up the drives (with no parity) and confirm that 10 are working properly, the other 10 are showing unmountable

 

Whats the best way to confirm the other drives are still good?  I was thinking of manually mounting them in /mnt temporarly.

 

I'm still trying to figure out a cause.  the 10 drives that are down may be connected via an external SATA card so it could be a case of the BIOS not loading the card right after a reset, still checking.

 

 

Jul 11 19:42:14 Tower kernel: REISERFS warning (device md1): sh-2011 read_super_block: can't find a reiserfs filesystem on (dev md1, block 16, size 4096)

Jul 11 19:42:14 Tower kernel: REISERFS warning (device md1): sh-2021 reiserfs_fill_super: can not find reiserfs on md1

Jul 11 19:42:14 Tower emhttp: shcmd: shcmd (48): exit status: 32

Jul 11 19:42:14 Tower emhttp: mount error: No file system (32)

Jul 11 19:42:14 Tower emhttp: shcmd (49): rmdir /mnt/disk1

Jul 11 19:42:14 Tower emhttp: shcmd (50): mkdir -p /mnt/disk2

Jul 11 19:42:14 Tower emhttp: shcmd (51): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

Jul 11 19:42:14 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal

Jul 11 19:42:14 Tower kernel: REISERFS (device md2): using ordered data mode

Jul 11 19:42:14 Tower kernel: reiserfs: using flush barriers

Jul 11 19:42:14 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jul 11 19:42:14 Tower kernel: REISERFS (device md2): checking transaction log (md2)

Jul 11 19:42:14 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

Jul 11 19:42:15 Tower emhttp: shcmd (52): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

Jul 11 19:42:15 Tower emhttp: reiserfs: resizing /mnt/disk2

Jul 11 19:42:15 Tower emhttp: shcmd (53): mkdir -p /mnt/disk3

Jul 11 19:42:15 Tower emhttp: shcmd (54): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Jul 11 19:42:15 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

Jul 11 19:42:15 Tower kernel: REISERFS (device md3): using ordered data mode

Jul 11 19:42:15 Tower kernel: reiserfs: using flush barriers

Jul 11 19:42:15 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

Jul 11 19:42:15 Tower kernel: REISERFS (device md3): checking transaction log (md3)

Jul 11 19:42:15 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

Jul 11 19:42:15 Tower emhttp: shcmd (55): set -o pipefail ; mount -t reiserfs -o remount,user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Jul 11 19:42:15 Tower emhttp: reiserfs: resizing /mnt/disk3

Jul 11 19:42:15 Tower emhttp: shcmd (56): mkdir -p /mnt/disk4

Jul 11 19:42:15 Tower emhttp: shcmd (57): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4 |& logger

Jul 11 19:42:15 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md4,

Jul 11 19:42:15 Tower logger:        missing codepage or helper program, or other error

Jul 11 19:42:15 Tower logger:        In some cases useful info is found in syslog - try

Jul 11 19:42:15 Tower logger:        dmesg | tail  or so

Jul 11 19:42:15 Tower logger:

Jul 11 19:42:15 Tower emhttp: shcmd: shcmd (57): exit status: 32

Jul 11 19:42:15 Tower emhttp: mount error: No file system (32)

Jul 11 19:42:15 Tower emhttp: shcmd (58): rmdir /mnt/disk4

Jul 11 19:42:15 Tower kernel: REISERFS warning (device md4): sh-2021 reiserfs_fill_super: can not find reiserfs on md4

Jul 11 19:42:15 Tower emhttp: shcmd (59): mkdir -p /mnt/disk5

Jul 11 19:42:15 Tower emhttp: shcmd (60): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5 |& logger

Jul 11 19:42:15 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5,

Jul 11 19:42:15 Tower logger:        missing codepage or helper program, or other error

Jul 11 19:42:15 Tower logger:        In some cases useful info is found in syslog - try

Jul 11 19:42:15 Tower logger:        dmesg | tail  or so

 

 

attaching diagnostics

tower-diagnostics-20160712-0609.zip

I don't have time for a full analysis at the moment, but just from what's above, I suspect that Disk 1 and Disk 4 don't have the correct file format set.  If you click on the drive (its clickable link) on the Main page, you'll get its settings and SMART info.  Make sure the file format is set to the correct file system, as those 2 are currently set to ReiserFS and it isn't finding a ReiserFS on them.  Make sure all of the drives are set correctly.

 

When more than one drive appears to fail simultaneously, the drives themselves are almost always perfectly fine, and it's some component common to them that has failed (or disconnected or crashed).  Make sure all connections (card and cable, data and power) are tight, then boot again.  Also, make sure your power supply is sufficient for all your cards and drives.

The drives were mis-labeled for type, and it appears a a single ext-sata cord was loose from some long term vibration.