[SOLVED] system blocks at boot after change of filesystem

Nareto · 2010-11-24 22:25:15

hello,
I have separate partitions for /boot and /. I made a backup with fsarchiver of /, resized and reformated the partition to ext4 (it was jfs before) and recopied my backup on the fresh partition with:

fsarchiver restfs /media/backup_device/backup.fsa id=0,dest=/dev/sda3,mkfs=ext4

next I changed filesystem type in /etc/fstab from jfs to ext4, and rebooted (all of this was done on a live cd).

I get this error:

mount: mounting /dev/disk/by-uuid/[disk_uuid] on new_root failed: no such device

screenshot of the screen:

http://i.imgur.com/LiMHy.jpg

BTW fsarchiver restores the uuid, so that has actually not changed from my old jfs partition.

What could it be?

My guess is that it has something to do with kernel26.img in /boot (which has remained untouched) which is expecting a jfs partition... or no? If yes, how could I, on a live cd, install an appropriate .img?

thanks for any help,
renato

Last edited by Nareto (2010-11-25 07:34:41)

stqn · 2010-11-25 02:28:31

Last time I got this kind of error, it was because I had plugged my hard drive on the USB and the HOOKS line in /etc/mkinitcpio.conf lacked "usb" at the start. Maybe yours is missing something too? Mine looks like that:
HOOKS="base udev autodetect pata scsi sata lvm2 filesystems keymap usbinput"

(I've added "lvm2" because I use LVM volumes.)

If that's the problem, I think you'll have to chroot from the live CD into your root partition and run mkinitcpio. You'll probably find how to chroot on the wiki.

Last edited by stqn (2010-11-25 02:29:59)

TigTex · 2010-11-25 02:50:19

Try to use "/dev/sda" naming instead of UUID and why is that "new_root/" ? that makes no sense...

I would also add "ext4" to MODULES= line in mkinicpio.conf if you dont have the filesystem hook. Rebuild you image with mkinicpio -p kernel26. You'll have to chroot.

and by the way... remove that image... it's too big to post here

Last edited by TigTex (2010-11-25 02:52:15)

Nareto · 2010-11-25 07:34:19

thanks guys... I allready had "filesystems" in HOOKS so I just added "ext4" to MODULES and rebuild kernel26.img with the command TigTex gave, and now it boots

stqn · 2010-11-25 14:26:02

After a look at /lib/initcpio/install/filesystems and .../autodetect, it looks like the autodetect hook *should* detect filesystems inside LVM volumes (though I don't completely understand how it works)... It's strange it doesn't work on your machine.

Nareto · 2010-11-26 08:43:24

I have no idea what LVM is... from the little I read, I'd dare to say that I don't have it/use it on my system.

stqn · 2010-11-26 16:52:19

Err... sorry, I mixed things up
It's still weird though.

Arch Linux

#1 2010-11-24 22:25:15

[SOLVED] system blocks at boot after change of filesystem

#2 2010-11-25 02:28:31

Re: [SOLVED] system blocks at boot after change of filesystem

#3 2010-11-25 02:50:19

Re: [SOLVED] system blocks at boot after change of filesystem

#4 2010-11-25 07:34:19

Re: [SOLVED] system blocks at boot after change of filesystem

#5 2010-11-25 14:26:02

Re: [SOLVED] system blocks at boot after change of filesystem

#6 2010-11-26 08:43:24

Re: [SOLVED] system blocks at boot after change of filesystem

#7 2010-11-26 16:52:19

Re: [SOLVED] system blocks at boot after change of filesystem

Board footer