Tortuga

Members
  • Posts

    6
  • Joined

Everything posted by Tortuga

  1. I too would LOVE to see this working correctly!
  2. I'm having the exact same issue. Been trying to figure out what to do for 2 days!
  3. Yeah, that sounds exactly like what happened to me, except I that had an uneventful upgrade/shutdown/reboot until I the "can't find bonded" error.
  4. Hi Ititmpi, Yah, it was weird, but I do have one update... To "restore" the usb after upgrading, I simply copied the files from my previous 6.9 backup to replace the files on the usb. I didn't use the restore usb function. I thought I'd try to simply replace the files first. After that, it booted correctly immediately, but to my surprise, the update to 6.10 survived replacing all the files from the backup. Everything has worked perfect. I guess something just got corrupted in the configuration during upgrade??? I don't know. Sorry! I wish I could give you more debugging specifics, but for anyone else that runs into this problem, simply replacing the usb files from the backup worked like a charm!
  5. Hi, I think I just found a serious issue with the the rc release and my bonded nic. I used the upgrade tool, everything said I was good to go. I did the upgrade, everything said it completed OK. I rebooted and...nothing. It appeared as if I had lost *everything*...not to be melodramatic... It booted, but the last line ominously said, "bonding module not found". No surpise, my router didn't see it and didn't give it an IP address, but when I tried to log in locally at the gui (which *did* boot to the log in screen)...but did not work. The gui simply went blank. Nothing. So I looked at the command line which appeared to log in no matter what password (or no password) but it wasn't my unraid. It looked like a fresh brand new install of unraid. Didn't even have my correct server name. Thank the gods the backup worked, I restored to 6.9 and the world was right again! Unfortunately, I didn't get any pictures to show so I don't think I have any further useful information to share, but I'm pretty sure it had something to do with my bond network card.