I had a LFS system up and running on /dev/sda4. I needed more space so I made a image of the LFS partition, deleted sda4, made it into an extended partition, and made new linux partitions sda5 and sda6. I then transferred the saved LFS partition to /dev/sda6.
I then booted to the live CD, mounted /dev/sda6, edited the grub menu to point to the new partion, and edited /etc/fstab to mount the new partition as root. But when I boot up now, the kernel gives several errors while attempting to "access beyond end of device" on sda4, unable to read superblock. Then it says Kernel panic - not syncing: VFS: Unable to mount rootfs on unknown block(8,4) I noticed that mtab still had a reference to sda4 so I removed it, but I still have the same problem. Why is the kernel still attempting to access sda4, which is now an extended partition table? Grub knows to look on (hd0,5) (i.e. /dev/sda6) and finds the kernel there, so I don't understand why the kernel itself is looking for sda4. - Joe -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
