Scales

Thank you JorgeB. Re formatting the cache pool did the trick.

Thanks for that. I will reformat it and see how that goes.

It appears the server is fine without dockers running. I deleted the docker img and re installed some apps and the issue started again. I watched as each cpu core slowly filled up to 100%. Had to power off the machine.

Hello, Server was running great for a number of years. Started having issues with drives showing errors in the UI but the drives would test fine in HD Sentinal. Once sorted, the server will boot and parity check starts. Sometimes parity check will finish and the server will work for a week or month then the system freezes when the CPU usage hit 100% and when I get it back up online it shows more errors. Other times it will only run for about 5 minutes before freezing. It does look like Parity check is still running when the system hangs. I replaced all the sata cables, checked and adjusted drive power cables. re seated everything. Memory passes memtest, I have also tried multiple ram sticks and also another processor. Any advice or assistance is greatly appreciated. beastmode-diagnostics-20200921-1327.zip

The files are there and accessible. These would have been added a few years ago.

I am running 6.7. It is strange that the disk appears have rebuilt with 5.4GB of data. On the bright side I now have approx 4TB free Thanks for help, If anything happens again I will reach out before attempting to screw it up.

I started unraid without the disk and it was emulated. I removed the partition on the corrupted disk using Windows based computer and inserted the drive back into unraid with no file system. I then checked the box to format and the drive was returned to the array with and XFS partition. After that the party-sync / rebuild commenced. Upon completion it looks like there is only 5.2GB returned of the 4TB. I am thinking the corruption was picked up on the last parity check perhaps and that is why the data did not return.

I have a 4TB drive formatted in XFS and I was unable to repair corruption. I pulled the drive and it tested 100% using HD Sentinel so I thought that I could delete the partition on my computer then insert the drive back into my Unraid server and have the data rebuilt. Well I was wrong. The drive is showing as empty on the main gui page. Is my data gone or is there something that I am missing?

Thanks for the reply. Everything is now showing up in the latest SAB. The renaming was an issue with actual paths. And the wiki was simple to follow and worked perfectly I think everything needed a restart or two LOL.

Hello everyone. I followed the wiki to install Couch Potato, Sickbeard, and SABnzbd. So my first file from Couch Potato has downloaded via SABnzbd but did not show in the queue but finished in the history and it is also not renaming the file. Any assistance or direction would be great.

Thank you fine sir Everything is now back on track. Hopefully no more hiccups with the next 10 TB's of data. Too bad you just couldn't convert ext4 to reiserfs.

I have decided to just write the data off as a loss. The data was not priceless and I can always get it back in the long run. Thank you for all the help

That what it says when the drive is in the server. I have now removed it. I have tried test disk and it appears that there is no partition. So upon searching for lost partition it shows up, however Testdisk says there are no files. I am thinking I will cut my losses as I think the file system has too much damage to be recovered. If anyone thinks other wise please let me know.

Hi everyone. I just replaced Amahi with UNRAID 2 days ago. Everything has been going well as I have been transfering all my data over to reiserfs from ext4. However today something happened. I have been transferring all night to a 2TB WDEARS drive. After the transfer was complete I installed unmenu but when I went to start the array it would not start. Upon further investigation it appears that my 2TB drive has no file system. I get this error message when running a file system check in Unmenu: Checking /dev/md3 (/dev/sdc) Sorry, no file system detected on /dev/md3 /dev/md3 mounted on Fdisk -l shows no partition. I used fdisk to prior to this on another drive. There is a small chance that I ran the command on the wrong disk. The 2TB drive is sdc and the fdisk command was run on sdd (perhaps coincidence?) Can anyone help me recover from this? or should I use a recovery program and try to save data to another drive? Is this a bad hard drive? I just moved to Unraid to keep my data safe LOL UNRAID v4.7 No Parity Drive / No Cache Drive Syslog is attached syslog.txt