Hi,

I have a problem with recognizing the high end part of a 40g hard drive
where I have an installation of Redhat installed. For some reason I can
no longer access the root partition on this drive. I get a kernel panic
with no init found. I was able to do it some months back but did not try
again until last night. It is a backup of my normally used Redhat
installation which is on the second drive. I am hoping that something I
noticed when using Tom's boot disk will provide some clues to someone on
this list.

This is from dmesg when I boot from the working copy of Redhat, which is
on a 6.8g hard drive:

--- snip

hda: Maxtor 54098H8, ATA DISK drive
hdb: WDC WD68AA, ATA DISK drive
hdc: PLEXTOR CD-R PX-W1610A, ATAPI CD/DVD-ROM drive
hdd: CREATIVE CD5233E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 80041248 sectors (40981 MB) w/2048KiB Cache, CHS=4982/255/63
hdb: 13281408 sectors (6800 MB) w/2048KiB Cache, CHS=826/255/63
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 >
 hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 >

--- snip

The "root" partition on the 1st hard drive is at /dev/hda12

Interesting is that when I tried to mount this from Tom's, the
partitions from hda9 through hda12 did not appear. I get this:

 hda: hda1 hda2 < hda5 hda6 hda7 hda8 >
 hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 hdb9 >

/dev/hda12: Unknown error
Attempt to access beyond end of device
:c: rw=0, want=1, limit=0
FAT bread failed

Running linux from the second hard drive, I can mount all of these
partitions and the files all appear.

I have tried to run Partition Magic from Windows and it won't run saying
that it can't access the MBR, according to the error code. I am able to
run Partition Magic from DOS fine and all looks well and all checks say
OK. 

I have tried "FDISK /MBR" even though the partition table running fdisk
in linux looks fine:

# fdisk /dev/hda

The number of cylinders for this disk is set to 4982.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/hda: 255 heads, 63 sectors, 4982 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       764   6136798+   b  Win95 FAT32
/dev/hda2           765      4982  33881085    f  Win95 Ext'd (LBA)
/dev/hda5           765      1528   6136798+   b  Win95 FAT32
/dev/hda6          1529      4061  20346291    b  Win95 FAT32
/dev/hda7          4062      4089    224878+   b  Win95 FAT32
/dev/hda8          4090      4133    353398+  82  Linux swap
/dev/hda9          4134      4172    313236   83  Linux
/dev/hda10         4173      4211    313236   83  Linux
/dev/hda11         4212      4466   2048256   83  Linux
/dev/hda12         4467      4982   4144738+  83  Linux

Command (m for help): q

[root@glenn /home/glenn] 
# fdisk /dev/hdb

Command (m for help): p

Disk /dev/hdb: 255 heads, 63 sectors, 826 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1             1        78    626503+   b  Win95 FAT32
/dev/hdb2            79       826   6008310    5  Extended
/dev/hdb5            79       122    353398+  82  Linux swap
/dev/hdb6           123       161    313236   83  Linux
/dev/hdb7           162       200    313236   83  Linux
/dev/hdb8           201       392   1542208+  83  Linux
/dev/hdb9           393       826   3486073+  83  Linux

Does anyone have any ideas on how to resolve this?

Thanks,
Glenn

Reply via email to