why not just boot from your mandrake install CD, and at the prompt, type "rescue"
then when you are in and running, type, chroot /mnt and from that point on, you essentially have your own system running, with the exception that its using the kernel off the CDROM... fix your problems, and reboot without the cdrom,, works like a treat, and is one of the all time best things mandrake ever came up with. (I have even used it to rescue other distro's... rgds Frank -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of ngn Sent: Sunday, 20 January 2002 9:53 PM To: [EMAIL PROTECTED] Subject: Re: [newbie] Superblocks corrupted after a change in fstab .... I think that I had a messy trouble!!!!! I had a boot floppy of Mandrake 8.1, but it is from another install of Mandrake!!! I don't know if it'll work properly. However, if one of my tries to recover the system I remember that I gat a root prompt, but I cannot open mc to edit any of those files!!!! Although I think I opened vi to do that..!!! Well, I'll give a try to this boot disk from another install Bye!! ----- Original Message ----- From: "Derek Jennings" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 9:57 PM Subject: Re: [newbie] Superblocks corrupted after a change in fstab .... > Can you boot from your Boot floppy? > > If so you should be able to fix it. It looks as if you have edited the > lilo.conf and fstab files incorrectly > > Your lilo.conf file should look something like this :- > > default=linux-2.4.8-34 > boot=/dev/hda > map=/boot/map > install=/boot/boot.b > vga=normal > keytable=/boot/uk.klt > lba32 > prompt > timeout=50 > message=/boot/message > menu-scheme=wb:bw:wb:bw > image=/boot/vmlinuz-2.4.8-34.1mdk > label=linux-2.4.8-34 > root=/dev/hda5 > read-only > optional > vga=normal > append=" hdc=ide-scsi hdd=ide-scsi devfs=nomount quiet" > initrd=/boot/initrd-2.4.8-34.1mdk.img > > ***SNIP more stanzas follow > > Here I have defined IDE devices hdd and hdd as SCSI emulation. > I am running with devfs disabled, but you may not need to do that. > (In my system the CD writer would not work with devfs enabled) > I am using the updated kernel so my Lilo points to the 2.4.8-34 image. > > After modifying /etc/lilo.conf be sure to run /sbin/lilo as root and be sure > there are no error messages or else you will not be able to boot. (This could > well be your problem) > > Now my /etc/fstab file looks like this :- > > /dev/scd0 /mnt/cdrom auto > iocharset=iso8859-1,user,exec,noauto,codepage=850,nodev 0 0 > /dev/scd1 /mnt/cdrom2 auto > iocharset=iso8859-1,user,exec,noauto,codepage=850,nodev 0 0 > > (these two statements occupy one line each. there is a space before and after > 'auto') > device hdc is now referred to as /dev/scd0 and hdd has become /dev/scd1 > Note you do not need any 'dev=xxxx' in the fstab file. > > If you can get in to make these corrections you should be OK > > derek > > > > On Sunday 20 January 2002 00:14, ngn wrote: > > Hi folks...I have the following trouble: I have a cd-copier & a cd-reader, > > Due to I want to perform direct cd copying I made some changes in fstab and > > lilo.conf. > > > > For example: when in fstab appeared /dev/cdrom1 I put instead > > dev=/dev/scd1 (This was to made SCSI simulation on the cd-reader) > > I get both the cd-r & the cd-wr recognized by the front-ends of burning > > although I cannot make any "on-the-fly" copies [This is another > > problem!!!]... > > > > > The problem starts to arose when I tried to install some packages from the > > download cd's... When Software Manager asks for the cd1, I put it on the > > reader, and it ejects me the cd like it was a wrong one!!! > > > > Well, here is when the problem arises!!!!!!...Due to my big ignorance I > > open the file fstab and when it says dev=/dev/scd1 [IT IS MY CD-R] I put > > something like this "dev=/dev/scd1,/dev/cdrom" > > > > After that I rebooted and neither I can run the label failsafe nor the > > "normal" linux entrie on lilo. Moreover I cannot bot in "linux > > 2-2.secure". > > > > When I tried to boot in any of those entries it stops in the "Checking root > > filesystem" step with a msg like this : > > " The Superblocks on the device are corrupted, try to run an fsck" and it > > says more things that I do not remember now. > > However, one thing sounds strange for me.....It's says that I had to run > > fsck when my root partition is on a journallised file system [EXT3] > > > > Well, I know that this post might be very large, but... Unless I have a > > solution, I'll have to re-install Linux-Mandrake 8.1 > > > > Thanks in Advance > > > > Nicolas Gomez > > Montevideo, URUGUAY > > ---------------------------------------------------------------------------- ---- > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
