Jump to content

Can't mount brand new Disk


BelviGER
Go to solution Solved by JorgeB,

Recommended Posts

unRaAID v6.12.4

"Fix Common Problems" Plugin and thats it

 

Hey,

 

I had to replace my parity drive(sdc). Replaced a 14tb ironwolf with a 14tb wd red.

When booting the server the drive will show up as an available drive, but after selecting it it disappears.

 

It remains visible as a drive in Tools>System Devices

 

The log throws a bunch of I/O Errors though.

 

 

Nov 12 10:40:01 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 12 10:40:01 Tower kernel: ata5.00: irq_stat 0x40000001
Nov 12 10:40:01 Tower kernel: ata5.00: failed command: READ DMA EXT
Nov 12 10:40:01 Tower kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 0 dma 4096 in
Nov 12 10:40:01 Tower kernel:         res 53/40:08:80:ff:df/00:00:5d:06:00/40 Emask 0x9 (media error)
Nov 12 10:40:01 Tower kernel: ata5.00: status: { DRDY SENSE ERR }
Nov 12 10:40:01 Tower kernel: ata5.00: error: { UNC }
Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Nov 12 10:40:01 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Nov 12 10:40:01 Tower kernel: ata5.00: configured for UDMA/133
Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 Sense Key : 0x3 [current] 
Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 ASC=0x11 ASCQ=0x4 
Nov 12 10:40:01 Tower kernel: sd 5:0:0:0: [sdc] tag#0 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00
Nov 12 10:40:01 Tower kernel: I/O error, dev sdc, sector 27344764800 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov 12 10:40:01 Tower kernel: ata5: EH complete
Nov 12 10:40:01 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov 12 10:40:01 Tower kernel: ata5.00: irq_stat 0x40000001
Nov 12 10:40:01 Tower kernel: ata5.00: failed command: READ DMA EXT
Nov 12 10:40:01 Tower kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 5 dma 4096 in
Nov 12 10:40:01 Tower kernel:         res 53/40:08:80:ff:df/00:00:5d:06:00/40 Emask 0x9 (media error)
Nov 12 10:40:01 Tower kernel: ata5.00: status: { DRDY SENSE ERR }
Nov 12 10:40:01 Tower kernel: ata5.00: error: { UNC }
Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Nov 12 10:40:02 Tower kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Nov 12 10:40:02 Tower kernel: ata5.00: configured for UDMA/133
Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 Sense Key : 0x3 [current] 
Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 ASC=0x11 ASCQ=0x4 
Nov 12 10:40:02 Tower kernel: sd 5:0:0:0: [sdc] tag#5 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00
Nov 12 10:40:02 Tower kernel: I/O error, dev sdc, sector 27344764800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Nov 12 10:40:02 Tower kernel: Buffer I/O error on dev sdc, logical block 3418095600, async page read
Nov 12 10:40:02 Tower kernel: ata5: EH complete

 

This error repeats every minute.

 

Is the drive DOA, did I forget something, or is it something else?

 

 

Edited by BelviGER
Link to comment
5 minutes ago, itimpi said:

Those errors normally suggest a cabling issue (power or sata).    You can run an extended SMART test on the drive to see if it fails that the drive is probably faulty.

 

I don't think I can run a SMART test because I can't choose it for a smart test because its only available for mounting, it can't be mounted S1.thumb.png.f0eb6e14113e9e42f140ccfb1a44f303.png

When I select it here it disappears from the list 

 

 

Will order a replacement cable though and try that
 

Edited by BelviGER
Link to comment
On 11/13/2023 at 10:03 AM, JorgeB said:

Based on the SMART report looks like a disk problem, try to swap cables with known good ones, if the same it's the disk.

 

I just ordered a new drive because sooner or later I'd need it anyways - and it was the drive

 

So brand new drive arrived dead

  • Like 1
Link to comment
  • 6 months later...

Apologies, but I'm also getting an identical error with a brand new WD Red Plus 14TB HDD. It also 'vanished' when trying to add it as a parity drive, and I'm unable to preclear or reformat it. I already had it exchanged thru Amazon, and the second drive is throwing the exact same issues.

 

I'm about to give up and just order a Seagate Ironwolf drive instead, and a few extra SATA cables just in case that's the issue (though I have three other drives all working A-OK and all came from the same batch of connectors. And another drive on this backplane working OK as well). What are the odds of two DOA drives? Should I just avoid Amazon HDDs?

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.

×
×
  • Create New...