Amahi Forums

My internet research is on going, but I thought I would try here as well.

I shut my hda off each night due to heat issues this summer - to many computers producing to much heat.

I turned my HDA on and Fedora never completes the bootup process. Right now I am looking at the nice little blue F logo... logon screen never comes up.

Being a windows man myself.... how does one even attempt to look at this kind of problem in linux?

It took over an hour to finish booting. This tells me its a hardware issue.

I am researching possible logs I can look at here. If anyone has suggestions I am open to them.

Seems I am getting Input/Output errors on My external Raid array - Hardware based.

This is all in an LVM...

Performance off of the Raid array is terrible... I can barely access any of the files.

So now I just really need to get my data off of that system so I can troubleshooting further...

the raid array is listed as healthy... so I am not sure what is going on.

errors found in bootlog

%G%G
udevadm settle - timeout of 180 seconds reached, the event queue contains:
/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1 (975)
/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb2 (976)
udevd[111]: worker [116] unexpectedly returned with status 0x0100


udevd[111]: worker [116] failed while handling '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1'


udevd[111]: worker [117] unexpectedly returned with status 0x0100


udevd[111]: worker [117] failed while handling '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb2'


udevd[111]: worker [279] unexpectedly returned with status 0x0100


udevd[111]: worker [279] failed while handling '/devices/virtual/block/dm-0'


Welcome to [0;34mFedora[0;39m
Press 'I' to enter interactive startup.
Starting udev: %Ginit: hdapsd main process (790) terminated with status 1

udevd[517]: worker [554] unexpectedly returned with status 0x0100


udevd[517]: worker [554] failed while handling '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb'



udevadm settle - timeout of 180 seconds reached, the event queue contains:
/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1 (1408)
/sys/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb2 (1409)
Wait timeout. Will continue in the background.[60G[[0;31mFAILED[0;39m]

Setting hostname defiant.catznet.local: [60G[[0;32m OK [0;39m]

ERROR: ddf1: reading /dev/dm-0[Input/output error]
udevd[517]: worker [521] unexpectedly returned with status 0x0100


udevd[517]: worker [521] failed while handling '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb1'


udevd[517]: worker [522] unexpectedly returned with status 0x0100


udevd[517]: worker [522] failed while handling '/devices/pci0000:00/0000:00:04.0/0000:02:00.0/host5/target5:0:0/5:0:0:0/block/sdb/sdb2'


ERROR: sil: reading /dev/dm-0[Input/output error]
Setting up Logical Volume Management: 1 logical volume(s) in volume group "vg_defiant00" now active
8 logical volume(s) in volume group "vg_defiant" now active
[60G[[0;32m OK [0;39m]

Checking filesystems
/dev/mapper/vg_defiant-root01: clean, 9845/673296 files, 146852/2688000 blocks
/dev/sda1: clean, 43/32768 files, 15287/131072 blocks
/dev/mapper/vg_defiant-home07: clean, 807/13443072 files, 909156/53741568 blocks
/dev/mapper/vg_defiant-opt02: clean, 11/160000 files, 27378/640000 blocks
/dev/mapper/vg_defiant-tmp03: clean, 54/339360 files, 56759/1356800 blocks
/dev/mapper/vg_defiant-usr04: clean, 133314/1409024 files, 789002/5632000 blocks
/dev/mapper/vg_defiant-usrlocal05: clean, 44/704512 files, 83901/2816000 blocks
/dev/mapper/vg_defiant-var06: clean, 23405/2240224 files, 361547/8960000 blocks
/dev/mapper/vg_defiant00-hda00: clean, 114032/156270592 files, 37673973/625079296 blocks
[60G[[0;32m OK [0;39m]

Remounting root filesystem in read-write mode: [60G[[0;32m OK [0;39m]

Mounting local filesystems: mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg_defiant00-hda00,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

[60G[[0;31mFAILED[0;39m]

ugh - it does look a bit like hardware.

can you try a different motherboard?
that way you determine is the hard drive or the controller?

first I'd try an fsck (filesystemcheck) of all the volumes.
the filesystems MUST be unmounted before you run fsck!
now: the hardware log can be accessed with the command dmesg
in the logging you provided it seems that /dev/sdb is corrupt.
a filesystemcheck may do good, but maybe there's more (since a filesystem check already completed succesfully (clean), but the -f (force) option tells fsck to really really do a check and do it thoroughly).
run the following command to get the SMART data from your harddisk: and post the resulting output here (the interesting parts is the smart error log, but there's more)

Thanks Moredruid. That info is getting saved in my growing linux knowledgebase.

I traced the problem to the e-sata cable. I find it odd that I could see the file structure just fine ( the LVM based on the external drive), even could get access to the files... it just took a darn long time to access anything. Replaced the cable and it was a speed demon again and worked fine.

I backed up the data in case it turns out to be something else.

If you want to be sure your drive is OK I'd recommend running some SMART tests. will give you all SMART output of the device will do a short SMART test (about 2 to 5 minutes IIRC).
the long test will take about an hour.