I just upgraded from 4.7 to 5.0-rc3 and when the server came back up one of my disks was missing - "Stopped. Missing disk."

 

It is an Intel SS4200-E that I have been running unraid on for a few years now and running 4.7 for a year with no known issues.  I tried selecting the drive (sdc) from the drop down on the main screen where it should be but it didnt seem to do anything.  Attached is my syslog.  I disabled any addons from the go script and rebooted with no change.  The drive is a WDC_WD20EARS. 

 

This stands out in the syslog or maybe it is just a consequence of the drive being missing:

(I removed a bunch of these redundant errors from the syslog to reduce the attachment size)

 

May 19 13:24:47 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

May 19 13:24:47 Tower kernel: ata4.00: irq_stat 0x40000001

May 19 13:24:47 Tower kernel: ata4.00: failed command: READ DMA EXT

May 19 13:24:47 Tower kernel: ata4.00: cmd 25/00:01:af:88:e0/00:00:e8:00:00/e0 tag 0 dma 512 in

May 19 13:24:47 Tower kernel:          res 51/01:01:af:88:e0/00:00:e8:00:00/e0 Emask 0x1 (device error)

May 19 13:24:47 Tower kernel: ata4.00: status: { DRDY ERR }

May 19 13:24:47 Tower kernel: ata4.00: configured for UDMA/33

May 19 13:24:47 Tower kernel: sd 4:0:0:0: [sdc] Unhandled sense code

May 19 13:24:47 Tower kernel: sd 4:0:0:0: [sdc]  Result: hostbyte=0x00 driverbyte=0x08

May 19 13:24:47 Tower kernel: sd 4:0:0:0: [sdc]  Sense Key : 0x3 [current] [descriptor]

May 19 13:24:47 Tower kernel: Descriptor sense data with sense descriptors (in hex):

May 19 13:24:47 Tower kernel:        72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00

May 19 13:24:47 Tower kernel:        e8 e0 88 af

May 19 13:24:47 Tower kernel: sd 4:0:0:0: [sdc]  ASC=0x13 ASCQ=0x0

May 19 13:24:47 Tower kernel: sd 4:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 e8 e0 88 af 00 00 01 00

May 19 13:24:47 Tower kernel: end_request: I/O error, dev sdc, sector 3907029167

May 19 13:24:47 Tower kernel: Buffer I/O error on device sdc1, logical block 3907029104

May 19 13:24:47 Tower kernel: ata4: EH complete

 

When I roll back to 4.7 everything seems to work fine.  I just noticed I havent done a parity check in a year - could that have anything to do with it?  Maybe if I do it will uncover a disk problem?  I am currently running a parity check.

 

Any help or insight would be appreciated. 

 

Thanks,

 

Mark

syslog.txt

Here is my disk status before the upgrade (from 4.7)

The recent Parity Check came back fine.

 

Thanks Mark