On Saturday, December 22, 2001, at 09:36 PM, Jeffrey Taylor wrote:
You need to add the ext3 module to INITRD_MODULES in /etc/rc.config,
Yes, I have already done this.
run mk_initrd script,
This too.
re-run lilo,
Oh. This bit is new for me, Let's try..... pared:~ # lilo Added linux * Added memtest86
and reboot.
:-( no joy. / is still ext2. from /var/log/boot.msg.... . . <4>VFS: Mounted root (ext2 filesystem) readonly. . . <6>Journalled Block Device driver loaded <6>kjournald starting. Commit interval 5 seconds <6>EXT3 FS 2.4-0.9.9, 5 Sep 2001 on ide0(3,1), internal journal <6>EXT3-fs: mounted filesystem with ordered data mode. <4>ide0: unexpected interrupt, status=0x58, count=1 . . /dev/hda1 on /boot type ext3 (rw) . . pared:~ # cat /proc/mounts /dev/root / ext2 rw 0 0 <--- no go, but why /dev/root? proc /proc proc rw 0 0 devpts /dev/pts devpts rw 0 0 /dev/hda1 /boot ext3 rw 0 0 <--- this one works shmfs /dev/shm shm rw 0 0 pared:~ # tune2fs -l /dev/hda3 | grep features Filesystem features: has_journal filetype sparse_super pared:~ # cat /etc/fstab /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 0 0 /dev/hda1 /boot ext3 defaults 0 0 /dev/fd0 /media/floppy auto noauto,user 0 0 proc /proc proc defaults 0 0 pared:~ #
Jeffrey
Quoting Gnu iBook 2
: Yes, I see that now, just found a nice page explaining it. (http://www.luv.asn.au/overheads/linux-startup.html)
So then it comes down to a problem with initrd not putting the ext3 module in the initial ramdisk?
On Saturday, December 22, 2001, at 09:04 PM, Jeffrey Taylor wrote:
This is what initrd is for, a initial ramdisk with needed modules. See the SuSE Handbook for details.
Jeffrey
Quoting Gnu iBook 2
: Ok. I got my /boot partition to convert to ext3. The key was running the tune2fs -j /dev/hda1 command with the partition unmounted.
Various documents say that it does not matter if the partition is mounted or not, but that was not the case for me.
Next I wanted to convert / to ext3 as well. I can only conclude that it is not possible with a stock SuSE kernel. I need to build a fresh kernel. This is because SuSE built the kernel with ext3 as a module, and the system can only load the modules from a mounted partition, so it mounts / ext2 in order to get to the modules. I don't think it is possible to then go back and remount / as ext3.
On Friday, December 21, 2001, at 02:16 PM, Nadeem Hasan wrote:
Gnu iBook 2 wrote:
OK, I tried it with jbd module as well, but no go. I still get the message during bootup:
<3>ext3: No journal on filesystem on ide0(3,1)
How do i get a journal on ide0(3,1)?
I ran tune2fs -j on /dev/hda1
On Thursday, December 20, 2001, at 12:17 PM, Purple Shirt wrote:
> you need jbd in conjunction with ext3 driver. go add it to > mk_initrd and rerun script and reboot. > > INITRD_MODULES="jbd ext3" >
Make sure you have the journal created. In my case:
# tune2fs -l /dev/hde2 | grep features Filesystem features: has_journal filetype needs_recovery sparse_super
If the has_journal does not appear, create the journal. If it fails, try to remove the .journal file from the filesystem. So if you are trying this on a filesystem /dev/hda1 mounted as /usr...u would do:
# cd /usr; rm .journal; tune2fs -j /dev/hda1
if you don't find a .journal....try:
# cd /usr/; chattr -i .journal; rm .journal; tune2fs -j /dev/hda1
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com