May 2, 201115 yr I added a 2TB drive to my unRAID. AS I didn't mind downtime, I didn't run a preclear script but let unRAID do the clearing. Now the drive has a red ball next to it. If I click on it it says "error (factory-erased)". the syslog periodicallly writes this: May 2 11:50:54 Tower kernel: sd 0:0:5:0: [sdg] ASC=0x0 ASCQ=0x0 (Drive related) May 2 11:50:54 Tower kernel: sd 0:0:5:0: [sdg] CDB: cdb[0]=0x2a: 2a 00 1b 4c 14 e0 00 02 00 00 (Drive related) May 2 11:50:54 Tower kernel: end_request: I/O error, dev sdg, sector 457970912 (Errors) May 2 11:50:54 Tower kernel: ata6: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) May 2 11:50:54 Tower kernel: ata6.00: device reported invalid CHS sector 0 (Drive related) May 2 11:50:54 Tower kernel: ata6: status=0x41 { DriveReady Error } (Errors) May 2 11:50:54 Tower kernel: ata6: error=0x04 { DriveStatusError } (Errors) Considering the drive is not very old, I doubt it has failed - it was running in my drobo until this morning. Any idea what I should do? Maybe run the preclearscript?
May 2, 201115 yr Author even though the drive is technically cleared? I guess it can't hurt to re-run.
May 6, 201115 yr I've got exactly the same problem on a 2TB drive (I think). Did preclear solve it? Haven't done anything like this before, so some help would be appreciated. EDIT: Other things I've tried/notes... - smartctl - resulted in "Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)" - Took it out, put it into a Windows 7 machine, formatted, worked fine (as far as I tested it) - Have tried it a couple of times in my unRAID system, but it's always coming back with a red ball problem - Western Digital 2tb EARS drive. I've replaced my parity and drive one with equivalent drives, no problem - Here, I'm adding a new drive to the array rather than replacing, and it's being plugged into an 8-port SATA card (SuperMicro AOC-SAT2-MV8)
May 6, 201115 yr A red ball means a write to the drive failed. Could be a cable, port, power, or disk problem.
May 6, 201115 yr A red ball means a write to the drive failed. Could be a cable, port, power, or disk problem. Once a drive has failed with a "red" indicator, you must re-construct it. A "write" to it failed. (Even if it was just a loose connector, it will not go "green" on its own if you fix the connector) You must: Stop the array Un-assign the failed disk. Start the array with it un-assigned (This will cause the array to forget the disks serial number) Stop the array Re-assign the drive to its former slot (It will think it is a replacement, since it forgot its original serial number) Start the array. It will re-construct the contents of the disk from parity and the other data disks. Of course, this assumes the disk is not actually failed. If that is the case, then it just needs to be replaced and the same steps followed. Joe L.
May 6, 201115 yr Yes, I've changed cables, ports, power *shouldn't* be a problem and had it running on a Win box fine. Have tried adding it three or four times now with various combinations, initialising configs between to rebuild cache. Taken a couple of weeks. However, I was drawn to this post when sunnyville mentioned "error (factory-erased)" when clicking on the red-ball drive. Something I've not seen before.
Archived
This topic is now archived and is closed to further replies.