Unable to boot HDA

[vegaramos1]

I'm not exactly sure what happened to my server, as it was working perfectly for quite a while. However I recently tried to reboot the server, and now it won't boot. I've gotten several different errror, but two seem to stand out as troublesome.

The first error I tend to see is:

An error occurred during the file system check.
Dropping you to a shell; the system will reboot
when you leave the shell.
Give root password for maintenance.

Once I give root password, I see the following error

fsck.ext4: Unable to resolve 'UUID=xxxxxxxxxxxxxxxxxxxxxxx'

My server is an old laptop with two 2 Tb external hard drives attached. I am using Greyhole to mirror the data on one drive to the other. Any suggestions would be appreciated.

[vegaramos1]

I've tried rebooting the HDA and upon reboot and dropping to the shell, I saw another issue. This time I found a message that says the following:

fsck.ext4: No such file or directory while trying to open /dev/.tmp-block-8:33
/dev/.tmp-block-8:33:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else) the the superblock
is corrupt and you might try running e2fsck with an alternat superblock:
e2fsck -b 8192 <device>

Any suggestions as to how I should proceed would be appreciated.

[vegaramos1]

I found the following website, and it helped me to figure out what needs to be done to at least be able to boot into the HDA, the website is:

http://blog.stpworks.com/archive/2010/1 ... ilure.aspx

I stopped at step 6, as I am not adding a new hard drive (I hope not anyway). By Process of elimination, I have determined that the second USB drive is preventing me from booting into the system. I commented it from my /etc/fstab and the HDA is booting again. I am currently running a

Code: Select all

e2fsck -cn /dev/sdd1

I'll post the results of that tomorrow (hopefully).

For completeness of my request, here are my Greyhole troubleshooting documents.

smb.conf

http://fpaste.org/e0UV/

greyhole.conf

http://fpaste.org/e0UV/

my fstab

http://fpaste.org/OLAX/


Results of: mount; fdisk -l; df -h; greyhole --stats

Code: Select all

/dev/mapper/vg_hda-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/sdb1 on /var/hda/files/drives/drive1 type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) gvfs-fuse-daemon on /home/alvin/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=alvin) Disk /dev/sda: 99.8 GB, 99830223360 bytes 255 heads, 63 sectors/track, 12137 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00069580 Device Boot Start End Blocks Id System /dev/sda1 * 1 26 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 26 12137 97285621 8e Linux LVM Disk /dev/dm-0: 96.5 GB, 96464797696 bytes 255 heads, 63 sectors/track, 11727 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 3154 MB, 3154116608 bytes 255 heads, 63 sectors/track, 383 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/sdb: 1999.7 GB, 1999696297984 bytes 255 heads, 63 sectors/track, 243115 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000667c5 Device Boot Start End Blocks Id System /dev/sdb1 1 243116 1952828356+ 83 Linux Disk /dev/sdd: 1999.7 GB, 1999696297984 bytes 255 heads, 63 sectors/track, 243115 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0005a4e2 Device Boot Start End Blocks Id System /dev/sdd1 1 243116 1952827392 83 Linux Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_hda-lv_root 89G 64G 21G 76% / tmpfs 750M 284K 750M 1% /dev/shm /dev/sda1 194M 22M 163M 12% /boot /dev/sdb1 1.8T 485G 1.3T 28% /var/hda/files/drives/drive1 Greyhole Statistics =================== Storage Pool Total - Used = Free + Attic = Possible /var/hda/files/drives/drive1/gh: 1833G - 484G = 1256G + 22G = 1278G /var/hda/files/drives/drive2/gh: df: `/var/hda/files/drives/drive2/gh': No such file or directory df: no file systems processed 0G - 0G = 1256G + 0G = 1256G

Results of: mysql -u root -phda -e "select * from disk_pool_partitions" hda_production

Code: Select all

+----+------------------------------+--------------+---------------------+---------------------+ | id | path | minimum_free | created_at | updated_at | +----+------------------------------+--------------+---------------------+---------------------+ | 1 | /var/hda/files/drives/drive1 | 10 | 2010-12-22 00:58:25 | 2010-12-22 00:58:25 | | 2 | /var/hda/files/drives/drive2 | 10 | 2010-12-22 00:58:27 | 2010-12-22 00:58:27 | +----+------------------------------+--------------+---------------------+---------------------+

Results of: mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la | fpaste

http://fpaste.org/mdVi/

[vegaramos1]

After 24 hours, the scan had only completed 6%, so I decided to format the drive and start all over again. The format took another 8 hours, but it finally completed. I have got the drive in the storage pool, but when I do a

Code: Select all

greyhole --fsck

Nothing seems to be happening. I checked the Greyhole log, and I see the following error.

Code: Select all

Mar 22 22:43:18 2 check_pool: Can't query tasks: Got error 134 from storage engine Mar 22 22:44:48 6 daemon: Greyhole (version 0.7.5) daemon started. Mar 22 22:44:48 7 daemon: Loading graveyard backup directories... Mar 22 22:44:48 7 daemon: Found 2 directories in the settings table. Mar 22 22:44:48 7 parse_logs: Parsing Samba logs... Mar 22 22:44:48 7 parse_logs: Done parsing. Mar 22 22:44:48 7 simplify_tasks: Simplifying pending tasks. Mar 22 22:44:48 7 parse_logs: Parsing Samba logs... Mar 22 22:44:48 7 parse_logs: Done parsing. Mar 22 22:44:48 2 check_pool: Can't query tasks: Got error 134 from storage engine

Anyone have any suggestions on how to resolve the error 134?

[gboudreau]

You'll probably need to delete the greyhole database, and re-create it.
The following should do it:

Code: Select all

mysql -u root -phda -e 'drop database greyhole' mysql -u root -phda -e 'create database greyhole' mysql -u root -phda -e "grant all on greyhole.* to greyhole@'localhost' identified by 'greyhole'" mysql -u greyhole -pgreyhole greyhole < /usr/share/greyhole/schema-mysql.sql

[vegaramos1]

That seemed resolve the issue. I'm in the process of copying my share data over to the new drive. I sure do hope that my HD issues are resolved, but I have a feeling that perhaps this HD is going bad. Thanks again.

[cpg]

Yup - it does look like a hard drive going bad!

It may also be taking a lot of timeouts and such to test things, that may be why it's taking so long to check ... typical of a bad drive. 2tb should be under warranty at this time still.

[slimborama]

http://blog.stpworks.com/archive/2010/1 ... ilure.aspx

This was a super useful post that got me out of panicking while replacing a drive. Thanks!