Installed windows on unassigned drive, cache no longer mounts

tuxbass

By tuxbass
in General Support

Go to solution Solved by itimpi,

Recommended Posts

tuxbass Apprentice

tuxbass

Posted
Posted (edited)

System has following drives:
- 3x4TB HDDs (array)

- 500GB SSD (cache, sdb)

- 512GB unassigned nvme m.2

 

Installed Windows 11 directly onto the nvme and all looked fine. While in windows, the other drives weren't even listed in the 'My Computer' section, but I disabled SATA controller just in case.

 

Now when I booted back into Unraid, the cache drive no longer mounts: 

1477:Jul 26 15:58:52 srvr emhttpd: shcmd (42): mount -t xfs -o noatime,nouuid /dev/sdb1 /mnt/cache
1479:Jul 26 15:58:52 srvr kernel: XFS (sdb1): Mounting V5 Filesystem
1581:Jul 26 15:58:54 srvr root: mount: /mnt/cache: can't read superblock on /dev/sdb1.

What gives? Is it just a coincidence or windows managed to write something on that drive?

 

srvr-diagnostics-20230726-1603.zip

Edited by tuxbass
Link to comment
dlandon Veteran

dlandon

Posted
Posted

That drive is having issues: 

Jul 26 15:58:52 srvr kernel: XFS (sdb1): Mounting V5 Filesystem
Jul 26 15:58:52 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x80000008 SErr 0x480101 action 0x6 frozen
Jul 26 15:58:52 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jul 26 15:58:52 srvr kernel: ata3: SError: { RecovData UnrecovData 10B8B Handshk }
Jul 26 15:58:52 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:52 srvr kernel: ata3.00: cmd 61/00:18:fc:a5:21/06:00:1d:00:00/40 tag 3 ncq dma 786432 out
Jul 26 15:58:52 srvr kernel:         res 40/00:18:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:52 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:52 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:52 srvr kernel: ata3.00: cmd 61/00:f8:fc:9b:21/0a:00:1d:00:00/40 tag 31 ncq dma 1310720 ou
Jul 26 15:58:52 srvr kernel:         res 40/00:18:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:52 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:52 srvr kernel: ata3: hard resetting link
Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133
Jul 26 15:58:53 srvr kernel: ata3: EH complete
Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0xc000 SErr 0x400101 action 0x6 frozen
Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x0c000000, interface fatal error
Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:70:fc:9b:21/0a:00:1d:00:00/40 tag 14 ncq dma 1310720 ou
Jul 26 15:58:53 srvr kernel:         res 40/00:78:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:78:fc:a5:21/06:00:1d:00:00/40 tag 15 ncq dma 786432 out
Jul 26 15:58:53 srvr kernel:         res 40/00:78:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3: hard resetting link
Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133
Jul 26 15:58:53 srvr kernel: ata3: EH complete
Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0xc000 SErr 0x400101 action 0x6 frozen
Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:70:fc:a5:21/06:00:1d:00:00/40 tag 14 ncq dma 786432 out
Jul 26 15:58:53 srvr kernel:         res 40/00:78:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:78:fc:9b:21/0a:00:1d:00:00/40 tag 15 ncq dma 1310720 ou
Jul 26 15:58:53 srvr kernel:         res 40/00:78:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3: hard resetting link
Jul 26 15:58:53 srvr kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 26 15:58:53 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:53 srvr kernel: ata3.00: configured for UDMA/133
Jul 26 15:58:53 srvr kernel: ata3: EH complete
Jul 26 15:58:53 srvr kernel: ata3: limiting SATA link speed to 3.0 Gbps
Jul 26 15:58:53 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x6 SErr 0x400101 action 0x6 frozen
Jul 26 15:58:53 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jul 26 15:58:53 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:08:fc:9b:21/0a:00:1d:00:00/40 tag 1 ncq dma 1310720 ou
Jul 26 15:58:53 srvr kernel:         res 40/00:10:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:53 srvr kernel: ata3.00: cmd 61/00:10:fc:a5:21/06:00:1d:00:00/40 tag 2 ncq dma 786432 out
Jul 26 15:58:53 srvr kernel:         res 40/00:10:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:53 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:53 srvr kernel: ata3: hard resetting link
Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:54 srvr kernel: ata3.00: configured for UDMA/133
Jul 26 15:58:54 srvr kernel: ata3: EH complete
Jul 26 15:58:54 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x60 SErr 0x400100 action 0x6 frozen
Jul 26 15:58:54 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jul 26 15:58:54 srvr kernel: ata3: SError: { UnrecovData Handshk }
Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:28:fc:a5:21/06:00:1d:00:00/40 tag 5 ncq dma 786432 out
Jul 26 15:58:54 srvr kernel:         res 40/00:30:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:30:fc:9b:21/0a:00:1d:00:00/40 tag 6 ncq dma 1310720 ou
Jul 26 15:58:54 srvr kernel:         res 40/00:30:fc:9b:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:54 srvr kernel: ata3: hard resetting link
Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:54 srvr kernel: ata3.00: configured for UDMA/133
Jul 26 15:58:54 srvr kernel: ata3: EH complete
Jul 26 15:58:54 srvr kernel: ata3.00: exception Emask 0x10 SAct 0x300 SErr 0x400101 action 0x6 frozen
Jul 26 15:58:54 srvr kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jul 26 15:58:54 srvr kernel: ata3: SError: { RecovData UnrecovData Handshk }
Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:40:fc:9b:21/0a:00:1d:00:00/40 tag 8 ncq dma 1310720 ou
Jul 26 15:58:54 srvr kernel:         res 40/00:48:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:54 srvr kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jul 26 15:58:54 srvr kernel: ata3.00: cmd 61/00:48:fc:a5:21/06:00:1d:00:00/40 tag 9 ncq dma 786432 out
Jul 26 15:58:54 srvr kernel:         res 40/00:48:fc:a5:21/00:00:1d:00:00/40 Emask 0x10 (ATA bus error)
Jul 26 15:58:54 srvr kernel: ata3.00: status: { DRDY }
Jul 26 15:58:54 srvr kernel: ata3: hard resetting link
Jul 26 15:58:54 srvr kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Jul 26 15:58:54 srvr kernel: ata3.00: supports DRM functions and may not be fully accessible
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jul 26 15:58:54 srvr root: mount: /mnt/cache: can't read superblock on /dev/sdb1.

