October 7, 20169 yr Had 6.0 running since release and had a disk failure that has turned into a nightmare. Ended up losing two disks at once. So, since I was having to spend time on my unraid I decided to enhance it (maybe a big mistake?). After recovering data from one drive successfully and getting entire system stable with a complete parity check (successful). I upgraded to 6.2 then 6.2.1. Had another drive fail (failed smart test) which prompted me to replace my:Supermicro AOC-SASLP-MV8 with an AOC-SAS2LP-MV8.. thinking it may be the controller? Rebuilt and fully stable for a day and then another drive threw an error disable and failed smart tests. I ended up doing a parity/swap/disable to install newest 8TB drives (seagates). During the parity rebuild of disk5 I noticed that my array still has some lingering issues. the /mnt/user share throws a : Structure needs cleaning and my user shares were not working. I decided to remove the disk5 and see how it looked as just the emulated disk5. same situation. How can I have had a successful parity build and then the emulated disk5 have this structure needs cleaning? Any thoughts?
October 7, 20169 yr Had 6.0 running since release and had a disk failure that has turned into a nightmare. Ended up losing two disks at once. So, since I was having to spend time on my unraid I decided to enhance it (maybe a big mistake?). After recovering data from one drive successfully and getting entire system stable with a complete parity check (successful). I upgraded to 6.2 then 6.2.1. Had another drive fail (failed smart test) which prompted me to replace my:Supermicro AOC-SASLP-MV8 with an AOC-SAS2LP-MV8.. thinking it may be the controller? Rebuilt and fully stable for a day and then another drive threw an error disable and failed smart tests. I ended up doing a parity/swap/disable to install newest 8TB drives (seagates). During the parity rebuild of disk5 I noticed that my array still has some lingering issues. the /mnt/user share throws a : Structure needs cleaning and my user shares were not working. I decided to remove the disk5 and see how it looked as just the emulated disk5. same situation. How can I have had a successful parity build and then the emulated disk5 have this structure needs cleaning? Any thoughts? You really should post your diagnostics so that the experts can help you out here. But you're going to have to repair the file system on disk 5. A successful rebuild of disk 5 merely means that it rebuilt the drive successfully. If the original drive had file system errors, then parity would reflect this, and the rebuilt drive would have them, and with the drive pulled, the emulated drive would also have them... The odd user here and there also has issues with the SAS2LP's when IOMMU is set in the BIOS. If you're not running VMs and hardware passthrough, it wouldn't be a bad idea to disable IOMMU
Archived
This topic is now archived and is closed to further replies.