Hi all,

 

Last night I upgraded my unraid pro installation to 6.1.4 through the plugin manager then shutdown the machine (without immediately rebooting).  This morning I rebooted and saw the following error on the console.

 

"Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key"

 

The bios of my unraid machine identifies my sandisk usb as the disk to boot from, but it won't boot.  I tried reading the usb disk on my macbook and on a linux machine (kodibuntu).  In linux the usb appears in file manager, but I can't browse the contents.  On my mac, the usb disk appears in the system report but doesn't show in the disk utility.

 

I'd not made any bios changes previous to the upgrade, and all was working fine.  I'd appreciate thoughts on this.

 

bye

rowan

 

 

 

 

What version did you upgrade from?

Unfortunately I don't recall the previous version

Since you can't browse the contents on another computer, its probably safe to assume that somehow the contents got trashed.  At this point, you're probably going to have to download the zip file from LT's website http://lime-technology.com/download/ and set up the flash from scratch.  Copy your .key file over to the config folder, boot and reset up  the disk assignments.

Hi Squid - thanks for your advice.  I'd assumed that I wouldn't be able to use the same key on a different usb.  I'll give it a go.

I would use the same flash since it's of no use (and may still be good).

 

But, if you want you can use a new flash drive (still copy over the old .key file).  unRaid will bitch about it, then prompt you through the process of transferring the .key file to a new flash drive.  Takes about 5 minutes for the email to arrive.

ok - I can't seem to read the usb stick at all so will try another one.

ok - I can't seem to read the usb stick at all so will try another one.

Format it with FAT32 and see if you can set it up fresh.

Thanks for the advice.  It certainly helped, and unraid is now checking parity. 

 

I'm unsure how to reinstate (?) user shares which I previously created via the unraid web utility.  On the 'Dashboard page' of the web utility, I can see all of my old user shares listed in the 'Shares List' column.  On the 'Shares' page of the web utility, no user shares are listed and I have options to 'Add share' or 'Compute all.' 

 

If I choose 'Compute all', would unraid recreate shares based on existing directory names under /mnt/user (i.e. the directories that unraid created when I last setup shares via the web utility)?

Thanks for the advice.  It certainly helped, and unraid is now checking parity. 

 

I'm unsure how to reinstate (?) user shares which I previously created via the unraid web utility.  On the 'Dashboard page' of the web utility, I can see all of my old user shares listed in the 'Shares List' column.  On the 'Shares' page of the web utility, no user shares are listed and I have options to 'Add share' or 'Compute all.' 

 

If I choose 'Compute all', would unraid recreate shares based on existing directory names under /mnt/user (i.e. the directories that unraid created when I last setup shares via the web utility)?

Not sure what could cause these symptoms.  All top level folders on each disk should automatically be turned into User shares (with default settings) as long as user shares are enabled under Settings->Global Share Settings. I would suggest posting the diagnostics zip file (obtained via Tools->Diagnostics) to provide enough information to help identify the cause of your problem.

ok - diagnostic file attached.  I checked that user shares are enabled under the global share settings.

tower-diagnostics-20151201-1750.zip

ok - diagnostic file attached.  I checked that user shares are enabled under the global share settings.

Not sure what might be causing your issues.  However a few observations:

 

- You have unMENU installed and are starting it in the 'go' file.  This is causing errors in the syslog of the form

Nov 30 20:44:07 Tower unmenu[15921]: sh: /root/mdcmd: No such file or directory

due to the fact that unMENU has not been updated to be fully compatible with unRAID v6.1.x series.  You can fix this by adding the following line to your go file

# Fix for 6.1 to get unMenu running
if [ ! -f /root/mdcmd ] ; then
  ln -s /usr/local/sbin/mdcmd /root/mdcmd
  logger -tgo "Set up soft link for /root/mdcmd (for unMenu)"
else
  logger -tgo "/root/mdcmd already exists"
fi
# Start up unmenu if it is installed
if [ -f /boot/unmenu/uu ] ; then
  /boot/unmenu/uu 
  logger -tgo "UnMenu started"
fi

. This is more than your strictly need but it is tidy way of handling this as writes entries to the syslog to remind you what has happened.

 

- I see a number of occurrences of

Nov 30 20:20:11 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Nov 30 20:20:11 Tower kernel: md: could not read superblock from /boot/config/super.dat

This should only happen if the array has never been started before.  When it happens on an existing system then it suggests that there might be some level of corruption on the USB stick that is causing it to be read-only.  The easiest way to fix such an issue is to insert it into a Windows system and let Windows fix it.

Thanks for that - I'd not realised the unmenu issue - had not been following the discussion forum for some-time.

I switched off the adblocker chrome plugin (for tower) as suggested elsewhere in the forum and that fixed the problem with user shares not displaying.

 

https://lime-technology.com/forum/index.php?topic=44351.0