I/O errors with two drives


Recommended Posts

Well, I can't really upload the syslog because it's still copying and it's > 500MB:-

2dUF6NF.png

 

and I'm also getting messaging in my terminal like:-

2pEwnmI.png

 

So, here's the last 40 lines:-

tail -n 40 -f /var/log/syslog
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 99 a8 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdj, sector 5860530600
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 7a 20 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdi, sector 5860522528
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] CDB: cdb[0]=0x88: 88 00 00 00 00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 99 a8 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdj, sector 5860530600
Mar 1 14:38:12 Tower kernel: 01 5d 50 7a 20 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdi, sector 5860522528
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Unhandled error code
Mar 1 14:38:12 Tower kernel: 99 a8 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdj, sector 5860530600
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 7a 20 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdi, sector 5860522528
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 99 a8 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdj, sector 5860530600
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x88: 88
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Unhandled error code
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] Result: hostbyte=0x04 driverbyte=0x00
Mar 1 14:38:12 Tower kernel: sd 0:0:1:0: [sdi] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 7a 20 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdi, sector 5860522528
Mar 1 14:38:12 Tower kernel: 00 00 00 00 01 5d 50 99 a8 00 00 00 08 00 00
Mar 1 14:38:12 Tower kernel: end_request: I/O error, dev sdj, sector 5860530600

 

Basically, I'm trying to preclear three drives, the two drives that are throwing errors (SDI and SDJ) are two of the three drives that are preclearing, they're also both 3TB (last drive is 1TB).

Any advice?

 

EDIT:- Both drives are also connected via a SATA controller & SATA breakout cable.

Link to comment

EDIT:- I wanted to say that I'm getting the same errors as this user:-

http://lime-technology.com/forum/index.php?topic=18454.0

 

On both my drives:-

7sdwlNw.png

 

Only reason why I doubt they're dead is because I have been using them fine up until the point I placed them in my unraid server. I'll check the cabling now.

 

EDIT:- No cabling felt loose, and, if I had to say which cables did feel loose it'd be the drives that are in my array and working fine. I'll try the preclear again.

 

EDIT2:- One drive seems to be in the process of preclearing, while the other one is just idling:-

58FrQDX.png

 

q1cC8HD.png

 

They were both started within 20 seconds of each other, the first one is not updating:-

87PTtyQ.png

 

EDIT:- CTRL+C'd the idle drive and got this when trying to restart it:-

i4ZhtI8.png

Link to comment

Bump.

 

Also, SDI seems to be working fine now(?) and isn't giving any errors, here's the preclear status:-

Preclear in progress... Post-Read (1 of 3). 28% @ 70 MB/s (14:57:33)

 

But SDJ is still being a bitch and refuses to reply to fdisk -l /dev/sdj:-

root@Tower:~# fdisk -l /dev/sdj                                                                                                                                                               
root@Tower:~# fdisk -l /dev/sdi                                                                                                                                                               
                                                                                                                                                                                              
Disk /dev/sdi: 3000.6 GB, 3000592982016 bytes                                                                                                                                                 
255 heads, 63 sectors/track, 364801 cylinders                                                                                                                                                 
Units = cylinders of 16065 * 512 = 8225280 bytes                                                                                                                                              
Sector size (logical/physical): 512 bytes / 4096 bytes                                                                                                                                        
I/O size (minimum/optimal): 4096 bytes / 4096 bytes                                                                                                                                           
Disk identifier: 0x00000000                                                                                                                                                                   
                                                                                                                                                                                              
   Device Boot      Start         End      Blocks   Id  System                                                                                                                                
/dev/sdi1               1      267350  2147483647+   0  Empty                                                                                                                                 
Partition 1 does not end on cylinder boundary.                                                                                                                                                
Partition 1 does not start on physical sector boundary.                                                                                                                                       
root@Tower:~#              

Link to comment

It sounds as if your /dev/sdj device is dropping offline for some reason.  I think a syslog will be needed for anyone to give any sort of diagnosis.  That would at least show if the disk is ever being seen by the system or starts of working and then is being disabled.

 

