okay, I wanted to resize a few partitions with partition magic. When I loaded it (v.8) it would only give me the resize option for ext2 file systems and not ext3. The partition I want to resize is ext3, so I figured I would just make it ext2 and then change it back when I was done.
So, I had a hard time with tune2fs at first because it told me I would need to run it with the root partition read-only or unmounted. The first thing I tried was changing my rc.S script. I commented out the first line that remounted the root partition read only and I changed the second one to remount it ro instead of rw. I then tried to restart but got a bunch of errors and decided that was a bad idea. I changed the script back and booted from the slack cdrom.
I then mounted my normal root partition (hda2) on /mnt/root as read only and chrooted into /mnt/root. I ran
Code:
tune2fs -O ^has_journal /dev/hda2
and it finished. I then tried to run it on /dev/hda3 but it gave an error and said to run e2fsck. So I did and then ran tune2fs with no problems.
When I tried to boot back into them I get a kernel panic with the following messages:
Code:
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
read_super_block: can't find reiserfs filesystem on (dev 03:02, block 64, size 1024)
read_super_block: can't find reiserfs filesystem on (dev 03:02, block 64, size 1024)
Kernel panic: VFS: Unable to mount root fs on 03:02
But here is the funny part (its not funny at all
) I can boot into that same partition with my slack cd using:
Code:
bare.i root=/dev/hda2 noinitrd ro
So, I guess I really don't understand enough about this whole process to figure out why there is a difference. Why would one kernel boot but not another? I didn't change anything even remotely assosciated with the kernel.
Help would be greately appreciated. I am at work and would hate it if I have to boot into windoz for the rest of the day.
--UPDATE
I am now really frustrated. I used my old kernel to boot and it WORKED!!! BUT WHY??? I DIDN'T CHANGE ANYTHING ON THE KERNEL DID I?
--UPDATE
Uh...don't compile the kernel without ext2 support ... he he
--UPDATE
Okay...I only post this in case anyone can use the information. I do have a question though. Does slackware do something different with their ext2 file system? I have had 3 situations now where other programs have said that my ext2 partitions were different. partition magic said my "file version" was not supported, and parted said it had an "incapatable attribute". Anyone know why this is happening?
