Re: new hard drive install
On Wed, 30 Jun 1999, charles kaufman wrote: > > Hi > > Not necessary. Recently i repartitioned my HD, moved Linux from hda2 to > > hda1. Never had any trouble after i restored my filesystem from backups > > and reran lilo (after editing lilo.conf and fstab) > > I did almost that. Instead of restoring from backups I had the old and > the new hard drives mounted at the same time and used cpio. > Did you have to tell the kernel where the new swap partition was? i had two hard drives, but the one i was repartitioning had the entire Linux installation on it at the time. So i tar-gzipped everything to the other drive (which fortunately had the space), popped in my old hamm installation floppy, repartitioned, used zcat and star off the floppy--fortunately i had tarred / into a separate tarball from /usr and other unessential stuff, because that tarball was the only one star managed to handle! i then resolved to make a new boot disk for myself one of these days ;) Didn't have to tell the kernel that either... i used the "initialize swap partition" option on the installation floppy when i was repartitioning, then just changed fstab.
Re: new hard drive install
On Thu, 1 Jul 1999, David Wright wrote: >> > Yes it really says FAT 12 > > ... which you presumably don't have. (Actually I just saw my Certainly not due to anything I did (on purpose, that is). > very first FAT12 partition yesterday when I was mending someone's > disk geometry settings. It was 9MB in size, which I'd guess might > be too small for FAT16.) So it's picking up garbage. > > > fdisk -l > > Disk /dev/hda: 255 Heads 63 Sectors 1027 Cylinders > > Units =Cylinders of 16065*512 bytes > > > > Device Boot Begin Start End Blocks Id System > > /dev/hda1 *11 64 51408+ 6 DOS 16 bit>=32M > > /dev/hda2 * 65 65192 1028160 83 Linux native > > /dev/hda3 193 193205 104422+ 82 Linux swap > > Segmentation fault. > > Doesn't that raise the question as to how you partitioned the disk > in the first place? Presumably that didn't segfault or you wouldn't > have been able to write the partition table at all. It was the same program-linux fdisk. > > Did you use a different program, in which case what does it say > and does it agree with the above? Or did you use the same program > in which case it's a bit worrying that a program can write a > partition table which it itself can't then read. It looks like I should repartition the disc and try again. It just seemed so close to working. And the error message is so clear. Oh well. Thanks again for the help. Chuck Kaufman
Re: new hard drive install
Quoting Brad ([EMAIL PROTECTED]): > On Tue, 29 Jun 1999, David Wright wrote: > > > Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to > > c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it. ^^^ > > Typerdev kernel-imageto see what it's set to and > > rdev kernel-image /dev/hda2to set it. This saves having to tell it > > where root is every time you boot it. > > Not necessary. Recently i repartitioned my HD, moved Linux from hda2 to > hda1. Never had any trouble after i restored my filesystem from backups > and reran lilo (after editing lilo.conf and fstab) Loadlin is not lilo. The "Yes" was answering the question as put, which was IIRC "Does the kernel have a place in which it remembers its root device". (But this was before it was revealed that there were far more serious error messages than a kernel panic.) Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: new hard drive install
Quoting charles kaufman ([EMAIL PROTECTED]): > > > On Tue, 29 Jun 1999, Brad wrote: > >> > Yes it really says FAT 12 ... which you presumably don't have. (Actually I just saw my very first FAT12 partition yesterday when I was mending someone's disk geometry settings. It was 9MB in size, which I'd guess might be too small for FAT16.) So it's picking up garbage. > > > > What does Linux "fdisk -l" show? > > Here it is. The segmentation fault at the end is > part of the output.(not encouraging) > The disk is not all partitioned. > > fdisk -l > > The number of cylinders for this disk is set to 1027. This is > larger than 1024 and may cause problems with > 1)software that runs at boot time (e.g. LILO) > 2)booting and partitioning software from other OS's (e.g. > DOS FDISK, OS/2 FDISK) > > Disk /dev/hda: 255 Heads 63 Sectors 1027 Cylinders > Units =Cylinders of 16065*512 bytes > > Device Boot Begin Start End Blocks Id System > /dev/hda1 *11 64 51408+ 6 DOS 16 bit>=32M > /dev/hda2 * 65 65192 1028160 83 Linux native > /dev/hda3 193 193205 104422+ 82 Linux swap > Segmentation fault. Doesn't that raise the question as to how you partitioned the disk in the first place? Presumably that didn't segfault or you wouldn't have been able to write the partition table at all. Did you use a different program, in which case what does it say and does it agree with the above? Or did you use the same program in which case it's a bit worrying that a program can write a partition table which it itself can't then read. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: new hard drive install
On Tue, 29 Jun 1999, Brad wrote: >> > Yes it really says FAT 12 > > What does Linux "fdisk -l" show? Here it is. The segmentation fault at the end is part of the output.(not encouraging) The disk is not all partitioned. fdisk -l The number of cylinders for this disk is set to 1027. This is larger than 1024 and may cause problems with 1)software that runs at boot time (e.g. LILO) 2)booting and partitioning software from other OS's (e.g. DOS FDISK, OS/2 FDISK) Disk /dev/hda: 255 Heads 63 Sectors 1027 Cylinders Units =Cylinders of 16065*512 bytes Device Boot Begin Start End Blocks Id System /dev/hda1 *11 64 51408+ 6 DOS 16 bit>=32M /dev/hda2 * 65 65192 1028160 83 Linux native /dev/hda3 193 193205 104422+ 82 Linux swap Segmentation fault. Chuck Kaufman
Re: new hard drive install
On Mon, 28 Jun 1999, Stephen Pitts wrote:> > > Check the boot= in LILO. I just recently had similar problems and it turned > out that I was writing my new lilo to /dev/hda1 instead of /dev/hda. Thanks. I've tried each of those and get the same error either way. Chuck Kaufman
Re: new hard drive install
Hi > Not necessary. Recently i repartitioned my HD, moved Linux from hda2 to > hda1. Never had any trouble after i restored my filesystem from backups > and reran lilo (after editing lilo.conf and fstab) I did almost that. Instead of restoring from backups I had the old and the new hard drives mounted at the same time and used cpio. Did you have to tell the kernel where the new swap partition was? Chuck Kaufman
Re: new hard drive install
On Mon, Jun 28, 1999 at 05:27:59PM -0500, Brad wrote: > On Mon, 28 Jun 1999, charles kaufman wrote: > > > I partitioned the new drive with hda1 as dos, hda2 as linux native, hda3 > > as linux swap. I copied (only) dos c: to hda1, and all of the linux > > to hda2. I altered lilo.conf to reflect these changes > > and ran lilo; I changed fstab. I also ran mkswap. > > Now with the new drive on the first ide socket I get the lilo prompt ok. > > If I choose dos, then dos boots and runs ok. But if I choose linux, the > > boot process runs part way and then hangs with a kernel panic after > > the partition check, with the message > > "kernel panic:VFS:Unable to mount root fs on 03:03" > > It's still trying to mount root from hda3. i don't know why, since you say > you've checked and rechecked to make sure /etc/lilo.conf is correct and > you've run lilo with the correct settings... > > Since i can't think of anything else, is the device correct? > $ ls -l /dev/hda2 > brw-rw 1 root disk 3, 2 Jun 17 22:13 /dev/hda2 > ^^ > > > The partition check gives "hda: hda1 hda2 hda3" which is what I think it > > should give. > > That's right. > > > I've checked and rechecked the lilo.conf stanza for linux > > and it says root=/dev/hda2 > > and the fstab entry is the same. > > Can anyone suggest what I've missed or forgotten? I'll supply > > more details if needed of course. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > Check the boot= in LILO. I just recently had similar problems and it turned out that I was writing my new lilo to /dev/hda1 instead of /dev/hda. -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: new hard drive install
On Tue, 29 Jun 1999, Charles Kaufman wrote: > On Tue, 29 Jun 1999, David Wright wrote: > > > Quoting charles kaufman ([EMAIL PROTECTED]): > "kernel panic:VFS:Unable to mount root fs on 03:03" > > > > I think that may change everything. Allowing for typos, because you > > copied that off the screen, did it really say FAT 12? It looks as > > though it's either misread the partition table (perhaps it got the > > geometry wrong or something) or the kernel lacks some necessary > > functionality to handle the new disk. What does lsmod show when you > > have the disk on /mnt. Is it using a module to get at that disk? > > Could your partitions be misnumbered in some way? > > > > Either way, I think you may need more expert help than I can provide. > > Yes it really says FAT 12 (twice). That has seemed strange to me too. What does Linux "fdisk -l" show?
Re: new hard drive install
On Tue, 29 Jun 1999, David Wright wrote: > Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to > c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it. > Typerdev kernel-imageto see what it's set to and > rdev kernel-image /dev/hda2to set it. This saves having to tell it > where root is every time you boot it. Not necessary. Recently i repartitioned my HD, moved Linux from hda2 to hda1. Never had any trouble after i restored my filesystem from backups and reran lilo (after editing lilo.conf and fstab)
Re: new hard drive install
Hi Thanks again. On Tue, 29 Jun 1999, David Wright wrote: > Quoting charles kaufman ([EMAIL PROTECTED]): "kernel panic:VFS:Unable to mount root fs on 03:03" > I think that may change everything. Allowing for typos, because you > copied that off the screen, did it really say FAT 12? It looks as > though it's either misread the partition table (perhaps it got the > geometry wrong or something) or the kernel lacks some necessary > functionality to handle the new disk. What does lsmod show when you > have the disk on /mnt. Is it using a module to get at that disk? > Could your partitions be misnumbered in some way? > > Either way, I think you may need more expert help than I can provide. Yes it really says FAT 12 (twice). That has seemed strange to me too. The root device had been set as /dev/hda3; the lilo option should have changed that on the fly, as you say, but not the swap device. rdev changed them both, and they are now set to /hda2 and /hda3 in the kernel. But as I said in my last note it still fails with the same message. insmod reports nothing. There are no modules loaded. IDE support is compiled in, I believe, since it has never needed any insmod 's. (by the way it was man rdev not man lilo that said rdev isn't needed- my mistake) Chuck Kaufman
Re: new hard drive install
Quoting charles kaufman ([EMAIL PROTECTED]): > Hello again > > On Tue, 29 Jun 1999, David Wright wrote: > > > Quoting charles kaufman ([EMAIL PROTECTED]): > > > "kernel panic:VFS:Unable to mount root fs on 03:03" > > > > > > > Is there somewhere in the kernel that remembers it used to boot from > > > /dev/hda3?> > > > > Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to > > c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it. > > Typerdev kernel-imageto see what it's set to and > > rdev kernel-image /dev/hda2to set it. This saves having to tell it > > where root is every time you boot it. > > Thanks. > > But the lilo manpage says rdev is no longer needed since the parameters > can be set from the lilo prompt. No, but I answered the question as posed. I would guess that lilo just modifies the same bytes as rdev does, but on the fly as it loads the kernel. > I tried it anyway. With the new drive at /mnt, I did > rdev /mnt/vmlinuz /dev/hda2, and > rdev -s /mnt/vmlinuz /dev/hda3. > > I then then reattached the new drive onto the first ide connector and > rebooted. It failed in exactly the same way as before. > > In case they contains any hints, here are the messages which immediately > precede the panic: > > partition check: > hda: hda1 hda2 hda3 > [MS-DOS FS Rel.12, FAT 12, check=n,conv=b,uid=0,gid=0,umask=022] > [me=oxff,cs=32385,#f=255,fs=65409,fl=65409,ds=33024,de=65535,data=37215, > se=65635,ts=-1,ls=65535,rc=0,fc=4294967295] > Transaction block size=512 > UMSDOS Beta 0.6 (compatability level 0.4 fast msdos) > > the lines from [MSDOS.. to Transaction.. are then repeated, > and then it says > Kernel panic : VFS Unable to mount root fs on 03:03. I think that may change everything. Allowing for typos, because you copied that off the screen, did it really say FAT 12? It looks as though it's either misread the partition table (perhaps it got the geometry wrong or something) or the kernel lacks some necessary functionality to handle the new disk. What does lsmod show when you have the disk on /mnt. Is it using a module to get at that disk? Could your partitions be misnumbered in some way? Either way, I think you may need more expert help than I can provide. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: new hard drive install
Hello again On Tue, 29 Jun 1999, David Wright wrote: > Quoting charles kaufman ([EMAIL PROTECTED]): > > "kernel panic:VFS:Unable to mount root fs on 03:03" > > > > Is there somewhere in the kernel that remembers it used to boot from > > /dev/hda3?> > Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to > c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it. > Typerdev kernel-imageto see what it's set to and > rdev kernel-image /dev/hda2to set it. This saves having to tell it > where root is every time you boot it. Thanks. But the lilo manpage says rdev is no longer needed since the parameters can be set from the lilo prompt. I tried it anyway. With the new drive at /mnt, I did rdev /mnt/vmlinuz /dev/hda2, and rdev -s /mnt/vmlinuz /dev/hda3. I then then reattached the new drive onto the first ide connector and rebooted. It failed in exactly the same way as before. In case they contains any hints, here are the messages which immediately precede the panic: partition check: hda: hda1 hda2 hda3 [MS-DOS FS Rel.12, FAT 12, check=n,conv=b,uid=0,gid=0,umask=022] [me=oxff,cs=32385,#f=255,fs=65409,fl=65409,ds=33024,de=65535,data=37215, se=65635,ts=-1,ls=65535,rc=0,fc=4294967295] Transaction block size=512 UMSDOS Beta 0.6 (compatability level 0.4 fast msdos) the lines from [MSDOS.. to Transaction.. are then repeated, and then it says Kernel panic : VFS Unable to mount root fs on 03:03. Thanks again Chuck Kaufman
Re: new hard drive install
Quoting charles kaufman ([EMAIL PROTECTED]): > > Hi > Thanks Brad. > On Mon, 28 Jun 1999, Brad wrote: > > > > "kernel panic:VFS:Unable to mount root fs on 03:03" > > > > It's still trying to mount root from hda3. i don't know why, since you say > > you've checked and rechecked to make sure /etc/lilo.conf is correct and > > you've run lilo with the correct settings... > > > > Since i can't think of anything else, is the device correct? > > $ ls -l /dev/hda2 > > brw-rw 1 root disk 3, 2 Jun 17 22:13 /dev/hda2 > > ^^ > > > ls -l /dev/hda2 gives > brw-r--r-- 1 root root 3,2 Jul 28 1998 /dev/hda2 > > That's before it's mounted-I have been booting with tomsrtbt (thanks > to Tom!) so it might be different if it actually boots from that device. > > Is there somewhere in the kernel that remembers it used to boot from > /dev/hda3? Yes. When you copy a kernel (e.g. I copy /boot/vmlinuz to c:\loadlin\zimage for loadlin to boot from dos) you need to rdev it. Typerdev kernel-imageto see what it's set to and rdev kernel-image /dev/hda2to set it. This saves having to tell it where root is every time you boot it. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: new hard drive install
Hi Thanks Brad. On Mon, 28 Jun 1999, Brad wrote: > > "kernel panic:VFS:Unable to mount root fs on 03:03" > > It's still trying to mount root from hda3. i don't know why, since you say > you've checked and rechecked to make sure /etc/lilo.conf is correct and > you've run lilo with the correct settings... > > Since i can't think of anything else, is the device correct? > $ ls -l /dev/hda2 > brw-rw 1 root disk 3, 2 Jun 17 22:13 /dev/hda2 > ^^ > ls -l /dev/hda2 gives brw-r--r-- 1 root root 3,2 Jul 28 1998 /dev/hda2 That's before it's mounted-I have been booting with tomsrtbt (thanks to Tom!) so it might be different if it actually boots from that device. Is there somewhere in the kernel that remembers it used to boot from /dev/hda3? chuck
Re: new hard drive install
On Mon, 28 Jun 1999, charles kaufman wrote: > I partitioned the new drive with hda1 as dos, hda2 as linux native, hda3 > as linux swap. I copied (only) dos c: to hda1, and all of the linux > to hda2. I altered lilo.conf to reflect these changes > and ran lilo; I changed fstab. I also ran mkswap. > Now with the new drive on the first ide socket I get the lilo prompt ok. > If I choose dos, then dos boots and runs ok. But if I choose linux, the > boot process runs part way and then hangs with a kernel panic after > the partition check, with the message > "kernel panic:VFS:Unable to mount root fs on 03:03" It's still trying to mount root from hda3. i don't know why, since you say you've checked and rechecked to make sure /etc/lilo.conf is correct and you've run lilo with the correct settings... Since i can't think of anything else, is the device correct? $ ls -l /dev/hda2 brw-rw 1 root disk 3, 2 Jun 17 22:13 /dev/hda2 ^^ > The partition check gives "hda: hda1 hda2 hda3" which is what I think it > should give. That's right. > I've checked and rechecked the lilo.conf stanza for linux > and it says root=/dev/hda2 > and the fstab entry is the same. > Can anyone suggest what I've missed or forgotten? I'll supply > more details if needed of course.
new hard drive install
Hi. I am trying to switch my debian 2.0 to a new hard drive. It was on a drive partitioned with dos on hda1 and hda2 and linux native and linux swap on hda3 and hda4 resp.; I partitioned the new drive with hda1 as dos, hda2 as linux native, hda3 as linux swap. I copied (only) dos c: to hda1, and all of the linux to hda2. I altered lilo.conf to reflect these changes and ran lilo; I changed fstab. I also ran mkswap. Now with the new drive on the first ide socket I get the lilo prompt ok. If I choose dos, then dos boots and runs ok. But if I choose linux, the boot process runs part way and then hangs with a kernel panic after the partition check, with the message "kernel panic:VFS:Unable to mount root fs on 03:03" The partition check gives "hda: hda1 hda2 hda3" which is what I think it should give. I've checked and rechecked the lilo.conf stanza for linux and it says root=/dev/hda2 and the fstab entry is the same. Can anyone suggest what I've missed or forgotten? I'll supply more details if needed of course. Thanks. chuck
