January 17, 20224 yr I was just setting up my server after it was off for a week, and this is what I see now. I was in the process up updating some containers when my daughter, 18 months old, walked over and hit the power button on the UPS. I don't even know where to start on troubleshooting this. I have read through a bunch of other posts and nothing seems to fit my situation. tower-diagnostics-20220117-1623.zip
January 17, 20224 yr Community Expert Looks like the sort of problems people have when they try to use RAID controllers with Unraid. I think the solution is to get rid of the RAID controller, figure out your disks assignments without that controller in the system, then see if you can rebuild each data disk one at a time from parity. Wait for additional opinions since I don't really have personal experience with this situation.
January 17, 20224 yr Author Unfortunately this won't really work for me. I have SAS drives and nothing in the retail space really uses SAS. I can keep troubleshooting that piece though.
January 17, 20224 yr Community Expert Lots of people using SAS drives with Unraid. It is the RAID controller you need to get rid of, or at least flash it to IT mode.
January 18, 20224 yr Author I swapped out my Adaptec 71605 with an 8 port SATA card as and as I suspected I am no longer able to see my SAS drives. The controller is listed on the compatible list. https://wiki.unraid.net/Hardware_Compatibility I moved recently, and lost my second parity drive to failure when I booted everything back up. I also just moved it out of my server rack into a tower case. In doing so I lost the capability to use a backplane. I will go back through and test every setting on the controller and see if I can get it to work again.
January 18, 20224 yr Community Expert 1 hour ago, corgiguy said: the compatible list Quote Please use this page with caution! It was updated much more in the days of v4 and v5, has seen little updating since the advent of v6. That means many hardware recommendations may be obsolete. See the link I already gave above
January 18, 20224 yr Community Expert 4 hours ago, trurl said: Wait for additional opinions since I don't really have personal experience with this situation. Maybe @JorgeB will take a look at this thread in the morning
January 18, 20224 yr Author 5 minutes ago, trurl said: See the link I already gave above Well I ordered a 24 port LSI card. It will be here Wednesday. I will be extremely sad if I can’t salvage any of the data. This NAS has 15 years of data stored on it.
January 18, 20224 yr Community Expert Recently one user with the same controller found it overwrote the first few sectors of every disk destroying the data after a firmware update, did you make any?
January 18, 20224 yr Community Expert Still likely the reason for the problem, depending on what/how much of the partitions was damaged data might still be recoverable, you can try this, assuming parity is still valid: -Stop the array -Unassign one of the data disks -Start the array -Post new diags Unraid will recreate the partition, depending on what is missing/damaged on the other disks it might work or not, if the emulated disk mounts and contents look correct you can just rebuild the disk, then repeat for the other ones, one at a time.
January 18, 20224 yr Author 2 hours ago, JorgeB said: Still likely the reason for the problem, depending on what/how much of the partitions was damaged data might still be recoverable, you can try this, assuming parity is still valid: -Stop the array -Unassign one of the data disks -Start the array -Post new diags Unraid will recreate the partition, depending on what is missing/damaged on the other disks it might work or not, if the emulated disk mounts and contents look correct you can just rebuild the disk, then repeat for the other ones, one at a time. Here are the new Diags. tower-diagnostics-20220118-0823.zip Additionally it looks like it may still have all the data there, but I will need to rebuild each disk one at a time?
January 18, 20224 yr Community Expert Diags are before array start with the emulated disk, so can't see if a valid filesystem was detected, try checking filesystem on that disk and/or post new diags, I mentioned rebuilding only if the emulated disk was mounting, not much point in rebuilding if the filesystem can't be fixed.
January 18, 20224 yr Author There was no filesystem found on the disk. I checked with Unassigned devises and was unable to mount the disk. All it kept saying was format.
January 18, 20224 yr Community Expert Check filesystem on that disk, primary superblock could be gone but it might find a backup one, as long as just the first few sectors were wiped.
January 20, 20224 yr Author Ok so I finished running the repair and all the disks show this: They all seem to be "repaired". But I am still having issues getting them to show up in the array. I am guessing the Array is working and good because I can remove a disk and rebuild it no problem, but I would like to get all of the working in one fell swoop vs rebuilding each disk one by one. As you can see I rebuilt two of them and they seem to be fine, this screenshot was taken in maintenance mode. Any ideas from here? tower-diagnostics-20220120-1405.zip
January 20, 20224 yr Community Expert You checked them with the no modify flag (-n) so the check only found the problems it didn't fix them.
January 20, 20224 yr Author I repaired all of them, then rebooted, the. Took this screenshot moments ago. I used the info in the linked article to repair them from the console.
January 20, 20224 yr Community Expert According to diags disks 1 and 2 mounted, or did you format them? Screenshot is maybe in maintenance mode? Jan 20 13:57:00 Tower emhttpd: shcmd (6033): xfs_growfs /mnt/disk1 Jan 20 13:57:00 Tower kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Jan 20 13:57:00 Tower root: meta-data=/dev/md1 isize=512 agcount=4, agsize=244188659 blks Jan 20 13:57:00 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 20 13:57:00 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 20 13:57:00 Tower root: = reflink=1 Jan 20 13:57:00 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 20 13:57:00 Tower root: = sunit=0 swidth=0 blks Jan 20 13:57:00 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 20 13:57:00 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Jan 20 13:57:00 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 20 13:57:00 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 20 13:57:00 Tower emhttpd: shcmd (6034): mkdir -p /mnt/disk2 Jan 20 13:57:00 Tower emhttpd: shcmd (6035): mount -t xfs -o noatime /dev/md2 /mnt/disk2 Jan 20 13:57:00 Tower kernel: XFS (md2): Mounting V5 Filesystem Jan 20 13:57:00 Tower kernel: XFS (md2): Ending clean mount Jan 20 13:57:01 Tower kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Jan 20 13:57:01 Tower emhttpd: shcmd (6036): xfs_growfs /mnt/disk2 Jan 20 13:57:01 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=244188659 blks Jan 20 13:57:01 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 20 13:57:01 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 20 13:57:01 Tower root: = reflink=1 Jan 20 13:57:01 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 20 13:57:01 Tower root: = sunit=0 swidth=0 blks Jan 20 13:57:01 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 20 13:57:01 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Jan 20 13:57:01 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 20 13:57:01 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0
January 20, 20224 yr Community Expert Previous diags are after array stop, post new diags after array start in normal mode.
January 20, 20224 yr Author I rebuilt those disks by un-assigning them and the re-adding them. 1 minute ago, JorgeB said: According to diags disks 1 and 2 mounted, or did you format them? Screenshot is maybe in maintenance mode? Jan 20 13:57:00 Tower emhttpd: shcmd (6033): xfs_growfs /mnt/disk1 Jan 20 13:57:00 Tower kernel: xfs filesystem being mounted at /mnt/disk1 supports timestamps until 2038 (0x7fffffff) Jan 20 13:57:00 Tower root: meta-data=/dev/md1 isize=512 agcount=4, agsize=244188659 blks Jan 20 13:57:00 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 20 13:57:00 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 20 13:57:00 Tower root: = reflink=1 Jan 20 13:57:00 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 20 13:57:00 Tower root: = sunit=0 swidth=0 blks Jan 20 13:57:00 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 20 13:57:00 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Jan 20 13:57:00 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 20 13:57:00 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 20 13:57:00 Tower emhttpd: shcmd (6034): mkdir -p /mnt/disk2 Jan 20 13:57:00 Tower emhttpd: shcmd (6035): mount -t xfs -o noatime /dev/md2 /mnt/disk2 Jan 20 13:57:00 Tower kernel: XFS (md2): Mounting V5 Filesystem Jan 20 13:57:00 Tower kernel: XFS (md2): Ending clean mount Jan 20 13:57:01 Tower kernel: xfs filesystem being mounted at /mnt/disk2 supports timestamps until 2038 (0x7fffffff) Jan 20 13:57:01 Tower emhttpd: shcmd (6036): xfs_growfs /mnt/disk2 Jan 20 13:57:01 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=244188659 blks Jan 20 13:57:01 Tower root: = sectsz=512 attr=2, projid32bit=1 Jan 20 13:57:01 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 20 13:57:01 Tower root: = reflink=1 Jan 20 13:57:01 Tower root: data = bsize=4096 blocks=976754633, imaxpct=5 Jan 20 13:57:01 Tower root: = sunit=0 swidth=0 blks Jan 20 13:57:01 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 20 13:57:01 Tower root: log =internal log bsize=4096 blocks=476930, version=2 Jan 20 13:57:01 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 20 13:57:01 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0
January 20, 20224 yr Author 9 minutes ago, trurl said: You checked them with the no modify flag (-n) so the check only found the problems it didn't fix them. Here is what I ran on all the disks and followed all the instructions.
January 20, 20224 yr Community Expert 4 minutes ago, corgiguy said: I rebuilt those disks by un-assigning them and the re-adding them. I know, but initially they weren't mounting, as the screenshot you posted shows. 5 minutes ago, JorgeB said: post new diags after array start in normal mode.
January 20, 20224 yr Author 6 minutes ago, JorgeB said: Previous diags are after array stop, post new diags after array start in normal mode. Please see attached. tower-diagnostics-20220120-1425.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.