It must be worth checking all cabling in case any have worked loose.

Link to comment

It sounds as if your /dev/sdj device is dropping offline for some reason.  I think a syslog will be needed for anyone to give any sort of diagnosis.  That would at least show if the disk is ever being seen by the system or starts of working and then is being disabled.

 

It must be worth checking all cabling in case any have worked loose.

 

As per the thread:-

A. I can't really give a system log since it's insanely huge, I provided the last 40 lines above, if you'd like more, tell me.

B. I have checked the cabling, as per what I posted in the thread

C. It would seem to be detected by the system as the preclear script successfully acquires a smart report, model number, serial number & starts, but, the second it starts reading actual (modifiable) data it drops off.

Link to comment

A. I can't really give a system log since it's insanely huge

Since most of the content is repeated lines, it will zip insanely well. How big is the syslog after you compress it, as referenced here?

 

Good point, I completely forgot how well text zips up, anyway, I'll upload that after the current drive has finished preclearing as I'll have to restart the server without plugins/etc to get a nice clean logfile for you.

Link to comment

A. I can't really give a system log since it's insanely huge

Since most of the content is repeated lines, it will zip insanely well. How big is the syslog after you compress it, as referenced here?

 

Good point, I completely forgot how well text zips up, anyway, I'll upload that after the current drive has finished preclearing as I'll have to restart the server without plugins/etc to get a nice clean logfile for you.

 

Make sure that the syslog contains entries for an error event.

Link to comment

Uptime is ~ 5 minutes, preclear is frozen, however, now it seems to reply to fdisk as long as I keep the preclear open, log file is 2GB (18.2 million lines), so, no idea how you're gonna read it, but:-

v7h9Qqw.png

 

And, like I said, no idea how you're gonna read it (This seems to work for me):-

AYSXXN2.png

 

Oh, and, if I close the preclear then it stops replying:-

dmCWXv2.png

 

Anyway, here's the log file:-

 

7Zip download (2GB in 20.2MB):- http://dl.dropbox.com/u/453865/For%20people/WD_IDLE_3TB_SDJ.7z

Zip download (2GB in 51.9MB):- http://dl.dropbox.com/u/453865/For%20people/WD_IDLE_3TB_SDJ.zip

 

Both downloads are the same file, I just felt as though I'd zip it in 7zip format for download speed (Then zip in case you don't have unrar/7zip insatlled).

 

Oh, and if you don't want to download it, it's basically a hell of a lot of these 4 lines:-

Mar  4 11:23:05 Tower kernel: sd 0:0:2:0: [sdj] Unhandled error code
Mar  4 11:23:05 Tower kernel: sd 0:0:2:0: [sdj]  Result: hostbyte=0x04 driverbyte=0x00
Mar  4 11:23:05 Tower kernel: sd 0:0:2:0: [sdj] CDB: cdb[0]=0x28: 28 00 1a 4b fd f0 00 00 08 00
Mar  4 11:23:05 Tower kernel: end_request: I/O error, dev sdj, sector 441187824

 

Just that with a different sector/error code.

Link to comment

Threw it into window, not really sure what to do now?

 

2rxBxij.png

 

Just allocated it and I guess I'll just run something like diskpart and do a long format?

 

PL8fZKE.png

 

EDIT:- Okay, doing a long format:-

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved

C:\Users\Nicholas>diskpart

Microsoft DiskPart version 6.1.7600
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: NICHOLAS-PC

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          119 GB      0 B
  Disk 1    Online         2794 GB      0 B        *

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> create partition primary

DiskPart succeeded in creating the specified partition.

DISKPART> clean

DiskPart succeeded in cleaning the disk.

DISKPART> create partition primary

DiskPart succeeded in creating the specified partition.

DISKPART> select partition 1

Partition 1 is now the selected partition.

DISKPART> active

The selected disk is not a fixed MBR disk.
The ACTIVE command can only be used on fixed MBR disks.

DISKPART> format fs=fat32

There is no volume selected.
Please select a volume and try again.

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> select partition 1

Partition 1 is now the selected partition.

DISKPART> format fs=fat32

