BigDaddyMoe Posted October 16, 2021 Share Posted October 16, 2021 6.9.2, Array stopped, stale configuration Disk 1 disabled Disk 3 missing Disk 3 shows on sas bios, switched cable to mainboard sata, still missing Please anyone that can help, much appreciated, it has been a week that I have tried to get the array started. tower45tb-diagnostics-20211016-1113.zip tower45tb-syslog-20211016-1610.zip Quote Link to comment
BigDaddyMoe Posted October 18, 2021 Author Share Posted October 18, 2021 Anyone with knowledge to help me? Please tower45tb-diagnostics-20211018-0953.zip tower45tb-syslog-20211018-1453.zip Quote Link to comment
JorgeB Posted October 18, 2021 Share Posted October 18, 2021 Disk3 is failing to initialize, replace cables and/or try a different controller: Oct 15 15:53:41 Tower45TB kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 15 15:53:41 Tower45TB kernel: ata2.00: failed to read native max address (err_mask=0x1) Oct 15 15:53:41 Tower45TB kernel: ata2.00: HPA support seems broken, skipping HPA handling Oct 15 15:53:41 Tower45TB kernel: ata2.00: READ LOG DMA EXT failed, trying PIO Oct 15 15:53:41 Tower45TB kernel: ata2.00: failed to get NCQ Send/Recv Log Emask 0x1 Oct 15 15:53:41 Tower45TB kernel: ata2.00: failed to get NCQ Non-Data Log Emask 0x1 Oct 15 15:53:41 Tower45TB kernel: ata2.00: ATA-9: WDC WD102KFBX-68M95N0, VCGAJHLM, 83.00A83, max UDMA/133 Oct 15 15:53:41 Tower45TB kernel: ata2.00: 19532873728 sectors, multi 16: LBA48 NCQ (depth 32), AA Oct 15 15:53:41 Tower45TB kernel: ata2.00: failed to get NCQ Send/Recv Log Emask 0x1 Oct 15 15:53:41 Tower45TB kernel: ata2.00: failed to get NCQ Non-Data Log Emask 0x1 Oct 15 15:53:41 Tower45TB kernel: ata2.00: configured for UDMA/133 Quote Link to comment
BigDaddyMoe Posted October 21, 2021 Author Share Posted October 21, 2021 First post above, I switched cable to mainboard sata, still missing. So it is missing if i connect tom my sas controller or if I use a sata cable to my mainboard. Very scary! Quote Link to comment
JorgeB Posted October 21, 2021 Share Posted October 21, 2021 6 minutes ago, BigDaddyMoe said: So it is missing if i connect tom my sas controller or if I use a sata cable to my mainboard. Then it's likely a disk problem, assuming power cable was already replaced/swapped. Quote Link to comment
BigDaddyMoe Posted October 24, 2021 Author Share Posted October 24, 2021 Damn they are new disks. I replaced the SAS board and now I have an additional drive missing! This is crazy! I have attatched files if you can provide any insight it would be much appreciated! tower45tb-diagnostics-20211024-1117.zip tower45tb-syslog-20211024-1616.zip Quote Link to comment
BigDaddyMoe Posted October 24, 2021 Author Share Posted October 24, 2021 I do not want to lose all my data, years worth of work. Quote Link to comment
JorgeB Posted October 25, 2021 Share Posted October 25, 2021 Again looks like a power/connection problem, try different cables or a different PSU Quote Link to comment
BigDaddyMoe Posted October 25, 2021 Author Share Posted October 25, 2021 Thanks for the reply, power cables or sata cables? I switched to a new controller and now have another disk missing! tower45tb-diagnostics-20211024-1125.zip tower45tb-syslog-20211024-1616.zip Quote Link to comment
JorgeB Posted October 26, 2021 Share Posted October 26, 2021 Try either or both, and not just the power cable, could also be a PSU issue like mentioned, certainly it's not something we can help remotely, there's clearly some hardware issue, or very bad luck with the disks. Quote Link to comment
BigDaddyMoe Posted October 27, 2021 Author Share Posted October 27, 2021 I think I have determined that BOTH of my 10TB WD Red Pro Disks failed. Disk 1, I was able to access on a windows machine with a Linux driver. Disk 3 which is listed as missing on Unraid , I could not get to mount on the windows machine. Question, is there a way I can turn off disk 1, which does not have much data on it. And then use the Disk 1 disk in place of the Disk 3 and restart array and have Parity Disk rebuild Disk 3? Or any other thoughts on how to get data off of Disk 3 if I can't get it to mount anywhere? THANKS in advance. Quote Link to comment
JorgeB Posted October 27, 2021 Share Posted October 27, 2021 26 minutes ago, BigDaddyMoe said: Question, is there a way I can turn off disk 1, which does not have much data on it. And then use the Disk 1 disk in place of the Disk 3 and restart array and have Parity Disk rebuild Disk 3? No, parity needs the correct missing disks (the ones that were used to sync it) to be able to rebuild a disk, and with single parity only one disk can be missing/disable. Quote Link to comment
BigDaddyMoe Posted October 27, 2021 Author Share Posted October 27, 2021 Not what I wanted to hear:( Any other thoughts on how to get data off of Disk 3 if I can't get it to mount anywhere? Do you think the disk is fried if I cant mount it anywhere? I thought 10TB WD Red Pro I wouldnt have to worry about it, Disk one that mounts, makes a loud grinding noise on occasion. Quote Link to comment
BigDaddyMoe Posted October 27, 2021 Author Share Posted October 27, 2021 I dont understand why I cant enable disk 1 if unraid finds it, and it mounts on other systems, shouldnt i just be able to choose it in the drop down and it should mount? THANKS Quote Link to comment
JorgeB Posted October 27, 2021 Share Posted October 27, 2021 17 minutes ago, BigDaddyMoe said: I dont understand why I cant enable disk 1 if unraid finds it, and it mounts on other systems, shouldnt i just be able to choose it in the drop down and it should mount? You can re-enable disk1, if it's not failing, but due to being out of sync and using btrfs disk3 would be unmountable, also disk6 could no longer be missing. Quote Link to comment
BigDaddyMoe Posted October 27, 2021 Author Share Posted October 27, 2021 Disk 6 shows up now. Quote Link to comment
JorgeB Posted October 27, 2021 Share Posted October 27, 2021 If you want to try it I'll post the procedure below, but like mentioned almost certainly disk3 will be unmountable, at best there could be some recoverable data using btrfs restore: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk3, replacement disk should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk3 -Start array (in normal mode now), ideally the emulated disk will now mount (unlike in this case) and contents look correct. -If the emulated disk mounts and contents look correct stop the array, re-assign disk3 and start array to begin rebuilding, if it doesn't you can try brtrs restore, on the emulated or rebuilt disk. Quote Link to comment
BigDaddyMoe Posted October 28, 2021 Author Share Posted October 28, 2021 THANKS Will try Quote Link to comment
BigDaddyMoe Posted November 1, 2021 Author Share Posted November 1, 2021 Didnt work I can get the array started but Disk 3 shows Unmountable: not mounted yet the parity rebuild made writes to the disk and it is green square. I'm in safe mode and Check Filesystem Status says See Disk Settings. Quote Link to comment
JorgeB Posted November 2, 2021 Share Posted November 2, 2021 17 hours ago, BigDaddyMoe said: but Disk 3 shows Unmountable: As expected. Quote Link to comment
BigDaddyMoe Posted November 3, 2021 Author Share Posted November 3, 2021 If I tried mounting this from a linux machine would I have better luck trying to get access to my data? root@Tower45TB:~# btrfs-find-root /dev/sdc1 Couldn't read tree root Superblock thinks the generation is 24 Superblock thinks the level is 0 bad key ordering 0 1 leaf free space ret -5563, leaf data size 16283, used 21846 nritems 243 leaf free space ret -5563, leaf data size 16283, used 21846 nritems 243 leaf free space incorrect 30490624 -5563 Well block 30408704(gen: 9 level: 0) seems good, but generation/level doesn't match, want gen: 24 level: 0 Well block 30654464(gen: 8 level: 0) seems good, but generation/level doesn't match, want gen: 24 level: 0 Well block 30638080(gen: 7 level: 0) seems good, but generation/level doesn't match, want gen: 24 level: 0 Well block 30556160(gen: 5 level: 0) seems good, but generation/level doesn't match, want gen: 24 level: 0 root@Tower45TB:~# ___________________________________________________________________________________________________ root@Tower45TB:~# btrfs restore -v /dev/sdc1 /mnt/disk2/restore checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super root@Tower45TB:~# _______________________________________________________________ root@Tower45TB:~# btrfs restore -v /dev/md3 /mnt/disk2/restore checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super root@Tower45TB:~# __________________________________________________________ root@Tower45TB:~# btrfs restore -vi /dev/md3 /mnt/disk2/restore checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super checksum verify failed on 21790720 found 000000CE wanted 00000078 checksum verify failed on 21790720 found 000000CE wanted 00000078 bad tree block 21790720, bytenr mismatch, want=21790720, have=0 Couldn't read tree root Could not open root, trying backup super root@Tower45TB:~# Quote Link to comment
JorgeB Posted November 4, 2021 Share Posted November 4, 2021 10 hours ago, BigDaddyMoe said: If I tried mounting this from a linux machine would I have better luck trying to get access to my data? It will be the same, Unraid is Linux, though if you use the latest kernel the btrfs tools might be a little better. Quote Link to comment
Recommended Posts
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.