I replaced a drive after encountering some issues with it. The background on that is here: https://forums.unraid.net/topic/91524-solved-unmountable-no-file-system/

 

 

I got my new disk, precleared it, then replaced the defective disk. 

 

Issue 1: Right after the parity rebuild, another disk failed

Issue 2: 4 of my disks (including the failed disk) have the "Unmountable: No file system" message. The error counts on the other disks that did not fail are now >8,000,000

 

I'm not sure what to do at this point. I'm afraid if I do anything I may dig myself into a deeper hole. Diags attached. 

 

 

 

server-diagnostics-20200521-0917.zip

Edited May 27, 20206 yr by squishee

Problems with the onboard SATA controller, quite common with some Ryzen boards, there are some reports that the newer kernel on v6.9-beta1 helps, upgrade reboot and post new diags after array start.

After updating, unraid is saying that disk 7 is missing, however, I see it under unassigned devices. I'm a little worried now because I still need to rebuild disk 3. 

server-diagnostics-20200523-1551.zip

There's a problem identifying that disk, try replacing/swapping both cables.

 

May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001
May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA
May 23 15:50:05 server kernel: ata10.00: cmd c8/00:20:00:00:00/00:00:00:00:00/e0 tag 10 dma 16384 in
May 23 15:50:05 server kernel:         res 61/04:20:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR }
May 23 15:50:05 server kernel: ata10.00: error: { ABRT }
May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored)
May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 Sense Key : 0x5 [current]
May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 ASC=0x21 ASCQ=0x4
May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
May 23 15:50:05 server kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
May 23 15:50:05 server kernel: ata10: EH complete
May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001
May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA
May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 12 dma 4096 in
May 23 15:50:05 server kernel:         res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR }
May 23 15:50:05 server kernel: ata10.00: error: { ABRT }
May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored)
May 23 15:50:05 server kernel: ata10: EH complete
May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001
May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA
May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 7 dma 4096 in
May 23 15:50:05 server kernel:         res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR }
May 23 15:50:05 server kernel: ata10.00: error: { ABRT }
May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored)
May 23 15:50:05 server kernel: ata10: EH complete
May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001
May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA
May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 28 dma 4096 in
May 23 15:50:05 server kernel:         res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR }
May 23 15:50:05 server kernel: ata10.00: error: { ABRT }
May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored)
May 23 15:50:05 server kernel: ata10: EH complete
May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001
May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA
May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 18 dma 4096 in
May 23 15:50:05 server kernel:         res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR }
May 23 15:50:05 server kernel: ata10.00: error: { ABRT }

 

Thanks Johnnie, that did the trick. The disk was detected and I was able to successfully rebuild the failed drive on a new disk. One new issue though: I'm missing some files on my user shares. When I check the disk itself, I see them as expected. I tried checking the settings to see if somehow it was excluding some disks but that doesn't seem like the issue. Any idea how I can fix this?

server-diagnostics-20200526-1109.zip

Check filesystem on disk3:

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

I ran the --check option and got the following results: https://pastebin.com/RxY7Szbu 

 

I see some errors but not sure how to proceed. 

21 found corruptions can be fixed only when running with --rebuild-tree

You need to use --rebuild-tree, it will take several hours.

 

 

It just finished and appears to have done the trick. Thanks for your help as always!