There is no volume selected.
Please select a volume and try again.

DISKPART> format fs=ntfs

There is no volume selected.
Please select a volume and try again.

DISKPART> format

There is no volume selected.
Please select a volume and try again.

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          119 GB      0 B
* Disk 1    Online         2794 GB      0 B        *

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved           128 MB    17 KB
  Partition 2    Primary           2794 GB   129 MB

DISKPART> select partition 2

Partition 2 is now the selected partition.

DISKPART> format fs=fat32

    0 percent completed

DiskPart has encountered an error: The parameter is incorrect.
See the System Event Log for more information.

DISKPART> format fs=ntfs

    0 percent completed

Link to comment

Uptime is ~ 5 minutes, preclear is frozen, however, now it seems to reply to fdisk as long as I keep the preclear open, log file is 2GB (18.2 million lines), so, no idea how you're gonna read it, but:-

 

Anyway, here's the log file:-

7Zip download (2GB in 20.2MB):- http://dl.dropbox.com/u/453865/For%20people/WD_IDLE_3TB_SDJ.7z

 

Thanks for the 7zip, good idea.  My Total Commander's built-in viewer had no problems with the file.  Your system had no trouble setting up, but within a minute of starting a preclear of sdj the controller was not responding, and in less than another minute, the system disabled the drive.  Once a drive is disabled, you can completely ignore all related disk errors that follow, and yes in this case, that is about 2GB of syslog lines of related disk errors!  That may be a new record!

 

There is no info as to why the controller or disk stopped communicating, but I see some "sas_scsi_find_task: aborting task" statements in there, and I believe I have read somewhere of other users with similar 'task aborting' statements who updated their controller card firmware, and that fixed this issue.  Checking for an updated firmware would be my strong recommendation.

Link to comment

Uptime is ~ 5 minutes, preclear is frozen, however, now it seems to reply to fdisk as long as I keep the preclear open, log file is 2GB (18.2 million lines), so, no idea how you're gonna read it, but:-

 

Anyway, here's the log file:-

7Zip download (2GB in 20.2MB):- http://dl.dropbox.com/u/453865/For%20people/WD_IDLE_3TB_SDJ.7z

 

Thanks for the 7zip, good idea.  My Total Commander's built-in viewer had no problems with the file.  Your system had no trouble setting up, but within a minute of starting a preclear of sdj the controller was not responding, and in less than another minute, the system disabled the drive.  Once a drive is disabled, you can completely ignore all related disk errors that follow, and yes in this case, that is about 2GB of syslog lines of related disk errors!  That may be a new record!

 

There is no info as to why the controller or disk stopped communicating, but I see some "sas_scsi_find_task: aborting task" statements in there, and I believe I have read somewhere of other users with similar 'task aborting' statements who updated their controller card firmware, and that fixed this issue.  Checking for an updated firmware would be my strong recommendation.

 

Okay, thanks for this advice. I'll do it directly after I'm done formatting the drive (in windows).

 

One thing to note is that the drive works perfectly in windows, but crashes in both UNRAID and DBAN.

Link to comment

One thing to note is that the drive works perfectly in windows, but crashes in both UNRAID and DBAN.

 

In Windows, you have it attached to a different controller?  And with UnRAID and DBAN, it is attached to the SAS controller?  If so, then that also points to a SAS card issue, such as a firmware bug.

Link to comment

One thing to note is that the drive works perfectly in windows, but crashes in both UNRAID and DBAN.

 

In Windows, you have it attached to a different controller?  And with UnRAID and DBAN, it is attached to the SAS controller?  If so, then that also points to a SAS card issue, such as a firmware bug.

 

Yes, windows is a different machine.

 

Also, on the PC with DBAN/Unraid I've used both a raid controller and a direct connection into the MOBO, both fail. Also, I just woke up (Fully formatted it):-

R5mvAUW.png

 

I don't see a firmware update.

 

EDIT:- I placed it back into the unraid box after a long format in windows (Which writes 0s to the drive & then creates the MBR/etc):-

 

A. No errors in syslog:-

