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.

unRAID Server Release 6.0-beta3-x86_64 Available

Featured Replies

 

2 full passes

I'm in no way qualified to make an assessment, just thought that would be good info to have in the thread.  Hopefully Tom is able to get to the bottom or it.

  • Replies 661
  • Views 149.7k
  • Created
  • Last Reply

Ive set this up on my main server to testing, seems i keep getting an error on my SSD cache drive!!

 

not sure if this is a bug, or something to do on my end.....

Any ideas?

 

Feb  8 16:43:16 Tower afpd[2878]: sys_getextattr_content(com.apple.metadata:kMDItemWhereFroms): error: Input/output error
Feb  8 16:43:16 Tower kernel: REISERFS warning (device sdj1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.metadata:kMDItemWhereFroms) associated with [702890 702984 0x0 SD]
Feb  8 16:43:16 Tower afpd[2878]: sys_getextattr_content(com.apple.metadata:kMDItemWhereFroms): error: Input/output error
Feb  8 16:43:16 Tower kernel: REISERFS warning (device sdj1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.metadata:kMDItemWhereFroms) associated with [702890 702984 0x0 SD]
Feb  8 16:43:17 Tower afpd[2878]: sys_getextattr_content(com.apple.metadata:kMDItemWhereFroms): error: Input/output error
Feb  8 16:43:17 Tower kernel: REISERFS warning (device sdj1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.metadata:kMDItemWhereFroms) associated with [702890 702984 0x0 SD]
Feb  8 16:43:25 Tower afpd[2878]: sys_getextattr_content(com.apple.metadata:kMDItemWhereFroms): error: Input/output error
Feb  8 16:43:25 Tower kernel: REISERFS warning (device sdj1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.metadata:kMDItemWhereFroms) associated with [702890 702984 0x0 SD]
Feb  8 16:43:25 Tower afpd[2878]: sys_getextattr_content(com.apple.TextEncoding): error: Input/output error
Feb  8 16:43:25 Tower kernel: REISERFS warning (device sdj1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.TextEncoding) associated with [702890 702993 0x0 SD]

 

It seems I only get this on the very first access of the cache drive from an apple computer. went back to 5.05 and tested again, and no error.....

 

Edit: I believe this was related to an Rsync back-up i did of my Flash on my main & test servers, Deleted these folders via ssh and all is good now.

Just to close out the process, all of the bugs APPEAR to be gone with plex off of Dom0....? I now have my server setup like this:

 

vXxN1KX.png

Pyratar, I wouldn't have participated except that I saw kernel crashes. Some kind of memory issue and/or cpu issue.

 

 

So I understand why you've been posting in here. Frankly I would opt to keep dom0 as plain as possible and put all the heavy library dependent software in a virtual machine.  Who knows what might have accidentally been replaced or what kind of shared library dependency issues are coming into play with Plex.  From what I saw, it was using allot of memory. Since I don't know the code, it could also have been requesting memory that cannot be paged out.

 

 

It seems other people are using very large amounts of memory or not using the XEN enabled options with plex x64.

 

 

Let's see how the simpler dom0 operates with cache_dirs.

I am confused now, in the forum map is shows this Note: please post version 6.0-beta bugs/issues up in the appropriate Announcement board thread.

However when I posted my problem with my disappearing shares I get told to post elsewhere, but in which forum are you now meant to post beta 3 from unraid 6 issues? If I have Xen issues I know I have to post in the Xen section, but I am confused about my disappearing shares?

 

Sorry not trying to be difficult I just want to have my shares back and I am getting desperate.

 

Thanks

 

MrLondon

@mrlondon

 

Sorry you are having issues buddy. I'm afraid that is the nature of beta software. If you're totally desperate v5 is nice and stable.

 

Perhaps we could use a v6 beta subforum? Or just create a thread in general support I guess.

 

Sent from my Nexus 5 using Tapatalk

 

It's strange that just a few people have had serious problems.  I'm amazed how stable the Unraid 6 releases have been for me - beta 3 has been up for a week with no problems and I've hammered it pretty hard.  CPU utilisation is incredibly low most of the time (2 or 3%).

 

Good luck Mr London.

 

Nic

I am confused now, in the forum map is shows this Note: please post version 6.0-beta bugs/issues up in the appropriate Announcement board thread.

However when I posted my problem with my disappearing shares I get told to post elsewhere, but in which forum are you now meant to post beta 3 from unraid 6 issues? If I have Xen issues I know I have to post in the Xen section, but I am confused about my disappearing shares?

 

Sorry not trying to be difficult I just want to have my shares back and I am getting desperate.

 

Thanks

 

MrLondon

MrLondon, here are my thoughts on this. I will start by saying I haven't read your other post. If you are running a vanilla beta 3 (meaning clean no plugins) and are having the issues then this is the right place. If you are running unclean, I would start in general support. My recommendation would be to remove/disable all plugins and see if your problem goes away. If it does then you would need to install one plugin at a time until the problem comes back and then start a thread in that plugin area.

 

Burt

ok i formatted my USB key, all vanilla, only copied over my config directory which is the normal procedure for an upgrade. So I have my Pro key in there and the shares, but still I cannot see any of my shares. I even tried to create a new share with the same name as before but it still will not show the data I already have on my 19 drives... I am still where I started. I am so confused.

 

syslog_09022014.txt

@WeeboTech

I agree! Im very thankful for everyone post and all the support. I dont plan on enabling cache_dirs since its running smooth unless u think i should for testing purposes. There's a thread for cache_dir with some kind of documented memory leak.

 

@MrLondon

