I have just upgraded BUBBA2 using the admin webpage.
After rebooting I cannot access BUBBA2 at all, no ssh, no web access, and the blue led keeps flashing.
Anyone have any ideas?
Thanks.
Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
No access to BUBBA2 after latest upgrade
Re: No access to BUBBA2 after latest upgrade
It sounds like some service is blocking during boot; Have you installed some other programs, or is there only the stuff we ship?wm.bubba wrote:I have just upgraded BUBBA2 using the admin webpage.
After rebooting I cannot access BUBBA2 at all, no ssh, no web access, and the blue led keeps flashing.
Anyone have any ideas?
Thanks.
/Carl
Re: No access to BUBBA2 after latest upgrade
The only service I can think of is hddtemp.
I've also made some tweaks to fstab (to auto mount BUBBA|STORAGE), to sudoers to give me access to some root commands, and added some entries into my crontab.
Other than this I can't think of anything.
I've also made some tweaks to fstab (to auto mount BUBBA|STORAGE), to sudoers to give me access to some root commands, and added some entries into my crontab.
Other than this I can't think of anything.
Re: No access to BUBBA2 after latest upgrade
Have you tried creating the boot USB device and booting from it, so you can see if their is any physical issues?
You can then look at the disks, and maybe get a better idea of what is blocking the boot sequence.
ISO for the USB disk is on the Excito site.
You can then look at the disks, and maybe get a better idea of what is blocking the boot sequence.
ISO for the USB disk is on the Excito site.
Re: No access to BUBBA2 after latest upgrade
Thanks for the suggestion, asparak.
I've already reinstalled the OS and I am back up and running again.
But it certainly is a suggestion to bear in mind for the future.
I'm in the process if making all the changes again, one by one, and will post back if I find anything conclusive.
I've already reinstalled the OS and I am back up and running again.
But it certainly is a suggestion to bear in mind for the future.
I'm in the process if making all the changes again, one by one, and will post back if I find anything conclusive.
Re: No access to BUBBA2 after latest upgrade
Making progress.
First change - install sudo and edit sudoers to allow access to some root commands.
- rebooted, no problems.
Second change - edit fstab to mount BUBBA|STORAGE on boot.
- rebooted, led keeps flashing, problem found.
Booted from USB stick, mounted BUBBA root partition and removed entry from fstab.
Rebooted, BUBBA back working again.
Mounted BUBBA|STORAGE from admin web page, and took a not of the entry added in fstab.
I have amended the fstab entry to match, have rebooted and BUBBA boots successfully.
The first fstab entry worked before the latest upgrade, but not after -
/dev/sdb1 /home/storage/extern/WDC_WD10EADS-00M-1 ext3 noatime,defaults 0 1
this is the fstab entry I now have, which works -
/dev/sdb1 /home/storage/extern/WDC_WD10EADS-00M-1 auto defaults 0 0
not much different in the two, I'm sure you'll agree.
I'd be interested to know if anyone can explain this.
Thanks.
First change - install sudo and edit sudoers to allow access to some root commands.
- rebooted, no problems.
Second change - edit fstab to mount BUBBA|STORAGE on boot.
- rebooted, led keeps flashing, problem found.
Booted from USB stick, mounted BUBBA root partition and removed entry from fstab.
Rebooted, BUBBA back working again.
Mounted BUBBA|STORAGE from admin web page, and took a not of the entry added in fstab.
I have amended the fstab entry to match, have rebooted and BUBBA boots successfully.
The first fstab entry worked before the latest upgrade, but not after -
/dev/sdb1 /home/storage/extern/WDC_WD10EADS-00M-1 ext3 noatime,defaults 0 1
this is the fstab entry I now have, which works -
/dev/sdb1 /home/storage/extern/WDC_WD10EADS-00M-1 auto defaults 0 0
not much different in the two, I'm sure you'll agree.
I'd be interested to know if anyone can explain this.
Thanks.