February 25, 20242 yr Hi all, Unfortunately I cannot figure out what is wrong with my system. It worked wonderfully for 3 years but it just started having issues. The syslog is full of storage related errors, some are definitely the cache (sdc) but I am not sure about the rest. What I've done so far: At some point the usb drive would not boot UNRAID anymore, but after replacing all bz files with those from the release, it was back to normal. (I think this is not directly related to my issues) Windows shows the usb drive to have errors, but when I ask it to fix it, it rescans for errors and says it is fine. Ran BTFS diagnostics, all without fault. SMART on the cache indicates at least a few errors, HDDs are fine. Please find attached the anonymised diagnostics from yesterday and also the syslog till crashing of the server. (To this regard: maybe it did not crash? I see logs that one of my access points (the one that my NAS is connected to) claimed the IP address before everything went silent. But then again, the logs show that several times, also during availability of the server. This would, however, explain why sometimes I cannot reach my server and waiting a bit makes it reachable again. In any case, it would be great for you guys to take a loot at my logs and diagnostics. I almost have a new build ready (shopping cart is filling up), but I don't think it should be necessary... Thanks! Best, Benedikt nas-diagnostics-20240224-1421.zip syslog.txt
February 25, 20242 yr Community Expert Solution Feb 24 22:36:33 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 24 22:36:33 NAS kernel: ata1.00: irq_stat 0x40000001 Feb 24 22:36:33 NAS kernel: ata1.00: failed command: READ DMA EXT Feb 24 22:36:33 NAS kernel: ata1.00: cmd 25/00:c0:20:18:d3/00:06:0e:00:00/e0 tag 14 dma 884736 in Feb 24 22:36:33 NAS kernel: res 51/40:c0:20:18:d3/00:06:0e:00:00/e0 Emask 0x9 (media error) Feb 24 22:36:33 NAS kernel: ata1.00: status: { DRDY ERR } Feb 24 22:36:33 NAS kernel: ata1.00: error: { UNC } Feb 24 22:36:33 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 24 22:36:33 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 24 22:36:33 NAS kernel: ata1.00: configured for UDMA/133 Constant issues with the cache device, check/replace cables, also see this: https://forums.unraid.net/topic/137795-6115-issues-with-btrfs-cache-after-ssds-replacement-and-hw-upgrade/?do=findComment&comment=1265949
February 28, 20242 yr Author Thank you. I have replaced the SATA cable with a known good cable, no betterment. I also purchased a completely new cable and the errors are not gone (though it has not crashed yet, but the server has only been running for 10 hrs). Here an excerpt from syslog: Quote Feb 28 07:25:09 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 28 07:25:09 NAS kernel: ata1.00: irq_stat 0x40000001 Feb 28 07:25:09 NAS kernel: ata1.00: failed command: READ DMA EXT Feb 28 07:25:09 NAS kernel: ata1.00: cmd 25/00:48:58:18:d3/00:05:0e:00:00/e0 tag 30 dma 692224 in Feb 28 07:25:09 NAS kernel: res 51/40:48:58:18:d3/00:05:0e:00:00/e0 Emask 0x9 (media error) Feb 28 07:25:09 NAS kernel: ata1.00: status: { DRDY ERR } Feb 28 07:25:09 NAS kernel: ata1.00: error: { UNC } Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: configured for UDMA/133 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#30 Sense Key : 0x3 [current] Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#30 ASC=0x11 ASCQ=0x4 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#30 CDB: opcode=0x28 28 00 0e d3 18 58 00 05 48 00 Feb 28 07:25:09 NAS kernel: I/O error, dev sdc, sector 248715352 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2 Feb 28 07:25:09 NAS kernel: ata1: EH complete Feb 28 07:25:09 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 28 07:25:09 NAS kernel: ata1.00: irq_stat 0x40000001 Feb 28 07:25:09 NAS kernel: ata1.00: failed command: READ DMA Feb 28 07:25:09 NAS kernel: ata1.00: cmd c8/00:08:80:1a:d3/00:00:00:00:00/ee tag 7 dma 4096 in Feb 28 07:25:09 NAS kernel: res 51/40:08:80:1a:d3/00:00:00:00:00/ee Emask 0x9 (media error) Feb 28 07:25:09 NAS kernel: ata1.00: status: { DRDY ERR } Feb 28 07:25:09 NAS kernel: ata1.00: error: { UNC } Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: configured for UDMA/133 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#7 Sense Key : 0x3 [current] Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#7 ASC=0x11 ASCQ=0x4 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#7 CDB: opcode=0x28 28 00 0e d3 1a 80 00 00 08 00 Feb 28 07:25:09 NAS kernel: I/O error, dev sdc, sector 248715904 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 28 07:25:09 NAS kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 57144, flush 0, corrupt 3, gen 0 Feb 28 07:25:09 NAS kernel: ata1: EH complete Feb 28 07:25:09 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 28 07:25:09 NAS kernel: ata1.00: irq_stat 0x40000001 Feb 28 07:25:09 NAS kernel: ata1.00: failed command: READ DMA Feb 28 07:25:09 NAS kernel: ata1.00: cmd c8/00:08:80:1a:d3/00:00:00:00:00/ee tag 10 dma 4096 in Feb 28 07:25:09 NAS kernel: res 51/40:08:80:1a:d3/00:00:00:00:00/ee Emask 0x9 (media error) Feb 28 07:25:09 NAS kernel: ata1.00: status: { DRDY ERR } Feb 28 07:25:09 NAS kernel: ata1.00: error: { UNC } Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: configured for UDMA/133 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#10 Sense Key : 0x3 [current] Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#10 ASC=0x11 ASCQ=0x4 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#10 CDB: opcode=0x28 28 00 0e d3 1a 80 00 00 08 00 Feb 28 07:25:09 NAS kernel: I/O error, dev sdc, sector 248715904 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 28 07:25:09 NAS kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 57145, flush 0, corrupt 3, gen 0 Feb 28 07:25:09 NAS kernel: ata1: EH complete Feb 28 07:25:09 NAS kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 28 07:25:09 NAS kernel: ata1.00: irq_stat 0x40000001 Feb 28 07:25:09 NAS kernel: ata1.00: failed command: READ DMA Feb 28 07:25:09 NAS kernel: ata1.00: cmd c8/00:08:80:1a:d3/00:00:00:00:00/ee tag 15 dma 4096 in Feb 28 07:25:09 NAS kernel: res 51/40:08:80:1a:d3/00:00:00:00:00/ee Emask 0x9 (media error) Feb 28 07:25:09 NAS kernel: ata1.00: status: { DRDY ERR } Feb 28 07:25:09 NAS kernel: ata1.00: error: { UNC } Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: supports DRM functions and may not be fully accessible Feb 28 07:25:09 NAS kernel: ata1.00: configured for UDMA/133 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#15 Sense Key : 0x3 [current] Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#15 ASC=0x11 ASCQ=0x4 Feb 28 07:25:09 NAS kernel: sd 2:0:0:0: [sdc] tag#15 CDB: opcode=0x28 28 00 0e d3 1a 80 00 00 08 00 Feb 28 07:25:09 NAS kernel: I/O error, dev sdc, sector 248715904 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 28 07:25:09 NAS kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 57146, flush 0, corrupt 3, gen 0 Also thanks for providing your link. I don't think this relates to my issue, but I will try their method soon regardless. But I think this might be a good time to upgrade to a 1TB cache drive. If the issue still persists then, the motherboard must be faulty. Could the issue (see syslog attached in original post) also be something else? I never checked my syslog in the past so I am unsure whether these were filling the log up for a long time before the crashes started, too. Edited February 28, 20242 yr by benediktleb
February 28, 20242 yr Community Expert 2 hours ago, benediktleb said: Could the issue (see syslog attached in original post) also be something else? It could, but you should fix that first.
March 3, 20242 yr Author Thanks @JorgeB. I replaced the drive (good time to increase capacity, too!) and the errors and reboots are a goner.
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.