udev breaking the booting process

nomorewindows · 2012-01-28 01:31:34

Do an fdisk -l, and if you can remember what partitions you put where based on their size and/or placement you can almost guess which one is which.
You can't do mkinitcpio until you've mounted the partitions and schrooted. At least not your installation you're trying to fix.
The /dev/sda3 partition is being mounted to /mnt/sda3 (whatever /dev/sda3 is in your filesystem). If you're confused just reboot and start fresh.

ilkyest · 2012-01-28 02:31:26

Some time ago, I was trying install arch from a damaged recorded ISO file...... well. I must start with noapic, why? In other side, I couldnt start a recovery try. No editing, no access to tty, well..... just a slave from my system

with noapic, just with noapic, that I could try solve my system. Some of the issues I've solved like pals wrote above, but, after three days, I downloades a new ISO, check md5sum and restart.... 'cause it was so anoying

leberyo · 2012-01-28 16:29:58

nomorewindows wrote:

Do an fdisk -l, and if you can remember what partitions you put where based on their size and/or placement you can almost guess which one is which.
You can't do mkinitcpio until you've mounted the partitions and schrooted. At least not your installation you're trying to fix.
The /dev/sda3 partition is being mounted to /mnt/sda3 (whatever /dev/sda3 is in your filesystem). If you're confused just reboot and start fresh.

I found an old post of mine with my mtab in it:
#UUID=8C6085FC6085ED70 /mnt/windows ntfs-3g defaults,noatime 0 0
/dev/sda2 /boot ext3 defaults 0 1
/dev/sda3 / ext4 defaults,noatime 0 1
/dev/sda5 /tmp ext4 defaults,nosuid,nodev 0 1
/dev/sda6 /var ext4 defaults,nosuid,nodev 0 1
/dev/sda7 /usr ext4 defaults,noatime,rw,nodev 0 1
/dev/sda8 swap swap defaults 0 0
/dev/sda9 /home ext4 defaults,noatime,nosuid,nodev 0 1

So, with my Puppy Linux LiveCd, I'll edit the mtab with these settings. Then,

mount /dev/sda2 /boot
mount /dev/sda3 /
mount /dev/sda5 /tmp
mount /dev/sda6 /var
mount /dev/sda7 /usr
mount /dev/sda8 swap
mount /dev/sda9 /home

After that, I should be able to reboot and have command prompt again, at which point I run
chroot /mnt

Then

mkinitcpio -p linux

Anything I'm missing??? Really appreciate all the help guys.

nomorewindows · 2012-01-28 16:45:12

Hold on there. You want to mount all of that under /mnt and then it will automatically show up in your live CD /etc/mtab.
Mount your / first under /mnt: mount /dev/sda3 /mnt, then mount /dev/sda2 /mnt/boot, then mount (you'll need this) /dev/sda7 /mnt/usr. You only need to mount what is necessary to repair the system, not necessarily every partition on the drive. When you have mounted this way, now try to chroot /mnt. This is where we can expect an error stating kernel is too old or a new prompt under your normal system with /.

Mkinitcpio -p (means preset-which isn't necessary)
Mkinitcpio -k /boot/your-kernel -c /etc/mkinitcpio.conf -g /boot/your-initramfs-image

If mkinitcpio doesn't give any errors during its' process, back out of the chroot and umount everything under /mnt (just to make sure the disk writes are committed), and then init 6 or reboot.

Last edited by nomorewindows (2012-01-28 16:52:04)

leberyo · 2012-01-28 22:30:40

I was able to mount my previous partitions and chrooted.

Now do I just do

Mkinitcpio -k /boot/your-kernel -c /etc/mkinitcpio.conf -g /boot/your-initramfs-image
Can you please give me an example of this? Do I have to know what kernel version and inert it in "your-kernel"?

or do I just
mkinitcpio -p ???

Thx I'm almost there...

TheSaint · 2012-01-29 12:27:53

I had similar problem like the OP.
The error was that /home already mounted. I solved by removing the udev rule, but the mess still around.
I can't get to my original /home, it seems that the booting process ignore /etc/fstab as here below

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /tmp           tmpfs   nodev,nosuid,nodiratime,size=1024M,mode=1777      0  0
none                   /var/run       tmpfs   nodev,nosuid,mode=1777      0  0
none                   /var/lock      tmpfs   nodev,nosuid,mode=1777      0  0

# devpts                 /dev/pts      devpts    defaults            0      0
# shm                    /dev/shm      tmpfs     nodev,nosuid        0      0

LABEL=arch64           /              ext3     defaults            0      1
LABEL=Swap             swap           swap     defaults            0      0
LABEL=Home             /home          ext3     defaults            0      1
none                   /proc/bus/usb  usbfs    auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0

and

ls -lF /dev/disk/by-label/
total 0
lrwxrwxrwx 1 root root 10 Jan 29 19:21 Acer -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 29 19:21 BigStor -> ../../sda8
lrwxrwxrwx 1 root root 10 Jan 29 19:21 Home -> ../../sda6
lrwxrwxrwx 1 root root 15 Jan 29 19:21 PhotoData -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 10 Jan 29 19:21 Root -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 29 19:21 Swap -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 29 19:21 arch64 -> ../../sda7

by confusion I delete /etc/mtab with the idea to resolve the problem.
What's the matter in my case?

EDIT
moving here
Maybe found a solution

Last edited by TheSaint (2012-01-30 05:04:12)

t1nk3r3r · 2012-03-23 07:07:27

I had a big upgrade to my system (trying to solve other problems). Then fsck started complaining about my usr partition being mounted (now being handled by udev before fsck got a chance to run).

Booted from a live-cd to manually run fsck on said partition (passed).
Noticed one thread that said to append 'fastboot' on kernel line in grub to bypass fsck altogether.
Got a working command line and added 'fsck' to hooks in mkinitcpio.conf.
Regenerate initramfs (mkinitcpio -p linux).
Reboot succeeds w/o 'fastboot' option.

Arch Linux

#26 2012-01-28 01:31:34

Re: udev breaking the booting process

#27 2012-01-28 02:31:26

Re: udev breaking the booting process

#28 2012-01-28 16:29:58

Re: udev breaking the booting process

#29 2012-01-28 16:45:12

Re: udev breaking the booting process

#30 2012-01-28 22:30:40

Re: udev breaking the booting process

#31 2012-01-29 12:27:53

Re: udev breaking the booting process

#32 2012-03-23 07:07:27

Re: udev breaking the booting process

Board footer