egag

Slack cd1 will not boot I keep getting that same message "use drive A:" rescue floppy (It was the floppy I made when I first installed slackware).

After using the rescue floppy I get a prompt saying "Boot:" so I typed "mount root=/dev/hda2 ro" to get to a login screen,
( I had to use read only (ro) because "reiserfsck --check" will not work if the partition is writable)

but during the boot up process a message scrolled past saying "remounting root with read write enabled (rw)". I tried "dmesg" to see what it was exactly but that part of the boot up screen didn't show.

Any ideas on how I can get round this read only/ write enabled problem.

Thanks
string

well.....can't your pc boot from a cd ? ( have you looked in the bios if you can change the boot-sequence ? )

if not possible, then you can make floppy's for booting-up. you need 3 of them.
on the cd look for "bare.i.img " in /bootdisks and "root1.img" and " root2.img " in /rootdisks

for each of the images do : put in a floppy ,
dd if=bare-i.img of=/dev/fd0 ( this will write the boot-floppy )
( do the same for the two root-disks )
when you boot from the boot-floppy, it will ask for the other two.
after that you can run " reiserfsck "

egag

egag

Firstly thanks for your help with this its really appreciated.
I've looked through slacks /bootdisk file, there's no "bare.i.img" but only "bare.i" is this what I need to copy?
also in /roodisks file there's no "root1.img" or "root2.img" but only "install1" and "install2" which are both Gzip files, do I copy them?
I have to check this because me+ guessing+ computers = bad idea!!

thanks
string

well.. i think you should read the " README.TXT " in the rootdisks-dir. there's an explanation on howto do things.
there's no use in posting readme-files wich are on your disk.
( btw.. you will need " bare.i " , it's 1.4 Mb )

good luck

egag

Ok this is the reiserfsck --check

replaying journal......

0 transactions replayed
checking internal tree........finished
comparing bitmaps........finished
checking semantic tree:
finished
no corruptions found

there are on the filesystem:
leaves 43400
internal nodes 294
directories 13694
other files 179907
data block pointers 586075 (74 of them zero)
safe links 0

Thanks
string

well... if your fs. is oke, i don't really uderstand the error-message " fat error "
wich indicates a wrong pointer in the file-alloccation-table.
i would reinstall lilo ( just type "lilo" at the prompt ) and try to boot from the hd.
do you still get the same error ?

edit: also check if the file " /sbin/init " exists on your system.

egag

egag

I typed "lilo" at prompt it said "added linux*" but I still get the same error.

There is a file called "/sbin/init"

I'm not too sure what you meant by "fat error" but part of the boot up message says-

FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
reiserfs: found format "3.6" with standard journal

Thanks
string

Well, the same message comes up on my system but it mounts my fat partition ok, so I really don't know what causes it.

well... i think " fat error " means an error in the file allocation table( fat), it has
nothing to do with the vfat-filesystem.

furthermore, i really don"t know an answer ........? ( anyone )

egag

Thanks for your time egag.

Can anyone else help me out.


Thanks

string

well... i found this :
http://www.linuxforums.org/forum/ntopic24118.html.

it suggests a kernel-recompile without umsdos and scsi_modules.

might be worth a try....

egag