My array shows all online drives, but does not see any filesystems.  I tried to switch to a different SAS controller, and I fear everything is gone.  Which is sad.  Is there a way I can scan for a filesystem, or at least my files?

ower emhttpd: shcmd (30): /sbin/btrfs device scan
Feb  1 18:47:50 Tower root: Scanning for Btrfs filesystems
Feb  1 18:47:50 Tower emhttpd: shcmd (31): mkdir -p /mnt/disk1
Feb  1 18:47:50 Tower emhttpd: /mnt/disk1 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (32): umount /mnt/disk1
Feb  1 18:47:50 Tower root: umount: /mnt/disk1: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (32): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (33): rmdir /mnt/disk1
Feb  1 18:47:50 Tower emhttpd: shcmd (34): mkdir -p /mnt/disk2
Feb  1 18:47:50 Tower emhttpd: /mnt/disk2 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (35): umount /mnt/disk2
Feb  1 18:47:50 Tower root: umount: /mnt/disk2: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (35): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (36): rmdir /mnt/disk2
Feb  1 18:47:50 Tower emhttpd: shcmd (37): mkdir -p /mnt/disk3
Feb  1 18:47:50 Tower emhttpd: /mnt/disk3 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (38): umount /mnt/disk3
Feb  1 18:47:50 Tower root: umount: /mnt/disk3: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (38): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (39): rmdir /mnt/disk3
Feb  1 18:47:50 Tower emhttpd: shcmd (40): mkdir -p /mnt/disk4
Feb  1 18:47:50 Tower emhttpd: /mnt/disk4 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (41): umount /mnt/disk4
Feb  1 18:47:50 Tower root: umount: /mnt/disk4: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (41): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (42): rmdir /mnt/disk4
Feb  1 18:47:50 Tower emhttpd: shcmd (43): mkdir -p /mnt/disk5
Feb  1 18:47:50 Tower emhttpd: /mnt/disk5 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (44): umount /mnt/disk5
Feb  1 18:47:50 Tower root: umount: /mnt/disk5: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (44): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (45): rmdir /mnt/disk5
Feb  1 18:47:50 Tower emhttpd: shcmd (46): mkdir -p /mnt/disk6
Feb  1 18:47:50 Tower emhttpd: /mnt/disk6 mount error: Unsupported partition layout
Feb  1 18:47:50 Tower emhttpd: shcmd (47): umount /mnt/disk6
Feb  1 18:47:50 Tower root: umount: /mnt/disk6: not mounted.
Feb  1 18:47:50 Tower emhttpd: shcmd (47): exit status: 32
Feb  1 18:47:50 Tower emhttpd: shcmd (48): rmdir /mnt/disk6
Feb  1 18:47:50 Tower emhttpd: shcmd (49): sync
Feb  1 18:47:50 Tower emhttpd: shcmd (50): mkdir /mnt/user
Feb  1 18:47:50 Tower emhttpd: shcmd (51): /usr/local/sbin/shfs /mnt/user -disks 126 -o noatime,allow_other -o remember=0  |& logger
Feb  1 18:47:50 Tower shfs: use_ino: 1
Feb  1 18:47:50 Tower shfs: direct_io: 0

Post diagnostics zip file.

 

I suspect, as long as parity is valid, that you could pull 1 disk at a time to force Unraid to emulate the drive and it would mount. If that's the case, you could rebuild the drives one at a time.

 

However... I wouldn't risk doing that without knowing more about what happened, and what state the array is in right now.

 

How is your backup situation?

it will start the array, and no mountable filesystem exists.  no drive has any files.  backups.... well, I suppose probably, mostly.  yeah.  still would rather get this back running.

This can happen when changing from RAID controller to HBA (or vice versa), since partitions are outside parity it's usually possible to rebuild the disks one at a time (or two if you have dual parity) on top so Unraid recreates the partition, test first by unassigning one of the data disks, then start the array, if the emulated disks mounts correctly you can rebuild on top, when rebuild is done repeat for the other disks.