Check your cables and interface.

Link to comment
tuxbass Apprentice

tuxbass

Posted
  • Author
Posted (edited)
16 hours ago, dlandon said:

That drive is having issues:

Check your cables and interface.

I believe that is a red herring. The cache drive has been showing those errors for over a year now. Have tried changing the cables to no avail. It's not a show-stopper of an error so I've just learnt to live with it. Including diagnostics from ~ year ago when cache mounted just fine:

tower-diagnostics-20220606-2221.zip

Edited by tuxbass
Link to comment
tuxbass Apprentice

tuxbass

Posted
  • Author
Posted
2 hours ago, itimpi said:

This IS a showstopper as if the superblock cannot be read then the drive cannot be mounted.

  

Yes, agreed. My point was - could the Windows installation in this dual-boot setup have caused it, or it's just a coincidence and I'm really looking at another drive failure here? The timing is just too close for a coincidence, in my experience.

Link to comment
  • Solution
itimpi Grand Master

itimpi

Posted
  • Solution
Posted
7 minutes ago, tuxbass said:

  

Yes, agreed. My point was - could the Windows installation in this dual-boot setup have caused it, or it's just a coincidence and I'm really looking at another drive failure here? The timing is just too close for a coincidence, in my experience.

Do not see how as the error message suggests a physical failure to read the superblock.

 

The earlier messages are what we normally see when there is an issue with the SATA or power cabling to the drive.

Link to comment
tuxbass Apprentice

tuxbass

Posted
  • Author
Posted
Just now, itimpi said:

Do not see how as the error message suggests a physical failure to read the superblock.

Hence my question regarding installing Windows onto the unassigned m2 drive.

 

1 minute ago, itimpi said:

The earlier messages are what we normally see when there is an issue with the SATA or power cabling to the drive.

Yup, which I tried to solve some few years back with no luck, and decided to just turn a blind eye on.

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.

×
Go to topic listing