assur191

Thanks again for the responses. I will go ahead and rebuild disk 17 and repair the filesystem on disk 3. However, I just want to confirm that I should first rebuild 17, then repair 3. Will that order result in the least amount of lost data?

Thanks all for your feedback. I rebooted the server and checked connections, and now I'm showing the message: The drive is now showing "healthy" under SMART, where it was "error" before. Is there any way I can just re-enable the drive without rebuilding, then fix the filesystem on drive 3? I have attached the new diagnostics here. Also, regarding the Marvell controllers, are they any suggestions on what I should replace them with? tower-diagnostics-20201009-1018.zip

Thank you, ChatNoir. I have attached my diagnostics here. tower-diagnostics-20201008-0840.zip

Hello All, I have an array of 22 drives and 1 parity drive, all xfs formatted. Simultaneously Disk 2 is showing "Unmountable: no filesystem" and Disk 17 is showing disabled, with contents emulated. I would like to try to restore Disk 2 and also replace Disk 17. I would appreciate any feedback on in which order I should resolve these issues, or what approaches I may take. I have attached a syslog I just captured after stopping and restarting the array. Please let me know any additional information I can provide. syslog.txt

Thank you for the information. I could have sworn I had it set to "Only" before. I was under the impression that "Only" required any new data to go to the cache drive, but it still used the Mover. Regardless, I changed it to "yes", and it's not working. Thank you.

Hello, I recently completed the process of converting a couple disks from Reiser to XFS. Now, when I run the mover, it skips over my only share "Media". The other three shares are on my cache drive. Oct 2 08:48:39 Tower logger: mover started Oct 2 08:48:39 Tower logger: skipping "Media" Oct 2 08:48:39 Tower logger: skipping "appdata" Oct 2 08:48:39 Tower logger: skipping "apps" Oct 2 08:48:39 Tower logger: skipping "downloads" Oct 2 08:48:39 Tower logger: mover finished I have the "Media" share set to Use cache disk "Only", and I deleted all the hidden Apple directories as suggested in another thread. Could someone please give me some direction on this issue? My cache is filling up. Thanks. tower-diagnostics-20151002-0855.zip

If you are copying files from a corrupt filesystem, then it's likely that there will be problems when trying to copy some files. Thanks again. So would it make sense to copy what I can to a new drive (create a backup of sorts), then --rebuilt-tree the old drive and try to copy over what can be saved from that to the new drive?

Thanks, trurl. That's what I was afraid of. If I were to copy the contents of the bad drive to a new drive with XFS format, are there any potential issues that I'm not aware of?

So I relocated the SATA expansion card to an open PCIe slot, and was able to rebuild. However, I now get permission errors, and after running reiserfsck, I was told to run --rebuild-tree. I really don't want to do that, since I've lost a lot of data before with that. If I were to rebuild onto a new drive, would that resolve the reiserfs errors and move over all the files?

I was reading in another post, that connecting drives to SATA expansion cards, as well as directly to the motherboard is not a good idea. Could this be causing my issue?

The power supply is a Corsair AX850

Hello, I've been having trouble getting one particular drive (or really, one particular drive slot) to stay green. I have a NORCO case, and I replaced a backplane, as I was having that issue no matter what drive I plugged into the old backplane. I rebuilt a drive on the new backplane, and it was good for a while, but now it's back to being red-balled. I tried re-building to the same drive, and tried rebuilding to a different drive as well, but both are red-balling before the rebuild completes. My suspicion now is that the SATA extender card is at fault. The 2nd backplane the card is connected to has issues with 2 of the 4 slots as well. The card is a Super AOC-SASLP-MV8. I have another of those as well, but that one is working well. I would like to be able to determine if the extender card is the issue for sure before replacing it. I have attached the diagnostic zip from my version 6.0.1 unRaid server. The failing drive is Disk 13. Any feedback is appreciated. tower-diagnostics-20150826-0821.zip

Thank you. I will re-rebuild the drive and capture the reports. Those reiserfs errors seem to be popping up sometimes when I move files out of the lost+found folder and back into the array. I ran new permissions per an earlier response, but that didn't stop the errors.

I have attached the most recent syslog. Unfortunately, I didn't think to create a syslog after the rebuild. Should I rebuild again and capture a syslog after? syslog.zip

I rebuilt the drive after running reiserfsck. Not only did I rebuild the drive, which did not resolve the red ball, but I replaced it and put the new drive into a different drive bay. I am able to fully access the contents of the drive, but it's still red-balled, and I am unable to test parity.