Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Wed, Jul 02, 2008 at 10:36:33AM +0100, Anthony Campbell wrote: > On 02 Jul 2008, Anthony Campbell wrote: > > On 02 Jul 2008, Andrei Popescu wrote: > > > On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote: > > > > > > > Sorry, I hadn't read the e2label line properly. But I don't think it > > > > would affect the issue I encountered here, which was a change in the > > > > actual partition referred to. The label would still be referring to > > > > the wrong partition. Still, now that I know this can happen I will not > > > > be caught by it in the future. > > > > > > Would you mind posting "fdisk -l" for both kernels (or just tell us if > > > there is a difference). I'm guessing your problem is elsewhere and > > > labels would help avoid it. > > > > > > > They are identical. > > > > As an experiment, I tried changing root=/dev/hdb9 to root=/dev/hdb10 for > the previous kernel (2.6.23) and that booted as well! So it looks as if > the earlier kernel could use either setting but the later one only > accepts /dev/hdb10. > > Is grub perhaps more flexible about this than I thought? AFAIUI grub only passes that information to the kernel. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 02 Jul 2008, Anthony Campbell wrote: > On 02 Jul 2008, Andrei Popescu wrote: > > On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote: > > > > > Sorry, I hadn't read the e2label line properly. But I don't think it > > > would affect the issue I encountered here, which was a change in the > > > actual partition referred to. The label would still be referring to > > > the wrong partition. Still, now that I know this can happen I will not > > > be caught by it in the future. > > > > Would you mind posting "fdisk -l" for both kernels (or just tell us if > > there is a difference). I'm guessing your problem is elsewhere and > > labels would help avoid it. > > > > They are identical. > As an experiment, I tried changing root=/dev/hdb9 to root=/dev/hdb10 for the previous kernel (2.6.23) and that booted as well! So it looks as if the earlier kernel could use either setting but the later one only accepts /dev/hdb10. Is grub perhaps more flexible about this than I thought? Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 02 Jul 2008, Andrei Popescu wrote: > On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote: > > > Sorry, I hadn't read the e2label line properly. But I don't think it > > would affect the issue I encountered here, which was a change in the > > actual partition referred to. The label would still be referring to > > the wrong partition. Still, now that I know this can happen I will not > > be caught by it in the future. > > Would you mind posting "fdisk -l" for both kernels (or just tell us if > there is a difference). I'm guessing your problem is elsewhere and > labels would help avoid it. > They are identical. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 02 Jul 2008, Andrei Popescu wrote: > On Wed, Jul 02, 2008 at 09:09:00AM +0100, Wackojacko wrote: > > > I think you should be asking yourself how the old kernel boots with hdb9. > > Grub numbering system starts from 0 so hd(0,0) is hda1 and hda(1,9) is > > hdb10 etc. Are you sure you don't have another debian/linux install on > > hdb9 :). > > Yeah, something similar happened to me :) That's when I labeled all my > partitions! > > Regards, > Andrei > -- > If you can't explain it simply, you don't understand it well enough. > (Albert Einstein) Yes, I know that grub numbers things this way but there is nothing on /dev/hdb9 except for lost+found. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Wed, Jul 02, 2008 at 09:09:00AM +0100, Wackojacko wrote: > I think you should be asking yourself how the old kernel boots with hdb9. > Grub numbering system starts from 0 so hd(0,0) is hda1 and hda(1,9) is > hdb10 etc. Are you sure you don't have another debian/linux install on > hdb9 :). Yeah, something similar happened to me :) That's when I labeled all my partitions! Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Wed, Jul 02, 2008 at 10:37:19AM +0300, Andrei Popescu wrote: > On Tue, Jul 01, 2008 at 03:40:12PM -0500, Hugo Vanwoerkom wrote: > > > and did you use a vga= parm? And did that work? > > $ dmesg | grep vga\=791 > [0.00] Kernel command line: root=LABEL=sid ro vga=791 > > $ uname -a > Linux think 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 GNU/Linux Sorry, you probably also want: $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote: > Sorry, I hadn't read the e2label line properly. But I don't think it > would affect the issue I encountered here, which was a change in the > actual partition referred to. The label would still be referring to > the wrong partition. Still, now that I know this can happen I will not > be caught by it in the future. Would you mind posting "fdisk -l" for both kernels (or just tell us if there is a difference). I'm guessing your problem is elsewhere and labels would help avoid it. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
Anthony Campbell wrote: On 02 Jul 2008, Bob Cox wrote: On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED]) wrote: I don't understand label in this context. Where is it set? This was explained by Florian Kulzer earlier in this thread. (It was such a good explanation I kept it for future reference!) On Mon, Jun 30, 2008 at 12:30:00 +0200, Florian Kulzer ([EMAIL PROTECTED]) wrote: You can use UUIDs or labels to refer to the partitions. This is robust if a newer kernel changes the device nodes (e.g. from /dev/hda to /dev/sda). You can use the "blkid" utility to find out the UUIDs of your partitions, or you can set your own labels with e2label (and mkswap -L for the swap partition). To give you an example, I labeled my root partition "root" and this is the corresponding fstab entry: LABEL=root / ext3defaults,errors=remount-ro 0 1 If you want to use UUIDs then the syntax is "UUID=". -- Sorry, I hadn't read the e2label line properly. But I don't think it would affect the issue I encountered here, which was a change in the actual partition referred to. The label would still be referring to the wrong partition. Still, now that I know this can happen I will not be caught by it in the future. Anthony I think you should be asking yourself how the old kernel boots with hdb9. Grub numbering system starts from 0 so hd(0,0) is hda1 and hda(1,9) is hdb10 etc. Are you sure you don't have another debian/linux install on hdb9 :). Anyhow glad you got it fixed. Wackojacko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 02 Jul 2008, Bob Cox wrote: > On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED]) > wrote: > > > I don't understand label in this context. Where is it set? > > This was explained by Florian Kulzer earlier in this thread. (It was > such a good explanation I kept it for future reference!) > > On Mon, Jun 30, 2008 at 12:30:00 +0200, Florian Kulzer > ([EMAIL PROTECTED]) wrote: > > > You can use UUIDs or labels to refer to the partitions. This is > > robust if a newer kernel changes the device nodes (e.g. from /dev/hda to > > /dev/sda). You can use the "blkid" utility to find out the UUIDs of your > > partitions, or you can set your own labels with e2label (and mkswap -L > > for the swap partition). > > > > To give you an example, I labeled my root partition "root" and this is > > the corresponding fstab entry: > > > > LABEL=root / ext3defaults,errors=remount-ro 0 1 > > > > If you want to use UUIDs then the syntax is "UUID=". > > -- Sorry, I hadn't read the e2label line properly. But I don't think it would affect the issue I encountered here, which was a change in the actual partition referred to. The label would still be referring to the wrong partition. Still, now that I know this can happen I will not be caught by it in the future. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Tue, Jul 01, 2008 at 03:40:12PM -0500, Hugo Vanwoerkom wrote: > and did you use a vga= parm? And did that work? $ dmesg | grep vga\=791 [0.00] Kernel command line: root=LABEL=sid ro vga=791 $ uname -a Linux think 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 GNU/Linux Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED]) wrote: > I don't understand label in this context. Where is it set? This was explained by Florian Kulzer earlier in this thread. (It was such a good explanation I kept it for future reference!) On Mon, Jun 30, 2008 at 12:30:00 +0200, Florian Kulzer ([EMAIL PROTECTED]) wrote: > You can use UUIDs or labels to refer to the partitions. This is > robust if a newer kernel changes the device nodes (e.g. from /dev/hda to > /dev/sda). You can use the "blkid" utility to find out the UUIDs of your > partitions, or you can set your own labels with e2label (and mkswap -L > for the swap partition). > > To give you an example, I labeled my root partition "root" and this is > the corresponding fstab entry: > > LABEL=root / ext3defaults,errors=remount-ro 0 1 > > If you want to use UUIDs then the syntax is "UUID=". -- Bob Cox. Stoke Gifford, near Bristol, UK. Registered user #445000 with the Linux Counter - http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 01 Jul 2008, Andrei Popescu wrote: > On Tue, Jul 01, 2008 at 10:02:39AM +0100, Anthony Campbell wrote: > > > Well, I finally found the answer but it's very odd. I don't think it > > should work but it does. I put the "wrong" root entry in > > /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this > > kernel seems to need /dev/hdb10. Here is the relevant section of the > > file: > > Just use labels and you'll never need to worry about this stuff. Find > the line starting with '# kopt' and edit to your needs. Here is mine: > > $ grep ^#\ kopt /boot/grub/menu.lst > # kopt=root=LABEL=sid ro vga=791 > > Don't forget to run 'update-grub' as root afterwards. > I don't understand label in this context. Where is it set? Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On Tue, Jul 01, 2008 at 10:02:39AM +0100, Anthony Campbell wrote: > Well, I finally found the answer but it's very odd. I don't think it > should work but it does. I put the "wrong" root entry in > /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this > kernel seems to need /dev/hdb10. Here is the relevant section of the > file: Just use labels and you'll never need to worry about this stuff. Find the line starting with '# kopt' and edit to your needs. Here is mine: $ grep ^#\ kopt /boot/grub/menu.lst # kopt=root=LABEL=sid ro vga=791 Don't forget to run 'update-grub' as root afterwards. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 01 Jul 2008, Hugo Vanwoerkom wrote: > Anthony Campbell wrote: >> On 30 Jun 2008, Andrei Popescu wrote: >>> On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote: >>> > Uh-oh, speaking of initrds: I forgot that in my previous message; you > should probably rebuild it if you change your fstab to labels or UUIDs. How do you do that? I changed to UUID and I got the same message with 2.6.25 although 2.6.23 still boots normally. I don't know how you would rebuilt initrds. >>> dpkg-reconfigure linux-image-... >>> >>> Regards, >>> Andrei >>> -- >>> If you can't explain it simply, you don't understand it well enough. >>> (Albert Einstein) >> >> >> Well, I finally found the answer but it's very odd. I don't think it >> should work but it does. I put the "wrong" root entry in >> /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this >> kernel seems to need /dev/hdb10. Here is the relevant section of the >> file: >> > > > > and did you use a vga= parm? And did that work? > > Hugo > No, I didn't do that at any time. I simply changed /dev/hdb9 to /dev/hdb10. I can't understand why the two kernels should require different values, but there it is. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
Anthony Campbell wrote: On 30 Jun 2008, Andrei Popescu wrote: On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote: Uh-oh, speaking of initrds: I forgot that in my previous message; you should probably rebuild it if you change your fstab to labels or UUIDs. How do you do that? I changed to UUID and I got the same message with 2.6.25 although 2.6.23 still boots normally. I don't know how you would rebuilt initrds. dpkg-reconfigure linux-image-... Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) Well, I finally found the answer but it's very odd. I don't think it should work but it does. I put the "wrong" root entry in /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this kernel seems to need /dev/hdb10. Here is the relevant section of the file: and did you use a vga= parm? And did that work? Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Linux-image-2.6.25 won't boot - target filesystem error -SOLVED
On 30 Jun 2008, Andrei Popescu wrote: > On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote: > > > > Uh-oh, speaking of initrds: I forgot that in my previous message; you > > > should probably rebuild it if you change your fstab to labels or UUIDs. > > > > How do you do that? I changed to UUID and I got the same message with > > 2.6.25 although 2.6.23 still boots normally. I don't know how you would > > rebuilt initrds. > > dpkg-reconfigure linux-image-... > > Regards, > Andrei > -- > If you can't explain it simply, you don't understand it well enough. > (Albert Einstein) Well, I finally found the answer but it's very odd. I don't think it should work but it does. I put the "wrong" root entry in /boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this kernel seems to need /dev/hdb10. Here is the relevant section of the file: title Debian GNU/Linux, kernel 2.6.25-2-amd64 root(hd1,9) kernel /boot/vmlinuz-2.6.25-2-amd64 root=/dev/hdb10 ro initrd /boot/initrd.img-2.6.25-2-amd64 title Debian GNU/Linux, kernel 2.6.25-2-amd64 (recovery mode) root(hd1,9) kernel /boot/vmlinuz-2.6.25-2-amd64 root=/dev/hdb10 ro single initrd /boot/initrd.img-2.6.25-2-amd64 title Debian GNU/Linux, kernel 2.6.23-1-amd64 root(hd1,9) kernel /boot/vmlinuz-2.6.23-1-amd64 root=/dev/hdb9 ro initrd /boot/initrd.img-2.6.23-1-amd64 title Debian GNU/Linux, kernel 2.6.23-1-amd64 (recovery mode) root(hd1,9) kernel /boot/vmlinuz-2.6.23-1-amd64 root=/dev/hdb9 ro single initrd /boot/initrd.img-2.6.23-1-amd64 I don't understand this at all. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
