maxse Posted March 3, 2017 Share Posted March 3, 2017 (edited) Hi guys, I need your help please. My unraid has been working great for many years and I have the 5.0.6 version installed now. I am starting to run low on space so I purchased an 8tb seagate archive drive to add to my array as a parity (currently my largest size is 6tb). Well when I stop the array and click on the drop down box the drive appears, as soon as I actually click on it, the drive completely disappears. I have to reboot the computer to get it to appear again in the drop down section, but again, as soon as I select it, it disappears again and my previous party drive still remains selectable as the only drive. Can someone please help me out with this? I have never had an issue like this happen before ad I have 8 drives there now! Syslog. This keeps repeating... Mar 3 00:02:21 Tower syslogd 1.4.1: restart. Mar 3 00:02:21 Tower logger: /etc/rc.d/rc.inet1: List of interfaces: 'eth0' Mar 3 00:02:21 Tower kernel: klogd 1.4.1, log source = /proc/kmsg started. Mar 3 00:02:21 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Mar 3 00:02:21 Tower kernel: 00 00 00 00 Mar 3 00:02:21 Tower kernel: sd 9:0:0:0: [sdk] Mar 3 00:02:21 Tower kernel: ASC=0x0 ASCQ=0x0 Mar 3 00:02:21 Tower kernel: sd 9:0:0:0: [sdk] CDB: Mar 3 00:02:21 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Mar 3 00:02:21 Tower kernel: ata8: EH complete Mar 3 00:02:21 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 3 00:02:21 Tower kernel: ata8.00: irq_stat 0x40000001 Mar 3 00:02:21 Tower kernel: ata8.00: failed command: READ DMA Mar 3 00:02:21 Tower kernel: ata8.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in Mar 3 00:02:21 Tower kernel: res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 3 00:02:21 Tower kernel: ata8.00: status: { DRDY ERR } Mar 3 00:02:21 Tower kernel: ata8.00: error: { ABRT } Mar 3 00:02:21 Tower kernel: ata8.00: configured for UDMA/133 (device error ignored) Mar 3 00:02:21 Tower kernel: ata8: EH complete Mar 3 00:02:21 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 3 00:02:21 Tower kernel: ata8.00: irq_stat 0x40000001 Mar 3 00:02:21 Tower kernel: ata8.00: failed command: READ DMA Mar 3 00:02:21 Tower kernel: ata8.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in Mar 3 00:02:21 Tower kernel: res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 3 00:02:21 Tower kernel: ata8.00: status: { DRDY ERR } Mar 3 00:02:21 Tower kernel: ata8.00: error: { ABRT } Mar 3 00:02:21 Tower kernel: ata8.00: configured for UDMA/133 (device error ignored) Mar 3 00:02:21 Tower kernel: ata8: EH complete Mar 3 00:02:21 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 3 00:02:21 Tower kernel: ata8.00: irq_stat 0x40000001 Mar 3 00:02:21 Tower kernel: ata8.00: failed command: READ DMA Mar 3 00:02:21 Tower kernel: ata8.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in Mar 3 00:02:21 Tower kernel: res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) Mar 3 00:02:21 Tower kernel: ata8.00: status: { DRDY ERR } Mar 3 00:02:21 Tower kernel: ata8.00: error: { ABRT } Mar 3 00:02:21 Tower kernel: ata8.00: configured for UDMA/133 (device error ignored) Mar 3 00:02:21 Tower kernel: ata8: EH complete Mar 3 00:02:21 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Edited March 3, 2017 by maxse Quote Link to comment
miniwalks Posted March 3, 2017 Share Posted March 3, 2017 Those errors generally indicate controller failure;Can you please try the following and report back?1) 8tb in other PC2) 8tb in unraid - different port3) other drive in same port as current 8tbCheersSent from my iPhone using Tapatalk Quote Link to comment
maxse Posted March 9, 2017 Author Share Posted March 9, 2017 Thanks miniwalks I tried what you said and had the same issue even swapping the drive into a hard drive cage that currently works. I figured it was a bad drive and ordered a new one which just came in and now all is working well. So it was just a bad drive that came dead. Thanks so much Quote Link to comment
miniwalks Posted March 9, 2017 Share Posted March 9, 2017 Happy to help mate!Sent from my iPhone using Tapatalk Quote Link to comment
Recommended Posts
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.