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.

[Partially Solved] Trouble Accessing Share after 4.7 =>5.05 Upgrade

Featured Replies

I purchased a new AVS10 server and migrated my old drives to the new server.  6 drive system (Parity + 5x2 TB drives). 

 

I have run the Permissions Utility.  However, I cannot access certain folders that reside on disk 1. It appears I can browse all folders/files on other disks--but any folders which contain files that reside on disk 1 results in a Windows error.

 

I have re-run permissions, no change.

I re-checked parity (although no errors were showing), no change

I went so far as to replace disk 1 with a spare and rebuild the array, no change. 

 

In running the Permissions utility, it seems to take 2-3 hours to go through disk 1, but the rest of disks are much faster.  This drive does have the most data on it (+/- 1.4 TB on a 2 TB drive).

 

On the Shares page (browsing to //tower), there is an "Orange Dot" next to the share.  If I click the file folder next to the share, I can see all the files which should be present (including those which reside on disk 1).

 

I am at a loss.  I use this Unraid Share as Storage for Media Files to serve to my HTPC (running Sage TV).  All movies/music/pictures which reside on disks 2-5 are visible to Sage (utilizing smb filepath referencing the shared unraid folder).  Nothing on disk 1 is visible to Sage.

 

Any help/ideas are appreciated. 

  • Author

Saturday Morning Bump.  Any help is appreciated is resolving this issue. 

 

Thanks.

It might be worth running a reiserfsck check of disk1 in case there is any sort of file system corruption.  The fact that the share has an orange dot means that at least some of the files in it are on your cache disk.  File system corruption would stop them being moved to the array disk.

  • Author

Thanks  Totally telnet/Linux noob.  Do I run it on /md1 (disk 1) or what that be my parity drive and I run it on /md2 ?

 

 

  • Author

Ran reiserfsck on /md1.  Output file scares me...  Says 16 found corruptions that can only be run with --rebuild--tree

 

Based on the reiserfsck tutorial page, I need some guidance. 

 

screenshot of the telnet session/results attached.

 

reiserfsck--gif.GIF.b3cb30202a0249ea8575b90c347ee8f4.GIF

  • Author

One more thing.  I added the cache drive a few days ago.  In order to troubleshoot, I unassigned the cache drive from the array.  The Share now has a green dot next to it in the unraid/shares menu.

Ran reiserfsck on /md1.  Output file scares me...  Says 16 found corruptions that can only be run with --rebuild--tree

 

Based on the reiserfsck tutorial page, I need some guidance. 

 

screenshot of the telnet session/results attached.

 

Run with rebuild-tree. See Check Disk Filesystems in my sig.

One more thing.  I added the cache drive a few days ago.  In order to troubleshoot, I unassigned the cache drive from the array.  The Share now has a green dot next to it in the unraid/shares menu.

 

It's green because there is nothing on the cache waiting for the mover.

  • Author

Thanks.  I ran --rebuild-tree.  I took over 5 hours (2TB drive) but I can now access the share drive.  Had about 6GB of data in the lost+found folder, so not sure what to do with that other than ignore it for now. 

 

Is there anything else I should run/do now?  Parity check shows good with no errors. 

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.