On Tue, 9 Jun 1998, Rick L. Mantooth wrote:
>
> Possible the scsi cable is "cocked" or not seated
> securely at either end?
>
> or
>
> Bring your machine up into "Single User" mode and run
>
> # fdisk -l
>
> this will show you your partitions on all drives.
>
> Should show you something like:
>
> Device Boot Begin Start End Blocks Id System
> /dev/hdd1 * 1 1 153 77080+ 83 Linux native
> /dev/hdd2 154 154 1169 512064 83 Linux native
> /dev/hdd3 1024 1170 1271 51408 82 Linux swap
> /dev/hdd4 1024 1272 3893 1321488 5 Extended
> /dev/hdd5 1024 1273 2796 768096 83 Linux native
> /dev/hdd6 2048 2798 2899 51408 83 Linux native
> /dev/hdd7 2048 2901 3002 51408 83 Linux native
> /dev/hdd8 2048 3004 3816 409752 83 Linux native
>
> Then cat /etc/fstab to make sure it hasn't been overwritten somehow
> by a binary or garbage...
>
> Good Luck,
> Rick
Thanks for the response. fstab looks normal, but fdisk -l shows that my
partition table is apparently messed up. Hereis the output:
>fdisk -l
The number of cylinders for this disk is set to 2063.
This is larger than 1024, and may cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and partitioning software form (sic) other OS's
(e.g., DOS FDISK, OS/2 FDISK)
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag ffff of partition table 5 will be corrected by
w(rite).
Disk /dev/sda: 64 heads, 32 sectors, 2063 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Begin Start End Blocks Id System
/dev/sda1 1 1 200 204784 6 DOS 16-bit >=32M
/dev/sda2 * 201 201 232 32768 83 Linux native
/dev/sda3 233 233 2063 1874944 5 Extended
/dev/sda5 ? 1028 232 2322147483647+ ff BBT
---------------------------------------
and of course there should be /sda6 /sda7 /sda8.
I neglected to say what I was doing when this happened - I was starting
amd, but this was only to mount remote filesystems. I turned this off and
rebooted in case it was the cause, but the table was already corrupted.
So, this situation begs two questions. First, what could have caused
this? Is there any chance that this is the result of a malicious security
compromise (I've been checking the logs though and there haven't been any
obvious compromises). Also, does this mean there has been a disk failure,
or can I just recreate the partition table and everything will be happy
once again? How would I go about fixing the partition table (i.e. where
is it located)?
Graham
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
