udev hangs without giving any errors. There is prolly a problem with the kernel drivers but it should give me an error instead of waiting forever imo. The cpu doesnt hangs, I can ctrl+c kill the process but it's not a good idea to do so! If I wait long enought, I get this message: Hangcheck: hangcheck value past margin! Here is a short description of the computer: MB: Abit VP6 (Via Apollo pro133x --> vt82cxxxx) HighPoint Raid ide controller (not in raid mode --> hpt370) CPUs: 2x1ghz PIII RAM: 1gb pc133 sound: sound blaster 128 (esoniq ict5880) --> es1371 Video: ATI Rage 128GL AGP Lan: 2x SMC 10/100 --> tulip 1x D-Link DGE 530T (Marvell chipset) Reproducible: Always Steps to Reproduce: 1.Boot 2.Wait 3.Cry Actual Results: If I press ctrl-c, i'm getting an error. Tells me that the file system on one of my drives can't be automagically repaired: fsck.ext3: Bad magic number in super-block while trying to open /dev/hdc [...] then asks for my password to correct the situation, wich i tryed. I deleted my partition table, made a new one (1 partition for the whole 120gb drive) and then "formatted" it. I still get the same error. Expected Results: Either continue the boot process normally or tell me what the problem is or at least what it is trying to do before hanging... I am prolly the source of the bug as I might have forgot a driver or something but I'm realy lost. I've been searching for 8 hours by now with the help of people on #gentoo on freenode, can't get trough this. I hope someone can help me to find a way to get a step furter! If you need any information, just ask.
For starters, how about your /etc/fstab and baselayout version?
Here is my fstab (handtyped since I can't get the box connected to the network): /dev/hda1 /boot ext2 noauto,noatime 1 2 /dev/hda5 / ext3 noatime 0 1 /dev/hda2 none swap sw 0 0 /dev/hdc1 /home ext3 noatime 0 0 /dev/hdb /mnt/cdrom iso9660 noauto 0 0 /dev/fd0 /mnt/floppy auto noauto 0 0 proc /proc proc defaults 0 0 shm /dev/shm tmpfs nodev,nosuid,noexec 0,0 Here is the baselayout version: gentoo Base System version 1.12.1
Well, first of all upgrade to last stable baselayout at least (1.12.9) before reporting related bugs...
By the way, I corrected the filesystem problem. Now if I ctrl+c, I can get to the console. Looks fine when I'm there, besides the fact that my system time seems to have 2 timers working at the same time. If I type "date" , enter, "date", enter, (repeat a few times) I can see that there is 2 timers setting the time, with 10- minutes difference. lets say I type date, I get 11:00, I type it again I get 11:10, again, I get 11:00... so on. So I can't "upgrade"... I might reload with install cd, chroot and upgrade from there?
Well, I did chrooted from the install CD and I have entered emerge -auvDN world. I guess everything will be up to date. Let's hope it'll fixes the problem. thx for your fast reply by the way.
As said above, reopen if current stable baselayout doesn't work for you; I fail to see why you "can't upgrade" or how's date related to it.
94 updates later, I,m back with the same exact problem. My baselayout is now 1.12.9
So, is /dev/hdc1 *really* ext3? Do you have sys-fs/e2fsprogs installed (which version)? Does /sbin/fsck.ext3 -> e2fsck symlink exist?
As I said, I corrected the hdc1 problem, and it was my bad (I made a typo). My problem is the very first I reported. it just get in an infinite loop or waits for something it can't find without giving any error message at "Letting udev process events ..." and the [OK] doesnt appear so the problem is inside that part I guess. My hdc1 defenitly is ext4 (I can see it in cfdisk /dev/hdc). e2fsck and fsck.ext3 both works fine.
(In reply to comment #9) > defenitly is ext4 (I can see it in cfdisk /dev/hdc). ext4? And why do you have /dev/hdc1 /home ext3 noatime 0 0 in /etc/fstab? Plus what's your sys-fs/e2fsprogs version? I really ask the questions for a reason, so answer them before reopening this bug over and over again.
First, I want you to know I'm realy sory if I make mistakes and I am not making it for purpose. English isnt my first language (As you prolly noticed) thats why I might not explain myself perfectly. I appreciate your help and your fast reply. it's ext3, not ext4 (sry bout the typo again) My hard drives seems to load correctly. One of my network cards dont tho. sysprogs: sys-fs/e2fsprogs-1.39
i dont really see anything for us to "fix" ... just looks like a lot of hardware/kernel troubles
