mounting an ext4 filesystem from ext3(or reiser): What do I need?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
According to BOOTING.TXT (available at root directory of DVD):
Quote:
If you installed using the Slackware CDROM, you should boot from this CDROM
again and then load the kernel you used while installing, with additional
parameters to make it mount your hard drive's root partition. Let's assume
your root Linux partition is on /dev/hda2 and you used the 'sata.i' kernel.
To boot the system, you'd enter this command at the "boot: " prompt:
sata.i root=/dev/hda2 noinitrd ro
So I assumed that you used hugesmp.s kernel during the installation. If not, please change accordingly. There is no reason why you should not be able to boot into your root directory using the installation DVD/CD.
So after you booted, what can you see for example in /boot directory and are there /etc/lilo.conf and /etc/fstab files?
Also, it could be helpful to post the result of "mount".
mount says
proc on /proc type proc(rw)
sysfs on /sys ype sysfs(rw)
After booting I get a "Welcome to Slack installation disk"
....
You may now login as 'root'
After I log it says
"....
Just mount your Linux partitions under /mnt and type pkgtool
/boot is a link to /mnt/boot
In /etc there is no lilo.conf
There is an fstab which only has proc
Nevertheless, if I mount /dev/sdb3 (mount /dev/sdb3 /mnt/root) I see what is supposed to be there(e.g. the Slack 13 lilo)
After booting I get a "Welcome to Slack installation disk"
....
You may now login as 'root'
After I log it says
"....
Just mount your Linux partitions under /mnt and type pkgtool
Are you sure, you type in:
Code:
hugesmp.s root=/dev/sdb3 noinitrd ro
when you have the boot prompt after inserting the DVD.
The "Welcome..." message seems to indicate that you just pressed the ENTER key when you had the boot prompt.
The result is that you booted the installation DVD to prepare the installation but not as an emergency DVD to boot into your installed system.
plasmonics, when I do from root(in the non-Slack installation)
# zcat /proc/config.gz | grep -i ext4
zcat: /proc/config.gz: No such file or directory
so looks like no chance unless I upgrade the kernel
What this error means is that support for seeing the config options in the kernel via /proc was not configured into the kernel. But all is not lost. There should be a copy of the config file in /boot. You can grep it for ext4.
But it looks like the non-slack distro did not ship the kernel with ext4 support, because "mount -t ext4" normally works out of the box. You can either recompile the kernel with ext4 support or upgrade.
thanks. plasmonics, it's that the kernel does not have support for ext4, so I need to
upgrade
gegechris99, yes, ths is exactly what I type. Should I assume a defective DVD? It does not look that way(at least no other indications)
I'm sorry, but I found time to boot with my own DVD (actually created from -current in July 2009). The help information at boot prompt says that the syntax to boot into one's own system is:
Code:
hugesmp.s root=/dev/sdb3 rdinit= ro
I'm not sure if it will solve your issue but for me, it works. Actually I reach the kdm login but I have no mouse and no keyboard.
ok, so the problem was the noinitrd. Meanwhile I did a fresh slack install and now I got 13
booting with lilo fine. I still could not boot from the I guess that was because of the
noinitrd
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.