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.

Files are not visible in unraid

Featured Replies

Hi guys

 

Some of my files movies etc are not visible in unraid filemanager, krusader etc.

 

But i can see that my unraid is still full i got 68% of my array full

 

Plex is still able to play the files that are inviisble

 

Can someone help me please don't know what to do

unraid-diagnostics-20230107-0600.zip

Solved by JorgeB

  • Author
On 1/7/2023 at 6:08 AM, JorgeB said:

Check filesystem on disk1.

hi after doind a repair i got this

 

resetting inode 4801177989 nlinks from 10 to 9
Metadata corruption detected at 0x451c80, xfs_bmbt block 0x381ddff20/0x1000
libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x381ddff20/0x8
Metadata corruption detected at 0x451c80, xfs_bmbt block 0x303f8eb00/0x1000
libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x303f8eb00/0x8
Metadata corruption detected at 0x451c80, xfs_bmbt block 0x304204810/0x1000
libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x304204810/0x8
Metadata corruption detected at 0x451c80, xfs_bmbt block 0x30dcb27f8/0x1000
libxfs_bwrite: write verifier failed on xfs_bmbt bno 0x30dcb27f8/0x8
Maximum metadata LSN (1713531926:523524561) is ahead of log (8:3564918).
Format log to cycle 1713531929.
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Refusing to write a corrupt buffer to the data device!
xfs_repair: Lost a write to the data device!

fatal error -- File system metadata writeout failed, err=117.  Re-run xfs_repair.

 

 

 

What should i do ?

 

thx

I would wait for JorgeB to reply, but I think you have a failing drive.

 

MrGrey.

  • Community Expert

Post new diags please.

  • Community Expert

Run xfs_repair again without -n, if it fails post new diags.

  • Author
1 minute ago, JorgeB said:

Run xfs_repair again without -n, if it fails post new diags.

do i need to run it again with the -d option ?

 

thx

  • Community Expert

Don't know a -d option, run without any flags or with just -v.

  • Community Expert

Don't see anything in the log, did you run it using the GUI? Did if fail again?

  • Author

i run it trhought gui under the disk 1

 

 

image.png.c4f37891ac63ccddca5fe15a4f953784.png

 

 

Also i now got a lost%found folder with like 270Go

 

What should i do with that ?

 

 

thx

  • Community Expert
15 minutes ago, francrouge said:

Also i now got a lost%found folder with like 270Go

lost+found is where filesystem repair puts anything it can't figure out. Files without folders, files and folders without names. You might be able to figure what type of data is in a particular file with the linux 'file' command.

  • Author
4 hours ago, trurl said:

lost+found is where filesystem repair puts anything it can't figure out. Files without folders, files and folders without names. You might be able to figure what type of data is in a particular file with the linux 'file' command.

ok so i should get all the data in that folder and replace it to the good spot then ?

 

Thx again for all the help

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.