I have no clue how to help you, however, i would not have copied my config over and would have recreated the entire system to rule it out, does it only have on Xen 64? Non Xen64? 5.0.X? Can you navigate to the data on each drive (mnt/disk/sharename/etc.)? Are you using simple features, boxcar, etc..? Have you tired a new share name? Are you including all of the drives in your new share?

 

Can you post your share.cfg? And i am summing the array starts fine?

 

There is definite data on each drive under /mnt/md1... And currently not booted into xen at all. I can copy the drive assignment and only copy over the pro key if that will help. actually I just found something I didn't see before. Under /mnt I have a directory called user0 when I go into that directory I can see all my shares. Should I change that name to just user? will that fix my issues?

 

 

Sent from my iPhone using Tapatalk

I would give it give it a shot, but do not take my advice on it as i am not a expert and i do want you to lose any data from bad advice. Here is my output:

 

Tower login: root
Linux 3.10.24p-unRAID.
Last login: Sat Feb  8 22:39:08 -0700 2014 on /dev/pts/0 from Office.
root@Tower:~# cd /mnt
root@Tower:/mnt# ls
cache/  disk1/  disk2/  disk3/  user/
root@Tower:/mnt#

 

When you goto /mnt/user0/ does it show all your data from each drive?

Be careful.  User0 is there for when using cache.  That is /user0 is all array folders, user is all array folders + cache dolders

 

Sent from my Nexus 7 using Tapatalk

 

 

I might have that backward.  I don't have my server handy to confirm.  But you u get the point I hope

 

Sent from my Nexus 7 using Tapatalk

 

 

i do have a cache drive in the system so that explains the user0. but still don't know how I get the user shares back.

i do have a cache drive in the system so that explains the user0. but still don't know how I get the user shares back.

 

Try stopping and starting the array via the emhttp web panel.

i do have a cache drive in the system so that explains the user0. but still don't know how I get the user shares back.

If you started from a clean system, did you remember to enable use shares under Settings?  Until you do so you will not see any such shares show up.

i do have a cache drive in the system so that explains the user0. but still don't know how I get the user shares back.

 

Try stopping and starting the array via the emhttp web panel.

 

I am currently trying to stop the raid and it has been doing it for several min now and not completed yet. Something seems wrong here.

 

MrLondon

Are you using simple features, boxcar, etc..?

Are you using simple features, boxcar, etc..?

 

everything is stock unRaid

 

in the syslog I can see these errors

 

 

Feb  9 16:00:33 Tower logger: rmdir: failed to remove '/mnt/user': Directory not                              empty

Feb  9 16:00:33 Tower emhttp: shcmd (1025): set -o pipefail ; umount /mnt/user0                              |& logger

Feb  9 16:00:33 Tower logger: umount: /mnt/user0: device is busy.

Feb  9 16:00:33 Tower logger:        (In some cases useful info about processes                              that use

Feb  9 16:00:33 Tower logger:          the device is found by lsof(8) or fuser(1                              ))

Feb  9 16:00:33 Tower emhttp: _shcmd: shcmd (1025): exit status: 1

Feb  9 16:00:33 Tower emhttp: shcmd (1026): rmdir /mnt/user0 |& logger

Feb  9 16:00:33 Tower logger: rmdir: failed to remove '/mnt/user0': Device or re                              source busy

Feb  9 16:00:33 Tower emhttp: shcmd (1027): crontab -c /etc/cron.d - <<< "# Gene                              rated mover schedule: 40 3 * * * /usr/local/sbin/mover |& logger"

Feb  9 16:00:33 Tower emhttp: Retry unmounting user share(s)...

 

You have a ssh/telnet session open and cd'ed to some /mnt/user/ folder?

root@Tower:/mnt/user0# tail /var/log/syslog

Feb  9 16:14:11 Tower logger: rmdir: failed to remove '/mnt/user': Directory not empty

Feb  9 16:14:11 Tower emhttp: shcmd (1840): set -o pipefail ; umount /mnt/user0 |& logger

Feb  9 16:14:11 Tower logger: umount: /mnt/user0: device is busy.

Feb  9 16:14:11 Tower logger:        (In some cases useful info about processes that use

Feb  9 16:14:11 Tower logger:          the device is found by lsof(8) or fuser(1))

Feb  9 16:14:11 Tower emhttp: _shcmd: shcmd (1840): exit status: 1

Feb  9 16:14:11 Tower emhttp: shcmd (1841): rmdir /mnt/user0 |& logger

Feb  9 16:14:11 Tower logger: rmdir: failed to remove '/mnt/user0': Device or resource busy

Feb  9 16:14:11 Tower emhttp: shcmd (1842): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 40 3 * * * /usr/local/sbin/mover |& logger"

Feb  9 16:14:11 Tower emhttp: Retry unmounting user share(s)...

root@Tower:/mnt/user0# cd ..

root@Tower:/mnt# cd user

root@Tower:/mnt/user# ls

series/

root@Tower:/mnt/user# cd series/

root@Tower:/mnt/user/series# ls

root@Tower:/mnt/user/series#

 

 

root@Tower:/etc# ls cr*

cron.d:

cron.update

 

cron.daily:

certwatch*  logrotate*

 

cron.hourly:

 

cron.monthly:

 

cron.weekly:

root@Tower:/etc#

 

Maybe you did cd.. and cd user too fast? Retry may take some seconds...

 

If still same problem try something like:

lsof | grep /mnt/

root@Tower:/etc# lsof | grep /mnt/

bash      1415      root  cwd      DIR                0,1        0      20630 /mnt/user

 

Another shell session open? running on 'screen'? Anyway 'kill -9 1415' should terminate it.

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.