Re: read only /dev/hda1 /mnt/gentoo/boot

Hey there Maynard,

Thank you for your thoughtful concern.

I thought it might be the boot sector also, I tried switching the drives
around to make the other one the master, and things sort went downhill from
there. I mentioned this in an earlier post today but haven't seen it posted
yet. When switching the drives (at this point they were both devoid of any
partitions by using Microsoft fdisk from a Win98 floppy and cfdisk from the
image cd) I was foolish enough to attempt changing them in bios because I
got the "Primary master boot fail" and "Primary slave boot fail" messages at
startup. That was really a bad move. It would have been fine I believe if I
would have done it with partitions remaining on the drives I think, however
at this point I am left with 2 drives that cannot be seen by the bios on
this particular machine. I may be able to recover them with a machine that
has a newer bios and a low level ide format program, or maybe a debug
program.

I am going to see if my nephew will bring his box over, he has a rather
recent bios on it. Then I will go from there. If it's still no go for these
particular drives (ulp!) then I will have to get some others to replace
them, I have a couple of more machines that I can scrounge off of, or I may
just opt to buy a scsi for this particular machine this time.

I wasn't planning on a dual boot system for this machine, hence the reason
why I wiped them both completely clean. I intend to run an apache server on
the rascal after it's up and running.

Michael S. Sprague
[email protected]
Registered LINUX User: 290220

----- Original Message -----
From: "Michael S Sprague" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, October 16, 2002 2:38 PM
Subject: [gentoo-newbies] read only /dev/hda1 /mnt/gentoo/boot


> I believe I followed the directions well enough during the partition setup
> process. The examples mention et2/3 as appropriate types for the boot
> partition. I made it ext3 using mk2fs -j -L Boot /dev/hda1. I did this
from
> the command line after I had first partitioned the /dev/hda1 using cfdisk
> which came with the install cd.
>
> Using "dmesg" I see a message that:
> Directory 1 : bad FAT
> Filesystem panic (dev 03:01).
> FAT error
> File system has been set read-only

Looks like a bad cluster error. Are you setting up for dual boot?

> How can I determine if this is /dev/hda1? If so, perhaps the fist block is
> damaged on that drive.

If there are 2 drives, unplug the secondary and physically confirm /hda is
set as master - unless - your system uses cable select like some Compaqs do.
Otherwise try using the Linux fdisk instead of cfdisk; seems to be a bit
more effective for some reasons.

> This may be the reason it is set to read only filesystem?

A bad sector or a SMART failure warning (internal drive monitoring) could
cause this. You need to do a low level format which fdisk does. I don't know
if cfdisk does or even if it's capable of it.
>
> Michael S. Sprague
----- Original Message -----


From: "Michael S Sprague" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, October 16, 2002 2:38 PM
Subject: [gentoo-newbies] read only /dev/hda1 /mnt/gentoo/boot


> I believe I followed the directions well enough during the partition setup
> process. The examples mention et2/3 as appropriate types for the boot
> partition. I made it ext3 using mk2fs -j -L Boot /dev/hda1. I did this
from
> the command line after I had first partitioned the /dev/hda1 using cfdisk
> which came with the install cd.
>
> Using "dmesg" I see a message that:
> Directory 1 : bad FAT
> Filesystem panic (dev 03:01).
> FAT error
> File system has been set read-only

Looks like a bad cluster error. Are you setting up for dual boot?

> How can I determine if this is /dev/hda1? If so, perhaps the fist block is
> damaged on that drive.

If there are 2 drives, unplug the secondary and physically confirm /hda is
set as master - unless - your system uses cable select like some Compaqs do.
Otherwise try using the Linux fdisk instead of cfdisk; seems to be a bit
more effective for some reasons.

> This may be the reason it is set to read only filesystem?

A bad sector or a SMART failure warning (internal drive monitoring) could
cause this. You need to do a low level format which fdisk does. I don't know
if cfdisk does or even if it's capable of it.
>
> Michael S. Sprague