July 6, 20233 yr I got one of my Drive become Unmountable: Unsupported or no file system after i reallocated it from onboard SATA to PCIE SATA. Also i did a gracefully shutdown but after boot up the parity doing resync and i dont dare to force shutdown to check on the Unsupport Drive connection. Since i had to wait for 2days for the Parity to complete Sync i've attach the Diagnostic file, hope someone could find out what might be the issue. Unraid was quite robust previously seems like there much fragile since 6.12 update.
July 7, 20233 yr Author 19 hours ago, JorgeB said: Please post the diagnostics. ts-p500-diagnostics-20230706-1610.zip Oooh Sorry forgot to attach the Diagnostic yesterday/ And heres the Check File System status. Edited July 7, 20233 yr by feins
July 7, 20233 yr Community Expert 3 hours ago, feins said: ts-p500-diagnostics-20230706-1610.zip 144.84 kB · 0 downloads Oooh Sorry forgot to attach the Diagnostic yesterday/ And heres the Check File System status. You need to run without the -n option or nothing will be done. On restarting in normal mode the drive should then mount.
July 7, 20233 yr Author 2 hours ago, itimpi said: You need to run without the -n option or nothing will be done. On restarting in normal mode the drive should then mount. Hi @itimpiI 've run Check Filesystem Status without -n and after normal reboot the Drive still Unmounted. Here is the latest Diagnostic after reboot. ts-p500-diagnostics-20230707-1658.zip
July 7, 20233 yr Community Expert Jul 7 16:56:54 TS-P500 kernel: ata3.00: exception Emask 0x10 SAct 0xc0000 SErr 0x400101 action 0x6 frozen Jul 7 16:56:54 TS-P500 kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 7 16:56:54 TS-P500 kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/fe:90:92:6d:78/09:00:74:00:00/40 tag 18 ncq dma 1309696 ou Jul 7 16:56:54 TS-P500 kernel: res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error) Jul 7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY } Jul 7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/02:98:90:77:78/06:00:74:00:00/40 tag 19 ncq dma 787456 out Jul 7 16:56:54 TS-P500 kernel: res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error) Jul 7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY } Jul 7 16:56:54 TS-P500 kernel: ata3: hard resetting link There's a problem with the device, try new cables or SATA port.
July 7, 20233 yr Author 58 minutes ago, JorgeB said: Jul 7 16:56:54 TS-P500 kernel: ata3.00: exception Emask 0x10 SAct 0xc0000 SErr 0x400101 action 0x6 frozen Jul 7 16:56:54 TS-P500 kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jul 7 16:56:54 TS-P500 kernel: ata3: SError: { RecovData UnrecovData Handshk } Jul 7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/fe:90:92:6d:78/09:00:74:00:00/40 tag 18 ncq dma 1309696 ou Jul 7 16:56:54 TS-P500 kernel: res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error) Jul 7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY } Jul 7 16:56:54 TS-P500 kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jul 7 16:56:54 TS-P500 kernel: ata3.00: cmd 61/02:98:90:77:78/06:00:74:00:00/40 tag 19 ncq dma 787456 out Jul 7 16:56:54 TS-P500 kernel: res 40/00:9c:90:77:78/00:00:74:00:00/40 Emask 0x10 (ATA bus error) Jul 7 16:56:54 TS-P500 kernel: ata3.00: status: { DRDY } Jul 7 16:56:54 TS-P500 kernel: ata3: hard resetting link There's a problem with the device, try new cables or SATA port. Ive just Tried relocated the cable and SATA port already. Here are the Check Filesystem Status without -n output.
July 7, 20233 yr Author 3 hours ago, JorgeB said: Post new diags to see if there still are hardware issues. ts-p500-diagnostics-20230707-2207.zip Heres the new Diagnostic
July 7, 20233 yr Community Expert Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00 Jul 7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Jul 7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jul 7 18:22:08 TS-P500 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Still issues on a different controller, assuming the cables are also not the same could just be a failing device.
July 7, 20233 yr Author 44 minutes ago, JorgeB said: Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#5 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00 Jul 7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Jul 7 18:22:08 TS-P500 kernel: sd 3:0:0:0: [sdd] tag#6 CDB: opcode=0x28 28 00 00 00 00 00 00 00 08 00 Jul 7 18:22:08 TS-P500 kernel: I/O error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jul 7 18:22:08 TS-P500 kernel: Buffer I/O error on dev sdd, logical block 0, async page read Still issues on a different controller, assuming the cables are also not the same could just be a failing device. I just replace the cable with another. Attach latest Diagnostic. ts-p500-diagnostics-20230707-2307.zip
July 8, 20233 yr Author 16 hours ago, JorgeB said: No ATA errors so far, try running xfs_repair again. Thanks, Finally its resolved.
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.