infamousmatic

.

.

.

.

.

.

.

.

Supermicro + Cables and 3TB HDD's have been sold. All other items are still available. Original post updated to reflect items still for sale.

.

.

all items have been sold. thank you Lime Tech community.

bump!

I have another set i'm willing to let go at $180 shipped within the continental US. Matches offers for the same set on eBay but I would rather avoid seller fees. Contact me via PM if interested.

Price bump, 190 shipped within continental US; or make an offer!

I have for sale two (2) 3TB Western Digital EZRX Hard Drives. These drives are brand new and have seen no use whatsoever. They were to be used as spares in the event one of my unraid server's drives crashed but have since began transition to 4TB drives. Drives are bare and will come with no cables whatsoever. I'm attempting to sell here before listing them on eBay (to avoid those horrendous eBay seller fees!). On eBay, I carry a 100% seller rating; feel free to PM me for proof. Drives will be packed in anti-static bags, wrapped in bubble wrap individually and packaged in a box with plenty of cushion. Shipping will be USPS Priority anywhere within the Continental US. Both drives for $200 shipped but willing to entertain offers. All payments must be made via PayPal. Please feel free to contact me via PM or post any questions on here. Thanks! edit: link to drive on newegg: http://www.newegg.com/Product/Product.aspx?Item=N82E16822136874

update. i forgot i had this issue when i first built the server. for some odd reason, i've always had issue with ONE drive in a drive cage i've used a molex splitter on. after switching the molex splitter to another cage and running the cage that housed the erroneous drive directly off the power supply's molex plug, all is well in the unraid world again. this is a very irritating issue that hasn't happened in well over a year. guess i'll try to upgrade my cabling!

reseated all sata cables connected to the cage that houses all three of the st2000dm001 drives and no change. i was able to figure out which of the three drives it was by using the ata_devices script recommended to another user. what would be the next course of action..? again, parity sync is working but VERY slow (1.54 MB/s). here is another copy of the syslog if necessary edit: changed out the sata cable for the drive and still showing the same errors and slow parity sync.. syslog.zip

again, took out the 2tb drive, put in the 3tb, assigned it as parity drive, started parity sync. here is the syslog. syslog.zip

the only thing i moved around was simply removing the drive cage with the 2tb drive, replacing it with the 3tb drive and putting it back in. nothing else was moved. i re-installed the 2tb drive after seeing these errors and i am still seeing the same as the snippet shows. i'll shut it down, put the 3tb back in, and post a full syslog. give me a few minutes.

i checked to be sure i have the latest firmware on my supermicro card and i do. everything else is working perfectly fine, except that drive..

recently upgraded my 2tb parity drive with a pre-cleared 3tb drive, running latest 5.0-rc i shut down server, took out 2tb drive, replace with 3tb drive, assigned drive in unraid webui, started parity sync. it has been crawling and fluctuating between 2 MB/s to 5 MB/s. the following messages have been displaying in the log and i'm sure they explain what's going on but i dont know what they mean: May 24 09:38:00 Tower kernel: ata2.00: configured for UDMA/33 May 24 09:38:00 Tower kernel: ata2: EH complete May 24 09:38:00 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen May 24 09:38:00 Tower kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed May 24 09:38:00 Tower kernel: ata2: SError: { Persist HostInt PHYRdyChg 10B8B } May 24 09:38:00 Tower kernel: ata2.00: failed command: READ DMA EXT May 24 09:38:00 Tower kernel: ata2.00: cmd 25/00:00:a0:42:35/00:02:00:00:00/e0 tag 0 dma 262144 in May 24 09:38:00 Tower kernel: res 50/00:00:df:cd:79/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) May 24 09:38:00 Tower kernel: ata2.00: status: { DRDY } May 24 09:38:00 Tower kernel: ata2: hard resetting link May 24 09:38:05 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) May 24 09:38:05 Tower kernel: ata2.00: configured for UDMA/33 May 24 09:38:05 Tower kernel: ata2: EH complete May 24 09:38:05 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen May 24 09:38:05 Tower kernel: ata2.00: irq_stat 0x01400000, PHY RDY changed May 24 09:38:05 Tower kernel: ata2: SError: { Persist HostInt PHYRdyChg 10B8B } May 24 09:38:05 Tower kernel: ata2.00: failed command: READ DMA EXT May 24 09:38:05 Tower kernel: ata2.00: cmd 25/00:00:a0:7a:35/00:02:00:00:00/e0 tag 0 dma 262144 in May 24 09:38:05 Tower kernel: res 50/00:00:df:05:7a/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) May 24 09:38:05 Tower kernel: ata2.00: status: { DRDY } May 24 09:38:05 Tower kernel: ata2: hard resetting link May 24 09:38:10 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) May 24 09:38:10 Tower kernel: ata2.00: configured for UDMA/33 May 24 09:38:10 Tower kernel: ata2: EH complete May 24 09:38:10 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x90a00 action 0xe frozen May 24 09:38:10 Tower kernel: ata2.00: irq_stat 0x01400000, PHY RDY changed May 24 09:38:10 Tower kernel: ata2: SError: { Persist HostInt PHYRdyChg 10B8B } May 24 09:38:10 Tower kernel: ata2.00: failed command: READ DMA EXT May 24 09:38:10 Tower kernel: ata2.00: cmd 25/00:00:a0:c0:35/00:02:00:00:00/e0 tag 0 dma 262144 in May 24 09:38:10 Tower kernel: res 50/00:00:df:4b:7a/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) May 24 09:38:10 Tower kernel: ata2.00: status: { DRDY } May 24 09:38:10 Tower kernel: ata2: hard resetting link the 3tb drive is connected via a supermicro AOC-SASLP-MV8 card. any help would be appreciated.