Mar 5 08:30:26 Tower login[8900]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.4'
Mar 5 08:30:50 Tower kernel: sdj: sdj1 sdj2
Mar 5 08:31:47 Tower sSMTP[10591]: Creating SSL connection to host
Mar 5 08:31:47 Tower sSMTP[10591]: SSL connection using RC4-SHA
Mar 5 08:31:52 Tower sSMTP[10591]: Sent mail for root@ (221 2.0.0 closing connection ex15sm18814154wid.5 - gsmtp) uid=0 username=root outbytes=1610

 

B. Preclear is loading:-

================================================================== 1.13                                                                                                                       
=                unRAID server Pre-Clear disk /dev/sdj                                                                                                                                        
=               cycle 1 of 3, partition start on sector 1                                                                                                                                     
= Disk Pre-Read in progress: 0% complete                                                                                                                                                      
= ( 9,909,043,200  bytes of  3,000,592,982,016  read ) 116 MB/s                                                                                                                               
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
=                                                                                                                                                                                             
Disk Temperature: 22C, Elapsed Time:  0:01:31

 

So, until it's complete I don't trust it, but, it seems to be working.

Link to comment

It lasted 30 hours this time:-

================================================================== 1.13                                                                                                                       
=                unRAID server Pre-Clear disk /dev/sdj                                                                                                                                        
=               cycle 1 of 3, partition start on sector 1                                                                                                                                     
= Disk Pre-Clear-Read completed                                 DONE                                                                                                                          
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE                                                                                                                          
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE                                                                                                                          
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE                                                                                                                          
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE                                                                                                                          
= Step 5 of 10 - Clearing MBR code area                         DONE                                                                                                                          
= Step 6 of 10 - Setting MBR signature bytes                    DONE                                                                                                                          
= Step 7 of 10 - Setting partition 1 to precleared state        DONE                                                                                                                          
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE                                                                                                                          
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE                                                                                                                          
= Step 10 of 10 - Verifying if the MBR is cleared.              DONE                                                                                                                          
= Post-Read in progress: 68% complete.                                                                                                                                                        
(  2,064,545,280,000  of  3,000,592,982,016  bytes read ) 87.0 MB/s                                                                                                                           
Disk Temperature: 27C, Elapsed Time:  30:16:08      

 

Frozen again, Syslog:-

tail -n 40 -f /var/log/syslog
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] CDB: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 83 10 00 00 00 08 00 00
Mar 6 14:53:34 Tower kernel: end_request: I/O error, dev sdj, sector 5860524816
Mar 6 14:53:34 Tower kernel: sd 0:0:6:0: [sdj] Unhandled error code

Link to comment

Personally I would RMA it and tell them it was because of "performance problems" if your RMA'ing to WD.

 

So both the 3TB drives and the 1TB drive that I've been using fine in windows for ages have all magically failed (One SMART failure, two physical failure) when I transferred them over to UNRAID?

 

Just my luck.  :-[ All of my new drives that I bought directly before setting up UNRAID (and never used on windows) work fine, I blame windows.

Link to comment

Personally I would RMA it and tell them it was because of "performance problems" if your RMA'ing to WD.

 

So both the 3TB drives and the 1TB drive that I've been using fine in windows for ages have all magically failed (One SMART failure, two physical failure) when I transferred them over to UNRAID?

 

Just my luck.  :-[ All of my new drives that I bought directly before setting up UNRAID (and never used on windows) work fine, I blame windows.

Maybe/Maybe not but you have two options either return them to a window box where they appear to work or RMA them if you can.  At a certain point continued attempts are a waste of time.  I try to preclear on 2-3 different boxes if it doesn't work after that - back they go.  I sent one back to NewEgg that I might have been able to salvage if I had tried the Windows format earlier.  It was the replacement for that RMA that I tried the Windows format on.  Couldn't believe I would get a replacement that was bad too - especially since it was a WD Red.  So after I couldn't clear it on two different PCs I stuck it in to a windows PC expecting it to fail on the long format and I could report it to NewEgg.  When it completed I put it back in my preclear station and ran 3 preclears on it successfully also and put it in the array.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.