PDA

View Full Version : Knoppix doesn't recognize 120GB hard drive.



dragon
04-23-2003, 07:49 AM
Does Knoppix support a Maxtor 120 GB hard drive? That seems to be the only problem I could not figure out for myself. I can't mount the drive. It is FAT32 without any operating system on it. Just storage. Any ideas? :lol:

Stephen
04-23-2003, 08:08 AM
What command did you use knoppix should recognize the drive. Are you running from the CD or HD?

dragon
04-23-2003, 08:49 AM
Running from the CD only. Everything configures correctly with just
Knoppix wheelmouse
All, except the hdb5 120 GB hard drive

Stephen
04-23-2003, 09:11 AM
Running from the CD only. Everything configures correctly with just
Knoppix wheelmouse
All, except the hdb5 120 GB hard drive

So how did you try to mount the drive???

dragon
04-23-2003, 09:25 AM
I clicked on the icon on the KDE desktop.

Stephen
04-23-2003, 06:23 PM
Open a console window and type dmesg | less you will have the boot messages on the screen one page at a time there will be lines refering to the drives hda, hdb, etc.. this will tell you they were detected. If you do a mount in the same window this tells you the mounted file systems in use if hdb5 is not there then sudo mount -t vfat /dev/hdb5 /mnt/hdb5 will mount the drive at the mount point /mnt/hdb5. You could also right click on the icon and choose properties and check that the icon actually refers to the proper device (/dev/hdb5).

dragon
04-24-2003, 08:02 AM
Will give that a try and let you know the results. Thank you for the help!

dragon
04-24-2003, 08:37 AM
did exactly as you said. Got the following error:
Wrong FS type, bad superblock on /dev/hdb1, or too many mounted file systems.
(I was wrong, it's hdb1)
I have a 40 GB drive that is partitioned into 10GB and 30GB with other op systems on them. I'm not surpirsed, but I had hoped that Knoppix would over come this problem. Suse 8.1 does the same thing. I was looking forward to eliminating the paid for op systems and going strictly linux in the future, if I can find one that is compatible with all my hardware.

Stephen
04-24-2003, 09:33 AM
Post the output of fdisk -l /dev/hdb so I see what partitions are on the drive.

dragon
04-25-2003, 05:49 AM
OK. Results of fdisk -l /dev/hdb1
error: cannot open dev/hdb1
I checked under windows and the partition shows to be a FAT32 with the MBR style. Should be just another standard FAT32 drive. I don't understand it, unless Knoppix doesn't support larger hard drives. I'll go back and check the bios settings. I installed it using the Maxtor installation software. I'm wondering if there is a bios driver that loads at boot up to force the hard drive, or if it is truely recognized by the bios. That would make sense, but the motherboard is a K7s5a and should support it.

dragon
04-25-2003, 05:59 AM
Checked the bios. It doesn't seem to be forced. It was set up for auto detection by the bios. It configured auto to be a set value under the bios and it showed the full storage size.

ktheking
05-03-2003, 03:42 PM
Simplicity is the key...

always check one step at a time and start from the bottom..

1)How was this FAT32 created ? (from linux,partition manager,dos,...)
2)Is there a compression utlity or safety soft active on these partitions ?
3)In BIOS , is LBA active ?
4)FAT32 is only working till 64Gb . After it some tricks have to be done to get it working.
5)use 'parted' (just type at command line from root box) to check info about disk.
6)If everything fails create a dos floppy bootdisk and launch xfdisk after boot. (check out http://www.mecronome.de/xfdisk/index.html
) with this tool you can easely manage partitions.

greetzzzz...

Henk Poley
05-06-2003, 05:58 PM
I'll go back and check the bios settings. I installed it using the Maxtor installation software.
So could it be that the Maxtor setup software installed an INT13 program in your bootsector (MBR)? You need such a program if your BIOS doesn support (that) large disks. If you boot from HD this little program will translate the read/write commands, but if you boot from CD it won't be loaded.

Could this be it?

btw, if you installed LILO in your MBR and windows still detects the disk correctly, then you don't have an INT13 extension installed (there can only be one thing in MBR).

Stephen
05-06-2003, 06:38 PM
So could it be that the Maxtor setup software installed an INT13 program in your bootsector (MBR)? You need such a program if your BIOS doesn support (that) large disks. If you boot from HD this little program will translate the read/write commands, but if you boot from CD it won't be loaded.

Could this be it?



That would only be a problem with the doz linux would recognize the true size of the drive with information from the drive itself.

dragon
05-06-2003, 07:00 PM
I think that is the case. I installed the hard drive with the Max Balst due to the fact that Windows fdisk doesn't work with bigger hard drives. It's not needed because the bios does support the drive, but I think Max Blast installed the INT 13 commands anyway. I have since found a poweruser version of windows fdisk that allows partitioning of up to 250GB without the INT 13 commands.
Thanks for the help.

DOOManiac
06-16-2003, 01:42 AM
First off, sorry to bump an old post. But so far its been the most relevant to my problem, as I have a very very similar problem, but need a different solution.

I don't know that much about Linux, but I've been wanting to use Knoppix as a Rescue Disc/Spare Time Plaything. I ran into a similar problem of it not mounting my 74GB FAT32 partition. Its the second partition on my drive (other is NTFS), which is on the Primary IDE as Master.

It was mentioned in this thread that I must jump through hoops to get Knoppix to read the drive. Are these hoops that I can jump through with just the standard knoppix distro, w/o needing other things?

Also dragon (I hope you see this) what is the advanced fdisk that you found? Cause I could use something like that too, as WinXP is fixed not to let you format bigger than 40gb or so in fat32 even though it recognizes the drive size.

I've Google'd everything I can think of trying to find an answer, but so far this thread is the closest thing I've seen to my problem. Thanks for any help you guys can give me, I appreciate it.


Here is a fdisk -l /dev/hda
Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 9768 78461428+ 7 HPFS/NTFS
/dev/hda2 9769 19457 77826892+ f Win95 Ext'd (LBA)
/dev/hda5 9769 19457 77826861 b Win95 FAT32

Stephen
06-16-2003, 02:30 AM
I don't know that much about Linux, but I've been wanting to use Knoppix as a Rescue Disc/Spare Time Plaything. I ran into a similar problem of it not mounting my 74GB FAT32 partition. Its the second partition on my drive (other is NTFS), which is on the Primary IDE as Master.

It was mentioned in this thread that I must jump through hoops to get Knoppix to read the drive. Are these hoops that I can jump through with just the standard knoppix distro, w/o needing other things?


What error is it giving you when it tries to mount the partition and what command did you use to mount it? post the output of any errors.

dragon
06-16-2003, 03:37 AM
The advanced fdisk I found will format up to 120 GB and is based on the standard DOS fdisk. I honestly don't know where I found it. I cruise so many freeware sites. I think I found it on one of those Windows XP Tips and Tricks sites, I'm sure that's where I found it. It was a link to a Microsoft back page that most people don't usually see. But, that was months ago and my memory of where I found it has faded. I will have to find the download again, might be on one of about 100 cd's, but I will attempt to locate it and post it. :P

dragon
06-16-2003, 03:42 AM
By the way, we think we figured out my mounting problems. The 120 GB I was trying to get Knoppix to see was configured with the Maxtor Max Blast software. We figure the Max Blast put some proprietary software in the boot sector of the hard disk to make it compatible with all bios versions, even though my bios supports it.