Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] All Drives have errors

Featured Replies

Hi All, 


I shut down my server to add a Network Card, when I booted the server back up one of the disks was missing, I suspect I dislodged the SATA cable by mistake. 


The disk then became disabled in the array, I shut down, reset all the cables and the disk came back up in disabled mode. 


I restart in maintenance mode to run smart tests - everything seemed fine - I removed it from the array and added it back in. Then rebuilt the array, no errors were reported. 


However, now i seems to have some XFS errors across all disks: 

Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x11a0df168 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x697e9f18 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x697e9f18 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x697e9f18 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x653bd0d8 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x653bd0d8 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x653bd0d8 len 32 error 5
Jul 15 10:06:12 Tower kernel: XFS (md2): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x653bd0d8 len 32 error 5
Jul 15 10:06:13 Tower dhcpcd[3442]: br1: using IPv4LL address 169.254.222.50

 

 

All drives appear to have errors now, i've attached the diagnostic files from before and after

  • Jul 14 - While disk was disabled. 
  • Jul 15 - After array was rebuilt 

 

Any advice on what I should do here? 

 

Thanks!

Drives.jpg

tower-diagnostics-20210715-1011.zip tower-diagnostics-20210714-1730.zip

  • Community Expert

This SATA controller is being passed through to the Win10 VM:

 

49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
    DeviceName: X570/590 SATA1
    Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
    Kernel driver in use: vfio-pci
    Kernel modules: ahci

 

So when the VM starts Unraid loses access to it and all the connected disks.

  • Author

OMG! Have i seriously just been this stupid!🙄 

This is next level dumb !  I moved my USB PCI card updated VM must have check the SATA controller too somehow. 

 

I shall remove that and hopefully my problems will go away

Screenshot 2021-07-15 151256.jpg

  • Author
46 minutes ago, JorgeB said:

This SATA controller is being passed through to the Win10 VM:

 


49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51)
    DeviceName: X570/590 SATA1
    Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901]
    Kernel driver in use: vfio-pci
    Kernel modules: ahci

 

So when the VM starts Unraid loses access to it and all the connected disks.

 

Hi JorgeB,

 

thank you so much for taking the time to review my logs i really appreicate it. 

 

This is 100% a classic case of dumb user error! 

 

I can confirm its all working well now, once i gave the sata contoller and the disks back to unraid..... 

 

thank you again! 

  • ChatNoir changed the title to [Solved] All Drives have errors

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.