Jump to content

Drive become Unmountable: Unsupported or no file system after relocation of SATA Port.


Go to solution Solved by JorgeB,

Recommended Posts

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.

Link to comment
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.

Link to comment
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.

 

image.thumb.png.ff281525dcf039143aebf47cc32cdadd.png

Link to comment
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.

Link to comment
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

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...