Mortumus

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Mortumus's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the tip on how to change the default menu to GUI mode. I've had the same problem since upgrading to 6.2.3 (I think it was). I always upgrade to the latest version. I was hoping this would be fixed in subsequent versions, but no, it persists. The biggest headache this caused was if I needed to reboot the system remotely it would never boot back up. It would just cycle around trying to boot into non-GUI mode (default), fail, then cycle again .. it was a pain. At least now I can reboot into GUI mode remotely, but also select non-GUI mode when I'm local to the machine. Thanks heaps. UnRaid rocks!
  2. Did you find a solution to this? I have a similar setup and I'm having the same issue
  3. Nice .. that looks like the set up I'm looking for
  4. OK ... another stab in the dark which worked. As this started after the upgrade to 6.3.2 I figured I'd try and revert back. I simply copied the bzimage, bzroot and bzroot-gui files from the 'previous' folder on the USB (which seems to be the previous version). I copied these over the current version files on the USB. When I booted it went through the motions just fine in non-gui mode and booted OK. If this didn't work I was going to simply try and change the menu so that the gui mode was the mode that booted unattended. I'll try and upgrade again and see what happens, but I suspect i'll get the same issue. Any other ideas welcome as this has allowed me to boot unattended, but it's not ideal.
  5. I tried this out. First I backed up the USB onto another computer. I downloaded the same build of Unraid as I had installed (6.3.2). After extracting the files I copied everything over the top of the existing files, except my config files I booted back up but it was exactly the same issue. I then copied all of the files including the config files and booted back up. Still the same issue but now the configurations are reset. I then just copied the original files on again ... still the same issue but the configs are back to how they were. Back to the drawing board.
  6. I have the same problem. I was told last night it's possibly something to do with the virtual RAM stored on the USB for each boot environment (or something like that). The GUI and the non-GUI boots will have different VM RAM files. The ram is backed up to disc if you like. Sounds a bit like a paging file on Windows. If the server goes down suddenly (like mine did, the toaster blew the fuse), the VM RAM can become corrupted. I could have my terms wrong here, but it's a Linux thing. The solution I am told is to download the latest copy of Unraid and overwrite the files on the USB with it. I'm not sure what happens to your configuration so perhaps someone else can chip in here with that info. I'm just passing on and paraphrasing what I was told by my Linux guru mate.
  7. I like this idea. At the moment we are in the dark a little as to what's happening with the mover. I guess a percent complete might be harder if you are also writing data to the cache while the mover is working, but I guess it can adjust.
  8. Check if there is a serial number using: http://www.softpedia.com/get/System/System-Info/USBView.shtml#download
  9. Hey guys, I was keen to find out this information before buying any new USB Flash drives. I found this utility that shows the Serial Number for any USB Flash drive that has one plus all the other info you might need. http://www.softpedia.com/get/System/System-Info/USBView.shtml#download Mortumus (Noob)