Amahi halts during boot: fsck.ext4: unable to resolve...

[kikkegek]

hi guys,

today suddenly the HDA stopped rebooting.
I even had to give my headless server a screen and keyboard, to see what was keeping it from booting.

I get to this screen and then I am stuck:



I have been re ading all kinds of stuff, but cant seem to find out what is causing this error.

please advise

[kikkegek]

I got some extra info:

[root@amahi jochen]# blkid
/dev/sda3: UUID="485db5c1-4dce-4b5d-b270-60b05a87659d" TYPE="ext4"
/dev/sdb1: LABEL="SAMSUNG" UUID="667bd417-70f4-4524-ab03-501113edf499" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda1: UUID="2f6fc156-23d4-4d4c-884e-2c21c7e71aed" TYPE="ext4"
/dev/sda2: UUID="BKEgkQ-Aqim-ykoi-8Bl2-1VIv-B9zr-mfrSqU" TYPE="LVM2_member"
/dev/mapper/vg_amahi-lv_swap: UUID="befaf5e4-3ca5-4342-8e40-4b4c0106ce08" TYPE="swap"
/dev/mapper/vg_amahi-lv_root: UUID="48a98650-9bf0-4dee-99ca-be88c0ac1933" TYPE="ext4"
/dev/mapper/vg_amahi-lv_home: UUID="f1ed0f46-e00d-4868-b8f3-19c5dc5dea4c" TYPE="ext4"

#
# /etc/fstab
# Created by anaconda on Sun Jul 31 16:09:11 2011
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_amahi-lv_root / ext4 defaults 1 1
UUID=2f6fc156-23d4-4d4c-884e-2c21c7e71aed /boot ext4 defaults 1 2
/dev/mapper/vg_amahi-lv_home /home ext4 defaults 1 2
UUID=485db5c1-4dce-4b5d-b270-60b05a87659d /var/hda/files ext4 defaults 1 2
/dev/mapper/vg_amahi-lv_swap swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
UUID=667bd417-70f4-4524-ab03-501113edf499 /var/hda/files/drives/drive1 ext4 defaults 1 2
UUID=067d880c-0b33-45f0-a218-af5743f08692 /var/hda/files/drives/drive5 ext4 defaults 1 2

I have already tracked down the problem to the last line in the fstab. That UUID does not exist as far as "blkid" tell me.

I will try to comment that line out and see if it fixes the problem and gets my my HDA back online..

[bigfoot65]

That should allow the HDA to boot.

[kikkegek]

yes, HDA start. so happy.

but now the sama shares are not acccesible.

[root@amahi jochen]# ls -l /usr/lib*/samba/vfs/greyhole.so​
ls: cannot access /usr/lib*/samba/vfs/greyhole.so​: No such file or directory

reinstalling the greyhole does not help, but returns an error:

[root@amahi jochen]# rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm
Retrieving http://www.greyhole.net/releases/rpm/i3 ... .25-1.i386
curl: (22) The requested URL returned error: 404
error: skipping http://www.greyhole.net/releases/rpm/i3 ... .25-1.i386 - transfer failed

checking my greyhole version now shows two? versions?

[root@amahi jochen]# rpm -q hda-greyhole
hda-greyhole-0.9.25-1.i386
hda-greyhole-0.9.26-3.i386

might those two versions be the trouble?

[kikkegek]

for some reason I was not able to retrieve the greyhole rpm. So I downladed it manually:

[root@amahi jochen]# wget http://www.greyhole.net/releases/rpm/i3 ... 1.i386.rpm
--2012-12-31 09:42:56-- http://www.greyhole.net/releases/rpm/i3 ... 1.i386.rpm
Resolving www.greyhole.net... 108.162.193.100, 108.162.196.198
Connecting to www.greyhole.net|108.162.193.100|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104171 (102K) [application/octet-stream]
Saving to: “hda-greyhole-0.9.25-1.i386.rpm”

100%[=================================================================================>] 104,171 172K/s in 0.6s

2012-12-31 09:42:57 (172 KB/s) - “hda-greyhole-0.9.25-1.i386.rpm” saved [104171/104171]

and then installed it manually:

[root@amahi jochen]# rpm -Uvh --force hda-greyhole-0.9.25-1.i386.rpm
Preparing... ########################################### [100%]
1:hda-greyhole ########################################### [100%]
Executing post-install script...
Found LIB_DIR = /usr/lib
Detected Samba 3.5; creating symlink pointing to greyhole-samba35.so
Post-install script completed.

===========================================================================
See /usr/share/greyhole/USAGE to learn how to configure and start Greyhole.
===========================================================================

but I still get:

[root@amahi jochen]# ls -l /usr/lib*/samba/vfs/greyhole.so​
ls: cannot access /usr/lib*/samba/vfs/greyhole.so​: No such file or directory

[kikkegek]

I tried Yum to update to latest version, but that also fails:

[root@amahi vfs]# yum --enablerepo=greyhole update hda-greyhole​
Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
Adding en_US to language list
Loading mirror speeds from cached hostfile
* fedora: ftp.heanet.ie
* rpmfusion-free: download1.rpmfusion.org
* rpmfusion-free-updates: download1.rpmfusion.org
* rpmfusion-nonfree: download1.rpmfusion.org
* rpmfusion-nonfree-updates: download1.rpmfusion.org
* updates: ftp.heanet.ie
Setting up Update Process
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
yummain.user_main(sys.argv[1:], exit_code=True)
File "/usr/share/yum-cli/yummain.py", line 258, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 113, in main
result, resultmsgs = base.doCommands()
File "/usr/share/yum-cli/cli.py", line 396, in doCommands
return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
File "/usr/share/yum-cli/yumcommands.py", line 225, in doCommand
return base.updatePkgs(extcmds)
File "/usr/share/yum-cli/cli.py", line 696, in updatePkgs
if not self.update(pattern=arg):
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3504, in update
self.logger.critical(_('No Match for argument: %s') % arg)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 12: ordinal not in range(128)

[kikkegek]

sorry,

eveything seems fine again. shares are accesible from my windows and linux clients.

and symlinks are in good shape again too:

[root@amahi vfs]# ls -l /usr/lib*/samba/vfs/greyhole.so
lrwxrwxrwx 1 root root 37 Dec 31 10:14 /usr/lib/samba/vfs/greyhole.so -> /usr/lib/greyhole/greyhole-samba35.so

I have absolutely no clue what caused this, but I am happy I am running again

[kikkegek]

well, server has been in sleep mode and when I wake it up the symlinks are gone again:

[root@amahi vfs]# ls -l /usr/lib*/samba/vfs/greyhole.so
ls: cannot access /usr/lib*/samba/vfs/greyhole.so: No such file or directory

also there seem to be two versions of greyhole present?

[root@amahi vfs]# rpm -q hda-greyhole
hda-greyhole-0.9.25-1.i386
hda-greyhole-0.9.26-3.i386

[kikkegek]

manually reinstalling greyhole seems to fix it. its fine after reboot...but after a suspend to disk from AES the samba shares are gone again?

[bigfoot65]

The AES may be the problem. Not sure what steps to take next, but might consider posting in the AES area for help with it.