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.

Share has no files after rebuild

Featured Replies

I have an UNRaid server where shortly after rebuilding a failing drive another drive has failed.  I stopped the array, removed the device and restarted and noticed my shares now have no files.  The dockers can still pull files, but the share is blank. 

 

All of the files that where on this drive (and the array in general) are backed up elsewhere. I have checked the logs, and see it recommends I run xfs_repair on the emulated drive md4p1.  I have done this with -n, -v, and -vL and it cannot find any superblocks and just terminates with no other information.     Is there a way to repair the emulated drive to restore my share files so I can see what I need to restore from lost&found from my backups, or do I have to create a new configuration?  Any help or direction would be appreciated.  

nyarlathotep-diagnostics-20240108-1936.zip

Diagnostics shows disks 1 - 5 all mounted and with data, including missing/emulated disk4, cache and user shares also mounted and with data.

 

Also don't see any lost+found share.

 

Syslog does suggest running xfs_repair on emulated disk4. Did you try this from the webUI or from the command line? Sounds like you used the correct device regardless.

 

Can you mount original disk4 as an Unassigned Device?

 

Do you have any screenshots or anything that might help demonstrate the difference between your description and your diagnostics?

  • Author

I ran xfs-repair -n from the GUI and then then from the CLI.

 

I restarted the array, and the shares are back and populated.  But no it says I have an unmountable disk on md4p1 and offers to format.  Unfortunately, the files on another of the disks while present appear to be all corrupted as none of them will open in their respective apps compared to the backups I have.  Gets more and more interesting.  Logs say now to run xfs_repair on md5p1.

 

As for mounting the original disk, it is currently pulled from the array and I was going to check it with TestDisk to see if it can find anything.  When it was in the system it reused to mount from unassigned devices.

Edited by mklem

1 hour ago, mklem said:

unmountable disk on md4p1 and offers to format.

DO NOT FORMAT.

 

Check filesystem on disk4 and disk5, using the webUI. Be sure to capture the complete output and post it.

  • Author

Missed the 'run from the GUI part, but both drives exit out with "Sorry, could not find valid secondary superblock"

 

Looks like I may have to restore from backups?

Just now, mklem said:

Missed the 'run from the GUI part

Do you mean you didn't run it from the webUI? It is very easy to get the command wrong.

  • Author

I ran it from the CLI.  It ran overnight and came back with no superblocks found.   Drive 4 is still unmountable and all the files on drive 5 appear corrupted, or at least every PDF, doc, mp4, etc file I tried opening wouldn't work.

Run it from the webUI. Be sure to capture the output so you can post it.

  • Author

After a long time (I edited a lot of . out for brevity).

Disk 4

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Sorry, could not find valid secondary superblock

Exiting now.

Disk 5
 

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Sorry, could not find valid secondary superblock

Exiting now.

 

I have backups of all the data and replacement drives (Drive 4 is currently emulated).  Is it best to just format these and restore from backup?

I still don't understand why the diagnostics you posted at the beginning were so much better than this outcome.

 

Post new diagnostics with the array started.

  • Author

Here you go.  Checked the files on Disk 5 that are in the share and they all appear corrupted/unplayable/unreadable/etc compared to my backups.

 

 

nyarlathotep-diagnostics-20240110-1631.zip

I still don't get it unless there is some anomaly with diagnostics collection.

 

What do you get from command line with this?

df -h

 

  • Author

root@Nyarlathotep:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs           16G  466M   16G   3% /
tmpfs            32M  1.7M   31M   6% /run
/dev/sda1       1.9G  893M  1.1G  47% /boot
overlay          16G  466M   16G   3% /lib
overlay          16G  466M   16G   3% /usr
devtmpfs        8.0M     0  8.0M   0% /dev
tmpfs            16G     0   16G   0% /dev/shm
tmpfs           128M  1.4M  127M   2% /var/log
tmpfs           1.0M     0  1.0M   0% /mnt/disks
tmpfs           1.0M     0  1.0M   0% /mnt/remotes
tmpfs           1.0M     0  1.0M   0% /mnt/addons
tmpfs           1.0M     0  1.0M   0% /mnt/rootshare
/dev/md1p1      3.7T  2.2T  1.6T  59% /mnt/disk1
/dev/md2p1      1.9T  236G  1.6T  13% /mnt/disk2
/dev/md3p1      3.7T  1.9T  1.9T  51% /mnt/disk3
/dev/md5p1      3.7T  1.9T  1.8T  51% /mnt/disk5
/dev/nvme0n1p1  954G  152G  801G  16% /mnt/cache
shfs             13T  6.1T  6.8T  48% /mnt/user0
shfs             13T  6.1T  6.8T  48% /mnt/user
/dev/loop2       80G   38G   43G  47% /var/lib/docker

Disk4 not mounted and that agrees with the latest diagnostics. Disk5 is mounted but it was showing corruption, don't know why it won't repair. Maybe some edge case with xfs_repair.

 

You aren't on the latest version of Unraid so you might try repair again after upgrading, but release notes for .5 and .6 don't mention any updates to xfs.

 

3 hours ago, mklem said:

I have backups of all the data and replacement drives (Drive 4 is currently emulated).  Is it best to just format these and restore from backup?

That might be best. You would format the disks while they are in the array.

 

Disk4 doesn't appear in your diagnostics, so I can't tell if there is anything actually wrong with the physical disk or not.

 

You will either have to rebuild disk4 anyway since it is part of the current array configuration, or New Config and rebuild parity instead.

  • Author

I came to the same conclusion and decided my time was better spent getting the data moved from backup to the array rather than guess what had happened.   Disk 4 was pulled due to write errors and before I could rebuild it, I noticed my shares not mounting while it was being emulated and thus my original ask.

 

I appreciate the time, and thanks!

I wonder if memtest would show anything?

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.