Mounting hard drive; Hello, where are you?
Madison Kelly
linux-5ZoueyuiTZhBDgjK7y7TUQ at public.gmane.org
Tue Oct 28 02:07:26 UTC 2003
[root at hannah root]# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 522 4192933+ b Win95 FAT32
/dev/hda2 523 587 522112+ 83 Linux
/dev/hda3 588 718 1052257+ 82 Linux swap
/dev/hda4 719 9076 67135635 f Win95 Ext'd (LBA)
/dev/hda5 719 8036 58781803+ 83 Linux
/dev/hda6 8037 8558 4192933+ 83 Linux
/dev/hda7 8559 9076 4160803+ 83 Linux
Disk /dev/hdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 33 265041 83 Linux
/dev/hdb2 34 164 1052257+ 82 Linux swap
/dev/hdb3 165 9729 76830862+ 83 Linux
[root at hannah root]# fdisk -l /dev/hdc
[root at hannah root]#
Nothing...
After posting I started thinking; this is a Dell box and I had a
problem once before where another Dell box with WinME/FAT32 had been
setup using some funky PartitionMagic-type porgram so that the FAT32
partition was not created as it would normally be. In that case the
reasult was a drive where the backup copy of the FAT was placed on a
logical head higher than the drive's default number of logical heads. I
wonder if that might be similar (in a different way) to what is
happening here.
More: When I cat partitions -something- is seen:
[root at hannah proc]# cat partitions
major minor #blocks name rio rmerge rsect ruse wio wmerge wsect
wuse running use aveq
22 0 1073741823 hdc 2 6 16 0 0 0 0 0 -10 1164540 31326712
3 0 78150744 hda 9631 29172 308692 694810 3549 5535 72706
185720 -9 1167390 31040812
3 1 4192933 hda1 1 3 8 10 0 0 0 0 0 10 10
3 2 522112 hda2 15 28 86 210 11 2 26 1690 0 1900 1900
3 3 1052257 hda3 2 3 16 20 0 0 0 0 0 20 20
3 4 1 hda4 0 0 0 0 0 0 0 0 0 0 0
3 5 58781803 hda5 316 4051 34562 594690 437 214 5184 5670 2
299670 601020
3 6 4192933 hda6 9271 24936 273642 99630 3097 5316 67464
178360 0 54770 278030
3 7 4160803 hda7 10 59 162 70 4 3 32 0 0 70 70
3 64 78150744 hdb 9 51 120 70 0 0 0 0 -11 1170530 30162072
3 65 265041 hdb1 1 3 8 10 0 0 0 0 0 10 10
3 66 1052257 hdb2 1 3 8 0 0 0 0 0 0 0 0
3 67 76830862 hdb3 1 3 8 0 0 0 0 0 0 0 0
[root at hannah proc]#
Notice the first line?
Do you (or someone) know FDISK well enough to know what I might try
to get a closer look at the drive? Well, I will keep looking... Thanks!
Madison
Marc Lijour (Professeur d'Informatique) wrote:
> Le 27 Octobre 2003 20:54, Madison Kelly a écrit :
>
>>Hi all,
>>
>> I am trying to do something very simple but it is being anything
>>but... I have a laptop hard drive here that I am trying to image before
>>I erase. Simple enough; I connect it as Master on the secondary channel,
>>boot, '# mount -t vfat /dev/hdc1 /mnt/backup'... nothing. Try '#fdisk
>>-l', nothing. I know that hardware-wise it's fine because I tried (uggh)
>>booting my Win2k part and there it is seen fine. Also, on boot the BIOS
>>sees it (not that it matters to Linux) and on powerdown it reports to
>>flush HDC...
>
>
> you did fdisk /dev/hdc?
>
>
>> So, does anyone have any idea why a seemingly fine connected FAT32
>>hard drive (10GB) would not be seen by Linux's FDISK but it WOULD be
>>found by Win2k? Isn't that pretty bass-ackwards? Any help is appreciated!
>>
>>Madison
>>
>>--
>>The Toronto Linux Users Group. Meetings: http://tlug.ss.org
>>TLUG requests: Linux topics, No HTML, wrap text below 80 columns
>>How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
>
>
> --
> The Toronto Linux Users Group. Meetings: http://tlug.ss.org
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
>
--
The Toronto Linux Users Group. Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
More information about the Legacy
mailing list