Bubba doesn't boot - blinking lights

johanheinesen · Post by **johanheinesen** » 17 Sep 2007, 12:05

Hi,

My Bubba has been a bit unstable lately. It startet to freeze from time to time and now it wont finish booting. I've booted it on the minimal usb boot image but don't know what to do next.
I guess I have to mount the disk (how) and then try to repair it (how) before I reboot again.
My wife will kill me if she don't get access to her email soon so I desperately need som help.....

Johan

pa · Post by pa » 18 Sep 2007, 04:00

Could you run "fsck /dev/hda1"

It is possible that you have some corrupt files on your system, and that the fsck is running during boot but can not repair your file system without user input.

johanheinesen · Post by **johanheinesen** » 18 Sep 2007, 18:59

Hmmm. This is what happened. Any ideas?

--------
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 19809511: 39656620 39656620

Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
Warning... fsck.ext3 for device /dev/hda1 exited with signal 9.
fsck 1.39 (29-May-2006)
---------------

pa · Post by pa » 19 Sep 2007, 02:48

The exit code "9" is means that there has been errors corrected (code 1) and that there was an "operational error" (code "8") and the "9" is the sum of these.

Could you try to run it again with the verbose flag set as well?
("fsck -V /dev/hda1")

/PA

johanheinesen · Post by **johanheinesen** » 19 Sep 2007, 13:41

Hi,

It didn't help. You wrote that 1 meant that errors had been corrected but it looks like the same inode as last time.

-------
# fsck -V /dev/hda1
fsck 1.39 (29-May-2006)
[/sbin/fsck.ext3 (1) -- /dev/hda1] fsck.ext3 /dev/hda1
e2fsck 1.39 (29-May-2006)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda1 is mounted.
Bubba contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 19809511: 39656620 39656620
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
Warning... fsck.ext3 for device /dev/hda1 exited with signal 9.
-------

johanheinesen · Post by **johanheinesen** » 23 Sep 2007, 13:48

Hi,
What do you suggest I do know?
Send it to you guys so you can fix it or is there anything else I can do myself?

pa · Post by pa » 23 Sep 2007, 16:15

Hi Johan,

I am sorry that you are experiencing so much problems with your bubba.
Before you send it back for repair, please try to re-install it as described in the manual.
There is also a discussion in this thread http://excito.org/forum/viewtopic.php?t=581, about installing the system.

/PA

Ubi · Post by **Ubi** » 24 Sep 2007, 03:23

Hang on

Many versions of Fsck require a flag set to actually repair anything. Default behaviour is to analyze but not repair.

Are you sure the repair was initiated?

johanheinesen · Post by **johanheinesen** » 24 Sep 2007, 07:29

Well - it looks like it started the repair but couldn't finish it.

I think I'll reinstall the whole thing. My only problem is that my backup is a bit old.
Can anyone tell me how I mount the hd so I can copy our email to another location?

Post by **tor** » 24 Sep 2007, 07:36

To mount the harddisk from the rescue image simply do:

Code: Select all

mount /dev/hda1 /mnt

And you should be able to access it under /mnt (This if the disk is not to currupt then.)

/Tor

solar · Post by **solar** » 02 Mar 2008, 13:36

Hello, first I would like to thank you guys at Excito for such a lovely little server!

Secondly, I've ran into a disk problem aswell.
I was happily messing around a little the other day, installing some wiki software and stuff, and then thought I would try reinstall my bubba completely, for a fresh start. The problem now is, somehow the disk is damaged. Can't boot the bubba.img and the LED keeps blinking indefinitely.
Anyway, when booting with the rescue image and running fsck -v -t ext3 /dev/hda1, this is what I get:

Code: Select all

fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda1 is mounted.
Resize inode not valid.  Recreate<y>? yes

Superblock last write time is in the future.  Fix<y>? yes

Bubba was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory.  Clear<y>? yes

Bus error

And after that, the whole thing crumbles to dust, ie. when trying to list the root dir:

Code: Select all

# ls
Segmentation fault

I think the superblock is damaged.. Any ideas on what's going on?

Thanks,
-Solar

Post by **tor** » 03 Mar 2008, 04:31

Solar,

First try getting a correct time on your system and see if that makes any difference. Then if it still does not work, can you try to reformat the disk and see if that solves the problem?

/Tor

solar · Post by **solar** » 03 Mar 2008, 13:17

Now that's really interesting, the time was set to "un sÃ¶n 31 17:02:21 MST 1969", lol. Running "date 030311512008" rewarded me with "un %y 3 11:51:00 MST 2008". And why would the timezone be set to MST, we're using UTC+1 in sweden?

Anyho, it appears that "fsck -v -t ext3 /dev/hda1" actually worked! Gonna try reinstalling now, be back later with the results.

Edit: Nope, reinstall didn't work this time either.. Booted up the rescue again, setting date and running fsck:

Code: Select all

<snip>Couldn't find ext2 superblock, trying backup blocks...
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Resize inode not valid.  Recreate<y>? yes</snip>

Reformatted hda, ran fsck again (this time telling me it was clean), then "mkfs.ext3 /dev/hda1" which ended with:

Code: Select all

Creating journal (32768 blocks): mkfs.ext3: No such file or directory 
        while trying to create journal

Ran fsck again to check if anything did happen to the disk, which resulted in "Superblock has an invalid ext3 journal (inode 8).", yet again...

solar · Post by **solar** » 04 Mar 2008, 11:48

I finally managed to reinstall my bubba by:
*setting date
*running fsck and with fdisk remove all the partitions on hda
*and lastly letting it cool down before attempting to reinstall

Just wonderful, I say xD