August 24, 201411 yr ok so ive done an upgrade from v6b6 to v6b7 and for some reason unraid is not mounting the defined shares. i was running powerdown package and cache_dirs script, both of which i have disabled, no plugins are running on my system. i can see the share cfg files in /boot/config/shares but unraid refuses to mount them, all drives are present and i have also run a parity check which checks out fine with no errors. i can see the user share section in the webui but its blank with only the option to add in shares again. things yet to try are run chkdsk on the usb key, and try downgrading to v6b6 to see if the shares re-appear. i am attaching my syslog, the section i think is causing the issue is below:- Aug 24 09:55:55 Tower emhttp: shcmd (60): mkdir /mnt/user0 Aug 24 09:55:55 Tower emhttp: shcmd (61): /usr/local/sbin/shfs /mnt/user0 -disks 510 -o noatime,big_writes,allow_other |& logger Aug 24 09:55:55 Tower emhttp: shcmd (62): mkdir /mnt/user Aug 24 09:55:55 Tower emhttp: shcmd (63): /usr/local/sbin/shfs /mnt/user -disks 511 -o noatime,big_writes,allow_other -o remember=330 |& logger Aug 24 09:55:55 Tower shfs/user: fuse_main exit: 1 Aug 24 09:55:55 Tower logger: fuse: invalid argument `noatime,big_writes,allow_other' Aug 24 09:55:55 Tower emhttp: shcmd (64): crontab -c /etc/cron.d - <<< "# Generated mover schedule: 40 3 * * * /usr/local/sbin/mover |& logger" Aug 24 09:55:55 Tower emhttp: shcmd (65): /usr/local/sbin/emhttp_event disks_mounted edit - if i do manually add a share then i can see it via smb, however if i reboot the system the share disapears, so i cannot just simply re-create the shares. FIXED! - looks like an old bug, tom had a workaround that fixes the issue http://lime-technology.com/forum/index.php?topic=31653.msg291122#msg291122 tom - might be worth forcing a numeric value if its null in the next beta to stop this happening? syslog.txt
August 24, 201411 yr I accidentally reintroduced this bug while fixing a different bug (proper handling of KB/MB/GB/TB suffix). The workaround is to put a value in the Min Free Space field. If you want no min free space, put a 0 in there (don't leave blank). Sorry this might warrant uploading a -beta7a.
August 25, 201411 yr Author Thanks for confirming this Tom, took me a fair bit of trawling of the forum to find your fix :-) Oh and on another note I suggest in your readme upgrade section you have a line in there that states you must copy your licence to /boot/config as this also tripped me up, there is no message about missing licence, the array just starts and stops
August 25, 201411 yr The workaround is to put a value in the Min Free Space field. If you want no min free space, put a 0 in there (don't leave blank). TBH I think this is good practice anyway. I am sure there is some best practice guide out there recommending that settings are never empty.
August 25, 201411 yr Author The workaround is to put a value in the Min Free Space field. If you want no min free space, put a 0 in there (don't leave blank). TBH I think this is good practice anyway. I am sure there is some best practice guide out there recommending that settings are never empty. Thing is I didn't specifically set it to null, maybe a previous release blanked it? I'm assuming the default behavior when you activate a cache drive is not null value right? Why not just don't allow the user/system to blank that field? If field == none then field = 0 Edit - thinking about it this may well of been blanked when I reformatted my cache drive to btrfs in beta 6, hard to say for sure when it happened as the bug was not present in beta 4-6.
August 25, 201411 yr I think that is sensible and essentially what I am saying... a blank field is no information and could be misinterpreted by the user or the code but a field that defaults to a finite value (lets say 0) cannot. I am sure there is a RFC or the like on this specific thing that I read years ago. Anyway regardless it may be a sensible idea.
August 25, 201411 yr Oh and on another note I suggest in your readme upgrade section you have a line in there that states you must copy your licence to /boot/config as this also tripped me up, there is no message about missing licence, the array just starts and stops From the -beta7 announcement post: NOTE: the "undocumented" feature of looking in /boot has been removed. If your key file is in the root of your flash, you must move it to the 'config' directory.
August 25, 201411 yr Author Oh and on another note I suggest in your readme upgrade section you have a line in there that states you must copy your licence to /boot/config as this also tripped me up, there is no message about missing licence, the array just starts and stops From the -beta7 announcement post: NOTE: the "undocumented" feature of looking in /boot has been removed. If your key file is in the root of your flash, you must move it to the 'config' directory. Yeah I saw that but only cos I watch the forums, how many other people just see it available in downloads on the website and just follow the readme for upgrade instructions, just feedback from a users point of view that's all, no biggie. Edit - I do see it listed in the summary of changes in the readme so maybe that's good enough.
Archived
This topic is now archived and is closed to further replies.