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.

Disks unmountable after changing cpu and mobo

Featured Replies

Last night I had an electrical storm and my unraid server got at least partially fried. I was up at the time and there was a really loud crack of lightning and I heard a loud pop over from near my server. After testing I found that my Modem and server got fried. They also both smelled like burnt electronics. I was able to transplant the hard drives and boot flash drive into a new PC and they seemed to work and I could access my files. However when I tried transfer a large file from one of the drives it lost connection and when I restarted my array through the webgui it showed as unmountable. After troubleshooting including rebooting and starting the array a couple times now all my drives show as unmountable. Is there any way that I can get these drives to mount and recover my data?

  • Author

Just looked through the logs and it shows that it doesn't recognize the file system, however I'm pretty sure that the file system is still fine on those drives. 

  • Community Expert

Tools -> Diagnostics

  • Community Expert

It doesn't look good, do you know what filesystem they were?

  • Author
On 6/19/2017 at 3:37 AM, johnnie.black said:

Tools -> Diagnostics

Yes, the storage disks were xfs and I believe the cache drive was btrfs.

  • Community Expert

For the cache try btrfs restore:

 

For the data disks, try running xfs_repair in read-only mode on them, start the array in maintenance mode and in the console/ssh type:

 

xfs_repair -vn /dev/mdX

 

X = disk number

 

Depending on the output remove the n to attempt a repair:

 

xfs_repair -v /dev/mdX

 

 

 

  • Author

I'm guessing that my drives are hosed... The xfs_repair just keeping searching for the secondary super block for hours with no end in sight.

btrfs repair.png

xfs repair.png

Edited by yosarianilives

  • Community Expert

Something serious happened to those disks, let it run till the end of the disk but it should have found a backup superblock much sooner.

As for the cache you're not following the btrfs restore instructions I linked.

Archived

This topic is now archived and is closed to further replies.

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.