BigDaddyMoe

under Fix Common Problems I have the following: disk4 (WDC_WD60EFRX-68L0BN1_WD-WX22D80FH53R) is disabled disk4 (WDC_WD60EFRX-68L0BN1_WD-WX22D80FH53R) has read errors /var/log is getting full (currently 100 % used) Any suggestions or direction on what to do? Thank you! tower45tb-smart-20220218-1311 (1).zip tower45tb-diagnostics-20220218-1319.zip

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:~#

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.

THANKS Will try

Disk 6 shows up now.

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

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.

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.

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

I do not want to lose all my data, years worth of work.

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

Any other advice?

Any other advice?

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!

Anyone with knowledge to help me? Please tower45tb-diagnostics-20211018-0953.zip tower45tb-syslog-20211018-1453.zip

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

I appreciate your help has volunteers! Having paid a license I feel Unraid should have a support line to help newbies like me. So much of the resources are outdated online too. Frustrating.....

hard drive was not in sas bios, so i checked all cables, maybe a power cable to disk 3 was loose? I restarted and it showed hard drive in the sas bios. but nothing has changed with the array. Disk 3 still missing. i cant figure this out? tower45tb-diagnostics-20211015-1219.zip tower45tb-syslog-20211015-1717.zip

appreciate your help, I'm a newbie, are you suggesting I restart server and go into bios to see if harddrive is there?

disk 3 still installed, havent touched anything inside the case of the server.

Array Operation Stopped. Invalid configuration. Too many wrong and/or missing disks!

HELP! tower45tb-syslog-20211013-2356.zip tower45tb-diagnostics-20211013-1856.zip

My point is that i was not copying anything new, my understanding is from the help text as follows: " Specify whether new files and directories written on the share can be written onto the Cache disk/pool if present. This setting also affects mover behavior. No prohibits new files and subdirectories from being written onto the Cache disk/pool. Mover will take no action so any existing files for this share that are on the cache are left there. Yes indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the Cache disk/pool and onto the array. Only indicates that all new files and subdirectories must be writen to the Cache disk/pool. If there is insufficient free space on the Cache disk/pool, create operations will fail with out of space status. Mover will take no action so any existing files for this share that are on the array are left there. Prefer indicates that all new files and subdirectories should be written to the Cache disk/pool, provided enough free space exists on the Cache disk/pool. If there is insufficient space on the Cache disk/pool, then new files and directories are created on the array. When the mover is invoked, files and subdirectories are transferred off the array and onto the Cache disk/pool. NOTE: Mover will never move any files that are currently in use. This means if you want to move files associated with system services such as Docker or VMs then you need to disable these services while mover is running."

but i havent copied anything why causes my array to go to my cache?

why when i swith my share from no to prefer, my cahe fills up rather than get smaller? HELP, PLEASE tower45tb-syslog-20211007-1503.zip tower45tb-diagnostics-20211007-1002.zip