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.

Unmountable disk after logic board change

Featured Replies

Hi all, 

I swapped the case and changed the mainboard. After the first boot I get one of my 2 drives unmountable.

I attach here my log.

 

srv02-diagnostics-20230721-1653.zip

Solved by itimpi

  • Community Expert

Log is being spammed with PCIe errors, see here then reboot and post new diags to see if it helps.

Do you have any parity? It's a pain but you could stop the Array > Unassign one of the data disks > Start Array.
From here it should emulate that disk so then Stop Array > Reassign the Disk > Start Array and this should begin rebuilding the disk.

 

I'm not the best at reading logs, but following and wishing you the best,

-Darrell

  • Community Expert
3 minutes ago, DirtyDarrell said:

From here it should emulate that disk so then Stop Array > Reassign the Disk > Start Array and this should begin rebuilding the disk.

Rebuilding won't usually help with unmountable disks, don't do that before posting new diags.

2 minutes ago, JorgeB said:

Rebuilding won't usually help with unmountable disks, don't do that before posting new diags.

Apologies for any wrong information.

 

-Darrell

  • Author

Do you think it’s related to the NVMe drive? I also read here that the issue may be caused by a bad sata cable. 
 

Here I post the error of corrupt drive that I see after boot 

 

IMG_3186.jpeg

  • Author

I solved the spam issue by adding pcie_aspm=off 

but I still have an unmountable disk

 

IMG_3241.HEIC

unraid unmountable.jpg

  • Community Expert

The command you used is wrong as you always need to include the partition number.  Ideally you should run the repair from the GUI as then the correct device id will be used.

  • Author

Ok, tried that

here's the log but the drive is still unmountable

1554299310_Screenshot2023-07-24alle18_17_15.thumb.png.dc3959aa06cd4e3ad366dcea5debf168.png

  • Community Expert
  • Solution

You ran with -n set which does a read-only check.   If you want any fix to be made then you need to remove the -n, and if it asks for -L then add that.   After that the repair should be done and the disk then mountable.

  • Author

Thank you, it worked!! :)

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.