February 24, 201610 yr I've got a 4TB 2.5" disk that is showing as disabled. Its a new disk that was recently inserted into the system. (Was cleared then formatted by unRAID) Smart health check reports as passed. From reading other posts; I have tried the following: 1. Stop the array 2. Remove disk from array 3. Start the array 4. Stop the array 5. Add disk back to array 6. Start array - let disk be rebuilt. Now it fails during the rebuild process which leads me to believe that parity is fubar'd. The disk itself has very little data on it; so I'm more than happy to lose what data I had on it; however the other disks in my array cant lose data. I've attached the syslog; this is after restarting my unRAID machine. Array is currently running without the disk in the array - unprotected. I'm thinking of simply rebuilding the array right now (New Config) just so atleast my remaining data is safe for the time being.. What do you guys think? syslog.txt
February 24, 201610 yr Community Expert Like jonathanm said. We really don't want just the syslog anymore, and the one you have attached only covers about 5 minutes after a reboot and nothing from the activity that you are describing so it isn't very helpful here. Go to Tools - Diagnostics and post the complete diagnostics zip file. That zip file includes your syslog and a lot of other things like the SMART attributes for all drives. Nothing in your description leads me to believe your parity is fubar. My first guess would be a bad connection.
February 24, 201610 yr Community Expert Now it fails during the rebuild process which leads me to believe that parity is fubar'd. The disk would have originally been disabled because a write to it failed. If it failed during rebuild that mean a write to it failed again. The reason for these write failures needs to be identified. It could be something like a bad connection, or it could be that the drive itself has issues.
February 25, 201610 yr Community Expert Looks like you set a New Config. You really should work with us and tell us these things instead of making us work so hard to figure them out. You should probably scrub your cache pool.
February 25, 201610 yr Author Apologies - I just didnt want to leave the array unprotected any longer. Scrubbing now.
February 25, 201610 yr Author I should elaborate a bit more on my H/W set-up. So its an HP N54L Microserver. Four 3.5" drives currently populated in the four available trays. I've got an Icydock MB994SP-4S enclosure currently sitting in the 5.25" slot; and this takes upto 4 2.5" drives. Reason I picked this particular enclosure up is that it supports 15mm drives; which my 2.5" 4TB seagate is. This is all connected together via Startech PCIe Controller (Mini-SAS breakout). P/N - PEXSAT34SFF (Datasheet says Marvell 88SE9230 chipset)
March 6, 201610 yr Author Alright; I'm just upgrading to 6.1.9; will reboot then add the drive back to the pool. I have changed the slot the drive goes in (thus effectively using a different mini-sas breakout cable) so lets see if it fares any better.
Archived
This topic is now archived and is closed to further replies.