----- Original Message ----- From: "Jan Schmidt" <[EMAIL PROTECTED]> Subject: Re: [SLUG] b0rked system
> <quote who="Rob B"> > > > I then ran tune2fs -j /dev/sda1 through 4 to add the journal, and changed > > /etc/fstab to make the drives mount ext3 at boot. Before rebooting, I > > re-made the kernel package with some network settings I had forgotten > > (didn't remove any config)and installed it, and rebooted - following the > > default questions re lilo all the way. Now the drives aren't being mounted > > at all. I can boot into tomsrtbt rescue disk and mount the drive fine to do > > an fsck on it, but once I boot back into Debian the problem remains. > > Well, it sounds like your new kernel can't mount ext3 drives, or is it that > you've left out SCSI support? I thought so as well, but both the controller and the disks are detected. I also checked the .config file and both the correct SCSI devices and ext3 are included in it. > First I would try booting from the emergency disk, mount the root partition > and modify /etc/fstab back to ext2 again. ext3 partitions are backwards > compatible and will load as ext2. > > If that doesn't work, I would next try using the emergency disk to boot the > root system you already have by giving the lilo prompt on the emergency disk > a boot command like: > > boot> linux root=/dev/sda1 Since my emergency disk decided to cark it, I tried booting from the Deb rescue disk, this worked OK, but hammered me with module dependency problems due to it being kernel 2.2.20, and I have no 2.2.20 modules.dep file. I will try again with the rescue disk from the bf2.4 directory tonight. Thanks for the help, Rob -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
