Re: Linux-image-2.6.25 won't boot - target filesystem error
Hello Jochen, Am 2008-07-09 01:36:10, schrieb Jochen Antesberger: > The device naming was changed. Instead of /dev/hda you've got /dev/sda > now. To make it boot you'll have to adjust menu.lst to give the kernel the > right argument for the boot partition. Also you'll have to change the > entries in fstab. Argh! -- I have forgotten about this. Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error
Am Fri, 04 Jul 2008 01:00:46 +0200 schrieb Michelle Konzack: > Hello Anthony, > > Am 2008-06-30 10:14:02, schrieb Anthony Campbell: >> I just installed linux-image-2.6.25-2 from Sid. Boot fails with a >> mwwage: >> >> "target filesystem doesn't have bootarg" >> >> This is followed by: >> "/bin/sh: can't access tty; job control turned off" > > I am using Etch with 2.6.18 and it works fine, if I try to install a > 2.6.22/24/25 and boot, I get a Kernel Oops since it can not find the > /etc/fstab and /dev/console. > > But the initrd.img is correctly build with the 2.6.18. > > Any suggestions? The device naming was changed. Instead of /dev/hda you've got /dev/sda now. To make it boot you'll have to adjust menu.lst to give the kernel the right argument for the boot partition. Also you'll have to change the entries in fstab. -- 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
Hello Anthony, Am 2008-06-30 10:14:02, schrieb Anthony Campbell: > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > mwwage: > > "target filesystem doesn't have bootarg" > > This is followed by: > "/bin/sh: can't access tty; job control turned off" I am using Etch with 2.6.18 and it works fine, if I try to install a 2.6.22/24/25 and boot, I get a Kernel Oops since it can not find the /etc/fstab and /dev/console. But the initrd.img is correctly build with the 2.6.18. Any suggestions? Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 +49/177/935194750, rue de Soultz MSN LinuxMichi +33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
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]
Re: Linux-image-2.6.25 won't boot - target filesystem error
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) signature.asc Description: Digital signature
Re: Linux-image-2.6.25 won't boot - target filesystem error
On Mon, Jun 30, 2008 at 15:28:10 +0100, Anthony Campbell wrote: > On 30 Jun 2008, Florian Kulzer wrote: > > On Mon, Jun 30, 2008 at 13:45:44 +0100, Anthony Campbell wrote: > > > On 30 Jun 2008, Andrei Popescu wrote: > > > > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > > > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > > > > mwwage: > > > > > > > > > > "target filesystem doesn't have bootarg" > > > > > > > > > > This is followed by: > > > > > "/bin/sh: can't access tty; job control turned off" > > > > > > > > > > 2.6.23 still boots normally. > > > > > > > > > > Google shows a number of people with similar problems, mainly on > > > > > Ubuntu. > > > > > I also found a Debian recommendation to modify /etc/fstab in order to > > > > > get the file systems recognized, but I'm reluctant to do so for fear > > > > > of > > > > > losing the ability to boot any kernel at all. > > > > > > > > > > Any ideas about this one? > > > > > > > > How large is your initrd? Assuming that you run lilo, you may be > > > > experiencing > > > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607 > > > > > > No, I'm using grub. > > > > 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. The easiest way to rebuild an initrd for a given kernel is to run dpkg-reconfigure on the corresponding linux-image-... package. This should call an initrd generator as well as update-grub. You can do this for the 2.6.25 kernel only, to make sure that you are not breaking the working 2.6.23. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- 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
On 30 Jun 2008, Florian Kulzer wrote: > On Mon, Jun 30, 2008 at 13:45:44 +0100, Anthony Campbell wrote: > > On 30 Jun 2008, Andrei Popescu wrote: > > > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > > > mwwage: > > > > > > > > "target filesystem doesn't have bootarg" > > > > > > > > This is followed by: > > > > "/bin/sh: can't access tty; job control turned off" > > > > > > > > 2.6.23 still boots normally. > > > > > > > > Google shows a number of people with similar problems, mainly on Ubuntu. > > > > I also found a Debian recommendation to modify /etc/fstab in order to > > > > get the file systems recognized, but I'm reluctant to do so for fear of > > > > losing the ability to boot any kernel at all. > > > > > > > > Any ideas about this one? > > > > > > How large is your initrd? Assuming that you run lilo, you may be > > > experiencing > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607 > > > > No, I'm using grub. > > 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. 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
On Mon, Jun 30, 2008 at 13:45:44 +0100, Anthony Campbell wrote: > On 30 Jun 2008, Andrei Popescu wrote: > > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > > mwwage: > > > > > > "target filesystem doesn't have bootarg" > > > > > > This is followed by: > > > "/bin/sh: can't access tty; job control turned off" > > > > > > 2.6.23 still boots normally. > > > > > > Google shows a number of people with similar problems, mainly on Ubuntu. > > > I also found a Debian recommendation to modify /etc/fstab in order to > > > get the file systems recognized, but I'm reluctant to do so for fear of > > > losing the ability to boot any kernel at all. > > > > > > Any ideas about this one? > > > > How large is your initrd? Assuming that you run lilo, you may be > > experiencing > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607 > > No, I'm using grub. 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. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- 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
On 30 Jun 2008, Andrei Popescu wrote: > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > mwwage: > > > > "target filesystem doesn't have bootarg" > > > > This is followed by: > > "/bin/sh: can't access tty; job control turned off" > > > > 2.6.23 still boots normally. > > > > Google shows a number of people with similar problems, mainly on Ubuntu. > > I also found a Debian recommendation to modify /etc/fstab in order to > > get the file systems recognized, but I'm reluctant to do so for fear of > > losing the ability to boot any kernel at all. > > > > Any ideas about this one? > > How large is your initrd? Assuming that you run lilo, you may be > experiencing > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607 > No, I'm using grub. -- 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
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > mwwage: > > "target filesystem doesn't have bootarg" > > This is followed by: > "/bin/sh: can't access tty; job control turned off" > > 2.6.23 still boots normally. > > Google shows a number of people with similar problems, mainly on Ubuntu. > I also found a Debian recommendation to modify /etc/fstab in order to > get the file systems recognized, but I'm reluctant to do so for fear of > losing the ability to boot any kernel at all. > > Any ideas about this one? How large is your initrd? Assuming that you run lilo, you may be experiencing http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479607 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
On Mon, Jun 30, 2008 at 10:50:03 +0100, Anthony Campbell wrote: > On 30 Jun 2008, Daniel Dalton wrote: > > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > > > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > > mwwage: > > > > > > "target filesystem doesn't have bootarg" > > > > > > This is followed by: > > > "/bin/sh: can't access tty; job control turned off" [...] > The kernel is correct; I'm currently using linux-image-2.6.23-amd64. > > I take the point about using a rescue disk but I'm not sure of what to > try for /etc/fstab. I know that a fresh installation of linux uses > different syntax but I don't remember what it is or how it works. > Currently I have: > > /dev/hdb10 / ext3errors=remount-ro 0 > 1 > /dev/hda5 noneswapsw 0 0 > proc/proc procdefaults0 0 > # none /proc/bus/usb/ usbdevfs user,noauto 0 0 > none /proc/bus/usb usbfs defaults 0 0 > /dev/fd0/media/floppy autouser,noauto,rw 0 0 > /dev/hdc/media/cdromiso9660 ro,user,noauto,unhide 0 0 > /dev/hdb6 noneswapsw 0 0 > /dev/hdb7 /usr/local ext3defaults0 2 > /dev/hdb8 /home ext3defaults0 2 > /dev/hda1/backupext3 user,defaults0 2 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=". You can try this with only your "backup" partition first to see if it works, i.e. if the 2.6.23 kernel mounts it correctly if the fstab entry refers to the label or UUID instead of /dev/hda1. The corresponding syntax for /boot/grub/menu.lst is # kopt=root=LABEL=root ro (plus other boot options that you might want to pass to the kernel) I would first try to switch to labels or UUIDs completely (including root) with 2.6.23. If you subsequently run into a problem with 2.6.25 then you may have to boot into 2.6.23 once more and change every reference in /boot/grub/device.map from /dev/hdX to /dev/sdX. (I have no idea how this works with LILO.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- 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
On 30 Jun 2008, Daniel Dalton wrote: > On Mon, Jun 30, 2008 at 10:50:03AM +0100, Anthony Campbell wrote: > > > On 30 Jun 2008, Daniel Dalton wrote: > > No error messages. I do get: > > aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ... > > Running depmod. > > Finding valid ramdisk creators. > > should be fine > > > The kernel is correct; I'm currently using linux-image-2.6.23-amd64. > > indeed > > > > > I take the point about using a rescue disk but I'm not sure of what to > > try for /etc/fstab. I know that a fresh installation of linux uses > > Erm, didn't you say you found this on google earlier? Isn't that how we > got started talking about rescue cds? Or have I mistaken... You know you > can also backup your fstab before you touch it so it is just a matter of > doing this when in the rescue cd: > cp /path/to/backup/fstab /etc > (that will restore your backup) > > > different syntax but I don't remember what it is or how it works. > > Currently I have: > > Don't ask me about fstab, I haven't read up on this much, perhaps others > can help with this. > Yes, I do know about rescue CDs, backing up /etc/fstab etc. But I didn't really want to go down that route unless it's necessary and I really don't know where to begin sorting this one out. None of the Goggle stuff is very helpful. I'm not at all sure that messing about with /etc/fstab would help. I don't seem to be alone with this one. There was a recent (June 21) post with almost identical errors: Begin: Running /scripts/init-bottom ... mount: No such file or directory mount: No such file or directory Target file system doesn't have /sbin/init No init found. Try passing init= bootarg. BusyBox v1.10.2 (Debian 1:1.10.2-1) built-in shell (ash) Enter 'help' for alist of built-in commands /bin/sh: can't access tty; job control off (initramfs) I have no idea where to start debugging from. I think that the problem is more about the kernel, not about the mdadm. I suppose I somehow did not comiped in the kernel something needed for finding the sATA devices, but I used the default kernel configuration and I was thinking that this should work. Morover, I cannot boot the LinuxOLD image (which was working perfectly before), since it ends in a kernel panic message. Any idea on how to boot this machine and bring back in a working condition is welcome. This is: http://www.mail-archive.com/debian-user@lists.debian.org/msg519211.html Time for a bug report, I think. 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
On Mon, Jun 30, 2008 at 10:50:03AM +0100, Anthony Campbell wrote: > On 30 Jun 2008, Daniel Dalton wrote: > No error messages. I do get: > aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ... > Running depmod. > Finding valid ramdisk creators. should be fine > The kernel is correct; I'm currently using linux-image-2.6.23-amd64. indeed > > I take the point about using a rescue disk but I'm not sure of what to > try for /etc/fstab. I know that a fresh installation of linux uses Erm, didn't you say you found this on google earlier? Isn't that how we got started talking about rescue cds? Or have I mistaken... You know you can also backup your fstab before you touch it so it is just a matter of doing this when in the rescue cd: cp /path/to/backup/fstab /etc (that will restore your backup) > different syntax but I don't remember what it is or how it works. > Currently I have: Don't ask me about fstab, I haven't read up on this much, perhaps others can help with this. -- Daniel Dalton http://members.iinet.net.au/~ddalton/ <[EMAIL PROTECTED]> -- 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
On 30 Jun 2008, Daniel Dalton wrote: > On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > > > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > > mwwage: > > > > "target filesystem doesn't have bootarg" > > > > This is followed by: > > "/bin/sh: can't access tty; job control turned off" > > > > Mine works here, but was there any errors with dpkg when installing? > Also, did you get the right one for your computer? Eg. x86 for x86 > machines. > > > I also found a Debian recommendation to modify /etc/fstab in order to > > get the file systems recognized, but I'm reluctant to do so for fear of > > losing the ability to boot any kernel at all. > > err... just get a rescue cd, if it won't boot, put it in the cd drive, > boot it mount your linux partition open > /mntp/to/linux/partition/etc/fstab > And remove those lines, reboot back into your linux 2.6.23 kernel... > No error messages. I do get: aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird The kernel is correct; I'm currently using linux-image-2.6.23-amd64. I take the point about using a rescue disk but I'm not sure of what to try for /etc/fstab. I know that a fresh installation of linux uses different syntax but I don't remember what it is or how it works. Currently I have: /dev/hdb10 / ext3errors=remount-ro 0 1 /dev/hda5 noneswapsw 0 0 proc/proc procdefaults0 0 # none /proc/bus/usb/ usbdevfs user,noauto 0 0 none /proc/bus/usb usbfs defaults 0 0 /dev/fd0/media/floppy autouser,noauto,rw 0 0 /dev/hdc/media/cdromiso9660 ro,user,noauto,unhide 0 0 /dev/hdb6 noneswapsw 0 0 /dev/hdb7 /usr/local ext3defaults0 2 /dev/hdb8 /home ext3defaults0 2 /dev/hda1/backupext3 user,defaults0 2 ~ ~ 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
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote: > I just installed linux-image-2.6.25-2 from Sid. Boot fails with a > mwwage: > > "target filesystem doesn't have bootarg" > > This is followed by: > "/bin/sh: can't access tty; job control turned off" > Mine works here, but was there any errors with dpkg when installing? Also, did you get the right one for your computer? Eg. x86 for x86 machines. > I also found a Debian recommendation to modify /etc/fstab in order to > get the file systems recognized, but I'm reluctant to do so for fear of > losing the ability to boot any kernel at all. err... just get a rescue cd, if it won't boot, put it in the cd drive, boot it mount your linux partition open /mntp/to/linux/partition/etc/fstab And remove those lines, reboot back into your linux 2.6.23 kernel... -- Daniel Dalton http://members.iinet.net.au/~ddalton/ <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Linux-image-2.6.25 won't boot - target filesystem error
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a mwwage: "target filesystem doesn't have bootarg" This is followed by: "/bin/sh: can't access tty; job control turned off" 2.6.23 still boots normally. Google shows a number of people with similar problems, mainly on Ubuntu. I also found a Debian recommendation to modify /etc/fstab in order to get the file systems recognized, but I'm reluctant to do so for fear of losing the ability to boot any kernel at all. Any ideas about this one? -- 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: ocfs2 (oracle cluster filesystem) error: Unable to load module "configfs"
Benedict Verheyen schreef: I didn't use ocfs2 nor hostf to do what i wanted. I moved the homedirectories to the uml and it works for me. Regards, Benedict -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ocfs2 (oracle cluster filesystem) error: Unable to load module "configfs"
Benedict Verheyen schreef: Hi, i want to run ocfs2 to load a shared filesystem for 3 uml's. ocfs2 allows 2 or more uml's to load the same filesystem so it should solve the limitations of hostfs. Anyway, i compiled ocfs2 support into the kernel and made a /etc/ocfs2/cluster.conf file. However, when i want to start the clustering service, it fails: /etc/init.d/o2cb load Loading module "configfs": Unable to load module "configfs" Uhm: grep "CONFIGFS" /boot/config-2.6.20.7.15aug2007 CONFIG_CONFIGFS_FS=y As it seems now, in order to get i working i shouldn't compile support into the kernel? Is there a workaround? Regards, Benedict Apparantly, it's a bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416662 When i do what's mentioned in the bug report, i can get the service to start. When i create a filesystem (mkfs.ocfs2 -b 4K -C 128K -N 4 home_fs), i get an error: ocfs2_hb_ctl: The block size is smaller than the sector size on this device while reading uuid mount.ocfs2: Error when attempting to run /sbin/ocfs2_hb_ctl: "Operation not permitted" Anyway, i'm getting closer :) Regards, Benedict -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ocfs2 (oracle cluster filesystem) error: Unable to load module "configfs"
Hi, i want to run ocfs2 to load a shared filesystem for 3 uml's. ocfs2 allows 2 or more uml's to load the same filesystem so it should solve the limitations of hostfs. Anyway, i compiled ocfs2 support into the kernel and made a /etc/ocfs2/cluster.conf file. However, when i want to start the clustering service, it fails: /etc/init.d/o2cb load Loading module "configfs": Unable to load module "configfs" Uhm: grep "CONFIGFS" /boot/config-2.6.20.7.15aug2007 CONFIG_CONFIGFS_FS=y As it seems now, in order to get i working i shouldn't compile support into the kernel? Is there a workaround? Regards, Benedict -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem error?
On Sat, Jan 25, 2003 at 05:45:46PM +, Paladin wrote: > > exotic tests that take a couple of hours to get to. I cut back > > the cpu/memory speed in the BIOS and mine now runs solidly, but > > In the mean while, I ran memtest86 over night and it doesn't show > any error report! I ran all the tests (more than one time I > suppose, since it was running for a long time). > I've changed my ext3 fs to reisersfs and still, when compiling on > it, gcc crashes! The only partition that remains in ext3 is the /. I > haven't had any idea of how to change it without loosing > everything... To change the BIOS settings that consider timing is imho a good idea. I've experienced a similar problem once, when I changed from a mixed setup with IDE and SCSI disks to SCSI disks only: After some time, the system just completely freezed, whereby 'some time' could be a few minutes up to several days of uptime. The freeze wasn't related to any particular operation. It was so annoying that I would have replaced the board, but it was at some time shortly before xmas, and boards were sold out. Thus, I again tried to change BIOS settings, and to my surprise, after changing some DRAM timing setting, the system ran stable (and it still does). That there's a relation to the FS being used in your case is possible in the sense that obscure timing factors may cause you the trouble. Maybe data is being delivered to gcc at another rate, depending on the FS being used, thereby electrical signals are running through your system in different patters. Thus, it may even be a problem with the cables that would never show up when running memory tests. The power supply being too weak or a loose contact is another possibility. Well, you may even try to choose the slowest memory settings your BIOS allows and still encounter the same problem. There *may* be a BIOS setting that helps, and the problem lies only in finding it --- but if the problem persists, I'd consider to change the board, and be it only to try if things improve on another board. HTH! GH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem error?
On Thu, 23 Jan 2003 10:26:40 -0800 Michael Epting <[EMAIL PROTECTED]> wrote: > I have one of these boards and have problems with memory errors. > Have > you tried running a memory test (before booting, such as the one > on the Linux BBC) overnight? Mine tends to fail on the more > exotic tests that take a couple of hours to get to. I cut back > the cpu/memory speed in the BIOS and mine now runs solidly, but > slower than spec. Life is full of tradeoffs -- this board was > very inexpensive and for me it's still fast enough. Sorry for the slow response, I've just been recovering from a rm -rf /usr/* sort of thing! ;P In the mean while, I ran memtest86 over night and it doesn't show any error report! I ran all the tests (more than one time I suppose, since it was running for a long time). I've changed my ext3 fs to reisersfs and still, when compiling on it, gcc crashes! The only partition that remains in ext3 is the /. I haven't had any idea of how to change it without loosing everything... --- Paladin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem error?
On Thu, Jan 23, 2003 at 05:00:49PM +, Paladin wrote: > From some time now I've been experiencing some problems with my sarge > debian box, ranging from gcc crashes (any of the three versions I have > installed), to corrupted files (in particular the /var/dpkg/status), > and I don't know how to discover where the problem is! I've even used > the memtest86 utility to see if it was a problem in the motherboard (I > have an ECS K7S5A and there are some reports of bugs in it). As anyone > experienced any kind of these problmes? I have one of these boards and have problems with memory errors. Have you tried running a memory test (before booting, such as the one on the Linux BBC) overnight? Mine tends to fail on the more exotic tests that take a couple of hours to get to. I cut back the cpu/memory speed in the BIOS and mine now runs solidly, but slower than spec. Life is full of tradeoffs -- this board was very inexpensive and for me it's still fast enough. -- Michael Epting ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Filesystem error?
Hi to all! >From some time now I've been experiencing some problems with my sarge debian box, ranging from gcc crashes (any of the three versions I have installed), to corrupted files (in particular the /var/dpkg/status), and I don't know how to discover where the problem is! I've even used the memtest86 utility to see if it was a problem in the motherboard (I have an ECS K7S5A and there are some reports of bugs in it). As anyone experienced any kind of these problmes? I have kernel 2.4.20 installed, compiled and installed "by hand". I'm using ext3 filesystems converted from ext2. Thanks in advance for any advice/idea/opinion, --- Paladin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ext3 filesystem error
On Tue, 24 Dec 2002 20:11:44 +0100 Elimar Riesebieter <[EMAIL PROTECTED]> wrote: > On Tue, 24 Dec 2002 the mental interface of > Jacob S. told: > > > On Tue, 24 Dec 2002 11:48:03 -0600 (CST) > > Russ Cook <[EMAIL PROTECTED]> wrote: > > > > > My hard drive is set up with /dev/hda1 /boot > > > and /dev/hda2 / > > > /dev/hda3 is my swap space. > > > > > > When I edit /etc/fstab to set /dev/hda2 and /dev/hda1 to ext3 > > > instead of ext2, I get the error: > > > kernel: ext3: No journal on filesystem on ide0(3,1) > > > My file /etc/mtab shows /dev/hda2 mounted as ext3, but /dev/hda1 > > > does not mount. I have no /boot directory. > > > If I change the /etc/fstab file to mount /dev/hda2 as ext3 and > > > /dev/hda1 as ext2, then both are mounted without errors. Can > > > anyone point out my problem? > > > > > > Thanks, > > > Russ > > > > Howdy Russ, > > > > I know this sounds obvious, but perhaps you haven't created a > > journal on hda1 yet? To quote the ext3 mini howto: > > > > "An ext2 filesystem may be converted to ext3 by creating a journal > > file on it. To do this, run > > > > tune2fs -j /dev/hdXX > > > > on the target filesystem. The filesystem is now ext3! > > If Russ does this on his /dev/hda3 his swap wil be gone ;-) > > Happy Xmas > > Elimar Very true, which is why I didn't say anything about his hda3. The problems and scenarios he gave were dealing with hda1 and 2. So, I suggested he try creating a journal on hda1, which is the one that was failing when trying to mount as an ext3 partition. Jacob - GnuPG Key: 1024D/16377135 In a world without fences, who needs Gates? http://www.linux.org/ msg20887/pgp0.pgp Description: PGP signature
Re: ext3 filesystem error
On Tue, 24 Dec 2002 the mental interface of Jacob S. told: > On Tue, 24 Dec 2002 11:48:03 -0600 (CST) > Russ Cook <[EMAIL PROTECTED]> wrote: > > > My hard drive is set up with /dev/hda1 /boot > > and /dev/hda2 / > > /dev/hda3 is my swap space. > > > > When I edit /etc/fstab to set /dev/hda2 and /dev/hda1 to ext3 instead > > of ext2, I get the error: > > kernel: ext3: No journal on filesystem on ide0(3,1) > > My file /etc/mtab shows /dev/hda2 mounted as ext3, but /dev/hda1 > > does not mount. I have no /boot directory. > > If I change the /etc/fstab file to mount /dev/hda2 as ext3 and > > /dev/hda1 as ext2, then both are mounted without errors. Can anyone > > point out my problem? > > > > Thanks, > > Russ > > Howdy Russ, > > I know this sounds obvious, but perhaps you haven't created a journal on > hda1 yet? To quote the ext3 mini howto: > > "An ext2 filesystem may be converted to ext3 by creating a journal file > on it. To do this, run > > tune2fs -j /dev/hdXX > > on the target filesystem. The filesystem is now ext3! If Russ does this on his /dev/hda3 his swap wil be gone ;-) Happy Xmas Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-) msg20886/pgp0.pgp Description: PGP signature
Re: ext3 filesystem error
On Tue, 24 Dec 2002 11:48:03 -0600 (CST) Russ Cook <[EMAIL PROTECTED]> wrote: > My hard drive is set up with /dev/hda1 /boot > and /dev/hda2 / > /dev/hda3 is my swap space. > > When I edit /etc/fstab to set /dev/hda2 and /dev/hda1 to ext3 instead > of ext2, I get the error: > kernel: ext3: No journal on filesystem on ide0(3,1) > My file /etc/mtab shows /dev/hda2 mounted as ext3, but /dev/hda1 > does not mount. I have no /boot directory. > If I change the /etc/fstab file to mount /dev/hda2 as ext3 and > /dev/hda1 as ext2, then both are mounted without errors. Can anyone > point out my problem? > > Thanks, > Russ Howdy Russ, I know this sounds obvious, but perhaps you haven't created a journal on hda1 yet? To quote the ext3 mini howto: "An ext2 filesystem may be converted to ext3 by creating a journal file on it. To do this, run tune2fs -j /dev/hdXX on the target filesystem. The filesystem is now ext3! Note that the filesystem need not be unmounted for this operation." The full mini howto can be found at: http://www.symonds.net/~rajesh/howto/ext3/toc.html HTH, Jacob - GnuPG Key: 1024D/16377135 In a world without fences, who needs Gates? http://www.linux.org/ msg20885/pgp0.pgp Description: PGP signature
ext3 filesystem error
My hard drive is set up with /dev/hda1 /boot and /dev/hda2 / /dev/hda3 is my swap space. When I edit /etc/fstab to set /dev/hda2 and /dev/hda1 to ext3 instead of ext2, I get the error: kernel: ext3: No journal on filesystem on ide0(3,1) My file /etc/mtab shows /dev/hda2 mounted as ext3, but /dev/hda1 does not mount. I have no /boot directory. If I change the /etc/fstab file to mount /dev/hda2 as ext3 and /dev/hda1 as ext2, then both are mounted without errors. Can anyone point out my problem? Thanks, Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: filesystem error???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 24 September 2002 08:54 pm, axacheng wrote: > .i have 2 partition and 1 swap in my disk > love:/# df -alhT > FilesystemTypeSize Used Avail Use% Mounted on > /dev/hda3 xfs 36G 1.2G 35G 4% / > /dev/hda1 xfs 89M 8.5M 80M 10% /boot > > i tried xfs_repair to check/repair my /dev/hda1 that have a warning > appeared on! > > love:/# xfs_repair /dev/hda1 > xfs_repair: /dev/hda1 contains a mounted filesystem > fatal error -- couldn't initialize XFS library > love:/# xfs_repair /dev/hda1 > > those mean,i should be use boot my system from cdrom than use xfs_repair to > check/repair /dev/hda1 again??? I think you are probably on the right track. Did this happen when you tried to run this program while the harddrive was mounted? Either use the cdrom or use toms root boot disk. I don't use xfs, so this is just my speculation. best of luck to you. tatah - -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9kVi9ZHBxKsta6kMRAgdEAJ0WwIAE9fFlM5sgsrQj7Rg4F4tukQCfYb5X GoR+mzDaTx/RrMOXJDRg2IY= =Fq43 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: filesystem error???
On Wed, Sep 25, 2002 at 11:54:13AM +0800, axacheng wrote: > love:/# xfs_repair /dev/hda1 > xfs_repair: /dev/hda1 contains a mounted filesystem > fatal error -- couldn't initialize XFS library > love:/# xfs_repair /dev/hda1 > > those mean,i should be use boot my system from cdrom than use > xfs_repair to check/repair /dev/hda1 again??? Yup. Kinda makes you wish you had used something other than XFS for your root filesystem, huh? It was enough to make me ditch it on a few systems. noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html msg03440/pgp0.pgp Description: PGP signature
Re: filesystem error???
.i have 2 partition and 1 swap in my disk love:/# df -alhT FilesystemTypeSize Used Avail Use% Mounted on /dev/hda3 xfs 36G 1.2G 35G 4% / /dev/hda1 xfs 89M 8.5M 80M 10% /boot i tried xfs_repair to check/repair my /dev/hda1 that have a warning appeared on! love:/# xfs_repair /dev/hda1 xfs_repair: /dev/hda1 contains a mounted filesystem fatal error -- couldn't initialize XFS library love:/# xfs_repair /dev/hda1 those mean,i should be use boot my system from cdrom than use xfs_repair to check/repair /dev/hda1 again??? love:/# xfs_repair /dev/hda > > Phase 1 - find and verify superblock... > > bad primary superblock - bad magic number !!! > > > > what's mean of "bad primary superblock - bad magic number !!!" > > are you sure you have a filesystem on /dev/hda? most people partition > their drives, so it would be /dev/hda1 or /dev/hda2 (etc..) > > nate > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Trust & Unique ... Axacheng's PGP Public Key http://www.navigation.idv.tw/pgpkey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: filesystem error???
From: "axacheng" <[EMAIL PROTECTED]> > Hello list : > when i using "xfs_repair" to repair my filesystem, i got a notic as following: > > love:/# xfs_repair /dev/hda > Phase 1 - find and verify superblock... > bad primary superblock - bad magic number !!! > > what's mean of "bad primary superblock - bad magic number !!!" Shouldn't you be trying xfs_repair /dev/hda1 or whatever your partition is? /dev/hda is the entire disk. Warning: I have not used XFS, or xfs_repair. -- Sanjeev Linux Brainbench MVP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: filesystem error???
axacheng said: > Hello list : > when i using "xfs_repair" to repair my filesystem, i got a notic as > following: > > love:/# xfs_repair /dev/hda > Phase 1 - find and verify superblock... > bad primary superblock - bad magic number !!! > > what's mean of "bad primary superblock - bad magic number !!!" are you sure you have a filesystem on /dev/hda? most people partition their drives, so it would be /dev/hda1 or /dev/hda2 (etc..) nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
filesystem error???
Hello list : when i using "xfs_repair" to repair my filesystem, i got a notic as following: love:/# xfs_repair /dev/hda Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! what's mean of "bad primary superblock - bad magic number !!!" -- Trust & Unique ... Axacheng's PGP Public Key http://www.navigation.idv.tw/pgpkey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem error
Hi Stefan. On Mon, 23 Sep 2002 15:21:59 -0500 Michael Heironimus <[EMAIL PROTECTED]> wrote: > On Mon, Sep 23, 2002 at 01:16:20PM -0500, Stefan Sten wrote: > > I followed the instructions at the promt tried with 'mount -n -o > > remount,rw /' and then 'e2fsck dev/hda1'. > > If at all possible you should boot from an emergency disk/CD. In any > case, it is dangerous to run fsck on a filesystem that is mounted > read-write. If you can boot from floppy/CD don't mount the filesystem at > all, and run fsck -c /dev/hda1 for check badblocks > and if you have to boot from HD don't remount it rw. > > That gave me: "FILE SYSTEM MODIFIED", I rebooted and the system keeps > > complaning as before. Does somebody recognise this? > > Don't stop after you run fsck once. Keep running it until it doesn't > tell you about any more errors. If you have too many errors you may want > to just save what data you can to another partition, wipe that one, and > restore from a backup. You should also make yourself a note about this, > filesystem corruption can sometimes be caused by a hardware problem. > > -- > Michael Heironimus > Regards, -- Marcio Roberto Teixeira endereço eletrônico: [EMAIL PROTECTED] página pessoal: http://www.marciotex.hpg.ig.com.br chave pública: http://www.marciotex.hpg.ig.com.br/marciotex.gpg Usuário "tchê" Debian/GNULinux Porto Alegre - RS - Brasil "A vida é como uma boa prova escolar: é curta, com múltiplas escolhas." O "world" não é o Word. Uso LaTeX: viva o código aberto! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Filesystem error
On Mon, Sep 23, 2002 at 01:16:20PM -0500, Stefan Sten wrote: > I followed the instructions at the promt tried with 'mount -n -o > remount,rw /' and then 'e2fsck dev/hda1'. If at all possible you should boot from an emergency disk/CD. In any case, it is dangerous to run fsck on a filesystem that is mounted read-write. If you can boot from floppy/CD don't mount the filesystem at all, and if you have to boot from HD don't remount it rw. > That gave me: "FILE SYSTEM MODIFIED", I rebooted and the system keeps > complaning as before. Does somebody recognise this? Don't stop after you run fsck once. Keep running it until it doesn't tell you about any more errors. If you have too many errors you may want to just save what data you can to another partition, wipe that one, and restore from a backup. You should also make yourself a note about this, filesystem corruption can sometimes be caused by a hardware problem. -- Michael Heironimus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Filesystem error
Hi, I just got myself in trouble. In some strange way, when I fired up the machine I got: "/dev/hda1 contains a file system with errors, check forced. Entry '20020^@19190017.ksyms in var/log/ksymoops (159509) has illegal characters in its name. fsck failed" I followed the instructions at the promt tried with 'mount -n -o remount,rw /' and then 'e2fsck dev/hda1'. That gave me: "FILE SYSTEM MODIFIED", I rebooted and the system keeps complaning as before. Does somebody recognise this? Would appreciate any help, Edward -- __ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Filesystem error,Lost+Found and weird permissions
G'day all, I had a few problems with a hard drive.. lots of INODE corrections and I thought it was dying but its stop finding errors and seems OK, however there is a whole bunch of stuff in Lost+fond that I can't delete! I tried chmod ing and chown ing (as root) the but I get the message :Operation not permitted and if i do a ls -al there is a lengthy example at the end of this email what is going on??? Is there a way to delete these things ? is deleting them the best thing to do??? --Gareth c--srwS-wt 1 111 25716101, 118 Jun 11 23:23 #24609 br-sr-sr-T 1 2698325972 49, 116 Jun 11 23:23 #24611 b--srwS-wT 1 29486users112, 253 Jun 11 23:23 #24614 b-wsrwsrwx 1 2494326989115, 101 Oct 24 2021 #24616 br-xrw-rwx 1 2571424324119, 97 Oct 26 2030 #24617 br-sr--rw- 1 2596429288 98, 115 Jun 11 23:23 #24621 b--x-wsrwt 1 2775326990109, 117 Jun 11 23:23 #24633 b--xr-srw- 1 root 27002112, 50 Jun 11 23:23 #24641 b--sr-S--t 1 2646528527 10, 13 Oct 12 2021 #24649 br-xrwS-w- 1 2953729545 32, 114 Jun 11 23:23 #24650 b--xr-srwx 1 101 25970255, 0 Apr 15 2030 #24673 cr-sr-S-wx 1 1182621325 51, 46 Oct 5 2013 #24687 b--sr-sr-x 1 root 26414 46, 116 Jun 11 23:23 #24695 c--srwS-wt 1 nobody 25390 0, 110 Jun 11 23:23 #24737 br--wx 1 2570028257104, 99 Sep 24 2022 #24738 b--Sr-xrw- 1 2802026670104, 46 Jun 11 23:23 #24739 br-srwSr-- 1 108 28020109, 116 Mar 24 1970 #24744
Re: [HELP]: FILESYSTEM ERROR ! :(((((((((((( IT'S SOLVED ! :)))
On Sun, 18 Oct 1998, Nuno Carvalho wrote: > I'm having serials problems with my linux partition ! :(( It happened > when the power was down ! :(( > > That's what appears: > > - cut here -- > Parallelizing fsck version 1.12 (9-Jul-98) > /dev/hda2 contains a file system with errors, check failed > /dev/hda2: Unattached inode 70007 > > /dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY >(i.e., without -a or -p options) > > $mount > /dev/hda2 on / type ext2 (rw, errors=remount-ro) > proc on /proc type proc(rw) > cut here > > I already used the -a and -p options instead and always had that error > ! :(( I already corrected my filesystem partition! :)) To resolve it I just did: $ fsck /dev/hda2 instead of -a and -p options ! Thanks for all. Best regards, Nuno Carvalho
Re: [HELP]: FILESYSTEM ERROR ! :((((((((((((
Hello Nuno: It looks like the system wasn't shutdown properly. However your disk may have got itself a bad block. Try running /sbin/badblock and see what happens. Peter -Original Message- From: Nuno Carvalho <[EMAIL PROTECTED]> To: debian-user@lists.debian.org ; debian-devel@lists.debian.org Date: Sunday, October 18, 1998 5:18 AM Subject: [HELP]: FILESYSTEM ERROR ! : >Hi, > > I'm having serials problems with my linux partition ! :(( It happened >when the power was down ! :(( > > That's what appears: > >- cut here -- >Parallelizing fsck version 1.12 (9-Jul-98) >/dev/hda2 contains a file system with errors, check failed >/dev/hda2: Unattached inode 70007 > >/dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY > (i.e., without -a or -p options) > >$mount >/dev/hda2 on / type ext2 (rw, errors=remount-ro) >proc on /proc type proc(rw) > cut here > > I already used the -a and -p options instead and always had that error >! :(( > >What should I do ? >Can someone help me ? > >Thanks. > > Best regards, > Nuno Carvalho > > > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > BEGIN:VCARD VERSION:2.1 N:Iannarelli;Peter FN:Peter Iannarelli ORG:GenX Internet Laboratories TITLE:Engineer TEL;WORK;VOICE:1+ 416-929-1885 TEL;WORK;FAX:1+416-929-1056 ADR;WORK:;Madison;20 Madison Ave.;Toronto;Ontario;;Canada LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Madison=0D=0A20 Madison Ave.=0D=0AToronto, Ontario=0D=0ACanada URL: URL:http://www.genxl.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:19981018T093014Z END:VCARD
[HELP]: FILESYSTEM ERROR ! :((((((((((((
Hi, I'm having serials problems with my linux partition ! :(( It happened when the power was down ! :(( That's what appears: - cut here -- Parallelizing fsck version 1.12 (9-Jul-98) /dev/hda2 contains a file system with errors, check failed /dev/hda2: Unattached inode 70007 /dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (i.e., without -a or -p options) $mount /dev/hda2 on / type ext2 (rw, errors=remount-ro) proc on /proc type proc(rw) cut here I already used the -a and -p options instead and always had that error ! :(( What should I do ? Can someone help me ? Thanks. Best regards, Nuno Carvalho
