pete69

It's working as expected for me. Are you sure the folders shown on that disk actually have data? your share may have data in that folder but it is stored on a different disk. Look at the folder on disk1 only, don't look at the share.

I got scared with this option and ended up going the normal route, rebuilding each parity drive one at a time. But thanks for your help.

Thanks, I'll give that a try.

Thanks it was previously set to shutdown at 80%, but the connection does not seem to be working after recent updates. I'll look into it when the parity issue is solved.

I have had a long blackout. I have a UPS which interfaces to unraid, and is supposed start a clean shutdown. I was not home but based on both parity drives showing disabled on restart I assume that is what happened. I did not have syslog server running, but after reading through threads here, I now do. Smart is fine on the disabled drives. I have had single data drives disabled before, and rebuilt ok. This is the first time I have had parity drives disabled, and can't find another thread that discusses both being disabled at the same time. They are a pair of 14tb drives, so will take a long time to rebuild, and I assume I now have an array without any parity protection, which is pretty crap considering I put the 2 drives in so I would not be in this position. I upgraded to V7 about a week ago if that makes any difference, it does look like it broke the UPS linking which I'll figure out. What is the best way to move forward from here? Bite the bullet and unassign one of the parity drives, re assign and rebuild, then the other or something different? Pete.

If you are re-cycling Netapp or some other modified sector size drives, then you will need the same process each time. If you are buying new drives, the sector size should be fine as Unraid handles most standard sector sizes out of the box.

I only have the one shelf currently connected, but had 2 in the past. Since you have 2 ports on your controller, just connect each port to the square SAS port on both your IOMs, that would give you 2 independent SAS paths for each shelf and they would be treated as separate entities by unraid. I think that would be better than trying to daisy chain the shelves which would have no benefit in Unraid.

I had similar issues on start up running 6.8.3, with some drives not showing (sometimes reds sometimes others). Usually pulling the drives and reseating or moving drives to other locations got them online. Once online it was rock solid until I needed to restart unraid and go through the process again. I initially thought it might be a backplane issue with the disk shelf, but didn't care too much as I don't need to restart unraid very often. When I upgraded unraid to 6.9.0 none of the drives were recognised due to the kernel issue. Rather than wait for a fix or remain on 6.8.3, I purchased an LSI 9212-4i4e 6Gb SAS Controller Card set on IT mode, and a QSFP SFF-8436 to Mini SAS SFF-8088 Cable. Since then it works fine on 6.9.x and the drives are all online at each restart without any fiddling. Pete.

I had the same problem using the PM8003. With V6.9.0 Stable. The PM8003 also used to drop drives occasionally on 6.8.3, but only when unraid was started, requiring drives to be pulled and re-seated to refresh the array. It was rock sold once running. Rather than wait for a fix or remain on 6.8.3, I purchased an LSI 9212-4i4e 6Gb SAS Controller Card set on IT mode, and a QSFP SFF-8436 to Mini SAS SFF-8088 Cable. I have not seen any issues with the LSI controller on 6.9.2.

I am using preclear for the first time. I installed 2 seagate drives that I knew had issues and 1 brand new 10TB WD RED. The 2 Seagate drives I knew had issues eventually both failed the pre-read, and the new WD passed. The WD Continued into zeroing as far as 21%. The logs look good for 5-20%. Each 5% has generally taken less than a hour. Preclear has now been stuck on 21% for over 3 hours, and there is no activity on the drive LED. Before I cancel it and retry, is there anything I can grab to assist the author with checking why it froze without showing any error message? Pete.