View previous topic :: View next topic |
Author |
Message |
Marwin n00b
Joined: 27 Oct 2002 Posts: 58
|
Posted: Sat Apr 17, 2004 10:09 am Post subject: HD problem (Solved) |
|
|
I just bought a Westen Digital 120GB (8MB) harddrive. But I can't get Gentoo to find it. If I check at the BIOS I see a 8.4GB, and that's OK because the BIOS can't handle bigger discs than 8.4GB. But Gentoo should find it even if BIOS doesn't.
dmesg doesn't show hda. And I know that the disc is hda
Anyone know got ideas of how to solve my issue?
Regards,
Marwin _________________ [ Never trust an operationsystem you don't have sources for ]
Last edited by Marwin on Sat Apr 17, 2004 7:41 pm; edited 1 time in total |
|
Back to top |
|
|
golloza Guru
Joined: 14 Mar 2004 Posts: 427
|
Posted: Sat Apr 17, 2004 10:43 am Post subject: |
|
|
Is it a S-ATA drive? |
|
Back to top |
|
|
Marwin n00b
Joined: 27 Oct 2002 Posts: 58
|
Posted: Sat Apr 17, 2004 10:50 am Post subject: |
|
|
golloza wrote: | Is it a S-ATA drive? |
No, it's an ATA-drive. _________________ [ Never trust an operationsystem you don't have sources for ] |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54793 Location: 56N 3W
|
Posted: Sat Apr 17, 2004 3:11 pm Post subject: |
|
|
Marwin,
Do This will list the IDE drives on your system.
The old BIOS 8.4Gb was a feature of how early LBA worked but there is a hard limit at 33.4Gb (approx) when you need more than 32 bits to hold the block address.
You may need to jumper the drive to 'soft clip' at 33.4Gb to stop the BIOS reporting rubbish. Linux will see past this limit.
You will need to fdisk it to create partitions before you can use it but thats difficult if you can't spot it. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Marwin n00b
Joined: 27 Oct 2002 Posts: 58
|
Posted: Sat Apr 17, 2004 5:12 pm Post subject: |
|
|
This is strange:
Code: |
hilda / # ls /dev/hd*
/dev/hda /dev/hdb15 /dev/hdc3 /dev/hde /dev/hdf15 /dev/hdg3
/dev/hda1 /dev/hdb16 /dev/hdc4 /dev/hde1 /dev/hdf16 /dev/hdg4
/dev/hda10 /dev/hdb17 /dev/hdc5 /dev/hde10 /dev/hdf17 /dev/hdg5
/dev/hda11 /dev/hdb18 /dev/hdc6 /dev/hde11 /dev/hdf18 /dev/hdg6
/dev/hda12 /dev/hdb19 /dev/hdc7 /dev/hde12 /dev/hdf19 /dev/hdg7
/dev/hda13 /dev/hdb2 /dev/hdc8 /dev/hde13 /dev/hdf2 /dev/hdg8
/dev/hda14 /dev/hdb20 /dev/hdc9 /dev/hde14 /dev/hdf20 /dev/hdg9
/dev/hda15 /dev/hdb3 /dev/hdd /dev/hde15 /dev/hdf3 /dev/hdh
/dev/hda16 /dev/hdb4 /dev/hdd1 /dev/hde16 /dev/hdf4 /dev/hdh1
/dev/hda17 /dev/hdb5 /dev/hdd10 /dev/hde17 /dev/hdf5 /dev/hdh10
/dev/hda18 /dev/hdb6 /dev/hdd11 /dev/hde18 /dev/hdf6 /dev/hdh11
/dev/hda19 /dev/hdb7 /dev/hdd12 /dev/hde19 /dev/hdf7 /dev/hdh12
/dev/hda2 /dev/hdb8 /dev/hdd13 /dev/hde2 /dev/hdf8 /dev/hdh13
/dev/hda20 /dev/hdb9 /dev/hdd14 /dev/hde20 /dev/hdf9 /dev/hdh14
/dev/hda3 /dev/hdc /dev/hdd15 /dev/hde3 /dev/hdg /dev/hdh15
/dev/hda4 /dev/hdc1 /dev/hdd16 /dev/hde4 /dev/hdg1 /dev/hdh16
/dev/hda5 /dev/hdc10 /dev/hdd17 /dev/hde5 /dev/hdg10 /dev/hdh17
/dev/hda6 /dev/hdc11 /dev/hdd18 /dev/hde6 /dev/hdg11 /dev/hdh18
/dev/hda7 /dev/hdc12 /dev/hdd19 /dev/hde7 /dev/hdg12 /dev/hdh19
/dev/hda8 /dev/hdc13 /dev/hdd2 /dev/hde8 /dev/hdg13 /dev/hdh2
/dev/hda9 /dev/hdc14 /dev/hdd20 /dev/hde9 /dev/hdg14 /dev/hdh20
/dev/hdb /dev/hdc15 /dev/hdd3 /dev/hdf /dev/hdg15 /dev/hdh3
/dev/hdb1 /dev/hdc16 /dev/hdd4 /dev/hdf1 /dev/hdg16 /dev/hdh4
/dev/hdb10 /dev/hdc17 /dev/hdd5 /dev/hdf10 /dev/hdg17 /dev/hdh5
/dev/hdb11 /dev/hdc18 /dev/hdd6 /dev/hdf11 /dev/hdg18 /dev/hdh6
/dev/hdb12 /dev/hdc19 /dev/hdd7 /dev/hdf12 /dev/hdg19 /dev/hdh7
/dev/hdb13 /dev/hdc2 /dev/hdd8 /dev/hdf13 /dev/hdg2 /dev/hdh8
/dev/hdb14 /dev/hdc20 /dev/hdd9 /dev/hdf14 /dev/hdg20 /dev/hdh9
|
I have partionated the /dev/hda but I can't access it from the computer it's in now. I setup one partition in my WS and I now tried to put it in the server, but I can't find it.
Code: |
hilda root # fdisk /dev/hda
Unable to open /dev/hda
|
_________________ [ Never trust an operationsystem you don't have sources for ] |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54793 Location: 56N 3W
|
Posted: Sat Apr 17, 2004 5:27 pm Post subject: |
|
|
Marwin,
Post the dribe model number and an ASCII art sketch of the jumper positions as they are set now. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
superuser Apprentice
Joined: 14 Mar 2004 Posts: 166 Location: Colorado, Colorado Springs
|
Posted: Sat Apr 17, 2004 5:54 pm Post subject: |
|
|
Marwin,
I think you were supposed to do ls /dev/hd?, not ls /dev/hd*, weren't you?
This makes a slight difference on my system:
Code: | ls /dev/hd?
/dev/hda /dev/hdb
| Code: |
ls /dev/hd*
/dev/hda /dev/hda1 /dev/hda2 /dev/hda3 /dev/hda4 /dev/hdb | Moritz |
|
Back to top |
|
|
Marwin n00b
Joined: 27 Oct 2002 Posts: 58
|
Posted: Sat Apr 17, 2004 6:31 pm Post subject: |
|
|
Code: | hilda root # ls /dev/hd?
/dev/hda /dev/hdb /dev/hdc /dev/hdd /dev/hde /dev/hdf /dev/hdg /dev/hdh
|
_________________ [ Never trust an operationsystem you don't have sources for ] |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54793 Location: 56N 3W
|
Posted: Sat Apr 17, 2004 7:01 pm Post subject: |
|
|
Marwin,
Are you useing devfs?
All those /dev/hd? entries are symbolic links created by devfsd when it finds a real device.
Did you have another (non devfs) linux installed on that drive before Gentoo?
If so, its /dev has been left behind.
If your new drive is /dev/hda how are you booting to be able to see that Gentoo can't see it?
With some other linux?
That would explain the misleading /dev/hd?
Boot with the livecd and redo the ls /dev/hd? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Marwin n00b
Joined: 27 Oct 2002 Posts: 58
|
Posted: Sat Apr 17, 2004 7:34 pm Post subject: |
|
|
LOL!
I found what the problem was!
I looked at the HD-Jumpering, and I had chosen that "Master w/ Slave Drive" was used. Acctualy, I don't know what that jumping does, but I think that if you got two discs, it choose Master if and Slave-drivers is detected. So I changed to Master and it worked. The reason it had worked earlier was probably that I had another disc at the same cable.
Thanks for the help! _________________ [ Never trust an operationsystem you don't have sources for ] |
|
Back to top |
|
|
|