Does the built in qemu in unraid need VT-D?

Not for virtualization but it's needed to pass trough a pci device.

Yanked the "bad" drive and installed the new one on a different controller. Rebuilt parity and am now Rebuilding parity on my new 4TB drive.

Maybe I'm missing something but something about this doesn't sound quite right.

 

When you say you "rebuilt parity" after yanking the "bad" drive, do you really mean you checked parity?

 

Yeah, rebuilt wasn't the right word. I just replaced the drive 1-to-1 and let it do whatever it does to replace it.

They usually work fine with vt-d disable, with it enable is hit and miss, mostly miss.

 

Bought a couple of these. Found them on the HCL. I've seen too many things around here about the Marvell controllers. Don't want to play that game.

Yeah, rebuilt wasn't the right word. I just replaced the drive 1-to-1 and let it do whatever it does to replace it.

OK, I think I get it. Rebuilt was the right word, but it wasn't parity you rebuilt, it was the data disk.

 

I'm easily confused when people use words differently than I expect.

Yep yep I feel you. This box has been humming along for like 8 years now so I'm a little behind on the "how it works" portion!

Seeing this in my syslog during my parity swap. How can I figure out which drive ata9 is?

 

Jan 26 20:39:39 Tower kernel: ata9.00: failed command: SMART
Jan 26 20:39:39 Tower kernel: ata9.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 11 pio 512 in
Jan 26 20:39:39 Tower kernel:         res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 26 20:39:39 Tower kernel: ata9.00: status: { DRDY }
Jan 26 20:39:39 Tower kernel: ata9: hard resetting link
Jan 26 20:39:40 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 26 20:39:45 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Jan 26 20:39:45 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan 26 20:39:45 Tower kernel: ata9.00: revalidation failed (errno=-5)
Jan 26 20:39:45 Tower kernel: ata9: hard resetting link
Jan 26 20:39:45 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 26 20:39:55 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Jan 26 20:39:55 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan 26 20:39:55 Tower kernel: ata9.00: revalidation failed (errno=-5)
Jan 26 20:39:55 Tower kernel: ata9: limiting SATA link speed to 3.0 Gbps
Jan 26 20:39:55 Tower kernel: ata9: hard resetting link
Jan 26 20:39:56 Tower kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 26 20:39:56 Tower kernel: ata9.00: configured for UDMA/133
Jan 26 20:39:56 Tower kernel: ata9: EH complete

Seeing this in my syslog during my parity swap. How can I figure out which drive ata9 is?

 

Jan 26 20:39:39 Tower kernel: ata9.00: failed command: SMART
Jan 26 20:39:39 Tower kernel: ata9.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 11 pio 512 in
Jan 26 20:39:39 Tower kernel:         res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 26 20:39:39 Tower kernel: ata9.00: status: { DRDY }
Jan 26 20:39:39 Tower kernel: ata9: hard resetting link
Jan 26 20:39:40 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 26 20:39:45 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Jan 26 20:39:45 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan 26 20:39:45 Tower kernel: ata9.00: revalidation failed (errno=-5)
Jan 26 20:39:45 Tower kernel: ata9: hard resetting link
Jan 26 20:39:45 Tower kernel: ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 26 20:39:55 Tower kernel: ata9.00: qc timeout (cmd 0xec)
Jan 26 20:39:55 Tower kernel: ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Jan 26 20:39:55 Tower kernel: ata9.00: revalidation failed (errno=-5)
Jan 26 20:39:55 Tower kernel: ata9: limiting SATA link speed to 3.0 Gbps
Jan 26 20:39:55 Tower kernel: ata9: hard resetting link
Jan 26 20:39:56 Tower kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jan 26 20:39:56 Tower kernel: ata9.00: configured for UDMA/133
Jan 26 20:39:56 Tower kernel: ata9: EH complete

That isn't enough for me to figure it out either but if you post the rest of the syslog I will show you.

Attached

syslog.txt

Jan 26 12:05:08 Tower kernel: ata9.00: ATA-8: OCZ-VERTEX3 MI, OCZ-46Y80W746F58WZU9, 2.25, max UDMA/133
Jan 26 12:05:34 Tower emhttp: OCZ-VERTEX3_MI_OCZ-46Y80W746F58WZU9 (sdf) 117220792
Jan 26 12:05:34 Tower emhttp: import 30 cache device: sdf

Crap. That's my cache drive, and it's never given me any issues. What should I do?

Crap. That's my cache drive, and it's never given me any issues. What should I do?

Check connection.

It's on that damn marvell card 

 

As soon as my parity is done rebuilding I'm removing that turd.

Marvell card is in the garbage where it belongs. I had all sorts of troubling things going on even with VT-D disabled.

The curious thing is that some people have no problems with them at all.

 

That is odd.

 

Found this guy on the wiki: https://www.amazon.com/gp/product/B005B0A6ZS/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

 

16 bucks shipped. Too cheap to pass up. Working great through heavy loads.