Posted April 5, 20214 yr Hi everyone, I was in the process of migrating my server to a new (very old) Norco 4224 case last weekend. Long story short I couldnt get the drives to detect through the sas backplanes, so I migrated back to my original case. I had a couple of HDD's drop out during that process, which ultimently lead to some data loss. No big deal, just Media stored on this server. I had some other issues around the same time, which I believed to be an issue with my cache drive. Since then I have replaced it with an m.2 drive. Now everything seems to be working OK, and I am in the process of redownloading missing media. However, over night I have filled my cache drive with downloaded data which Sonarr is no longer moving onto my array (it was working last night). Manually copy pasting to the array doesnt work either, as I get the following error (through Win10) . *Error 0x8007045D: The request could not be performed because of an I/O device error* I get the same error when trying to access drive10 directly from my /tower/ directory. This drive had been rebuilt a day or so ago, so I assume this is where the fault lies. I am currently 24 hours into a parity rebuild (the parity drive got unmounted while I was futzing around), so I havent tried to reboot yet. I am currently running newpermissions just incase that is at fault, and I have attached my diagnostics. I have 2 replacement 12TB hdd's coming, one of which will replace my cache drive, and at this stage I assume the other will be replacing drive10. They wont be here for another 10 days though (delivering from tyhe UK to Australia) HELP! wotbox-diagnostics-20210405-2128.zip Edited April 28, 20214 yr by Die_piggy
April 5, 20214 yr Community Expert Check filesystem on disk10: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Disk5 appears to be failing, and since parity is not valid you may lose some data there.
April 5, 20214 yr Author Thanks for the Heads up on Disk5. ill do your suggestions soon as parity has completed (about 4 hours)
April 5, 20214 yr Community Expert Note that parity won't be 100% valid due to the read errors on disk5.
April 5, 20214 yr Community Expert Some additional thoughts 3 hours ago, Die_piggy said: access drive10 directly from my /tower/ directory I recommend not sharing disks. 3 hours ago, Die_piggy said: running newpermissions running New Permissions on appdata may break some containers.
April 5, 20214 yr Author Hi guys, running the checkfilesystem/repair worked opn disk10 thanks! I will replace disk5 ASAP with a new drive. Any other issues anyone can see?
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.