Discussion Locked

Hard disk recognized no volume assigned

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an odd one. I am trying to rescue information from a Quantum Fireball 14GB drive from an older Gateway - Fireball has Win98 loaded on a single FAT32 partition and it works fine in the older Gateway system. I am doing this by physically placing the drive into my newer system, along with my Maxtor 40GB drive (basic simple partitions, C: - system and D: - extended, both NTFS) on the Primary IDE channel. I do have the jumpers on the drives set correctly (Maxtor - master, Fireball - slave). I also have two other IDE devices, DVD-ROM and CDRW, both on the secondary IDE channel. I am running XP Pro (sp1+). The BIOS detects the additional drive. Disk Management detects the additional drive, but there is no volume label assigned (no drive letter). The only action that can be performed by Disk Management is "Delete Partition." I cannot "Assign/Change Drive Letter"

I have tried removing my DVD and CDRW drives from the secondary IDE channel and putting the Fireball on it, as master and slave, but nothing changes.

What am I missing? I should be able to have more than one physical hard disk on an IDE channel, and the drive works fine in another machine. Anyone got a clue? Thanks...

9 replies

by info

I think you will find it is because the older drive is fat32 and the newer in ntfs , my solution would be to network the 2 machine and transfer the data that way, the other option wich is a long shot is to set the new drive to fat32 and then give ita go

by compumgk

Sorry, but I can't accept that one. FAT32 is a perfectly recognizable file system to WinXP.

by thechas

Depending on how old the Gateway is, the 14GB drive may well be larger than the BIOS could recognize.

If so, it is likely that a drive overlay program was installed to allow the full drive to be accessed.

Since the overlay programs all run from the boot partition, the program does not load when the drive with the program is installed as a slave.

You have a few options:
Un-install the overlay program with the drive mounted in your new PC as the primary master.
(there is some risk of data lose, so proceed with caution)

Use a partition manager to remove the overlay program. (less risk than the first option, but not zero risk)

Network the 2 PCs, and transfer the files that way. (least risk to the data)

Chas

by compumgk

I don't know if it is an issue of age, the Gateway is a fairly recent machine. The problem, however, was an overlay. I couldn't network the two machines - only one monitor/mouse/keyboard and no KVM. I didn't want to risk losing any of the data, as it was a client's, so I didn't mess around with trying to remove the overlay. I ended up installing my CDRW into the Gateway, burning a copy of the data, restoring the Gateway from the restoration CDs, re-installed the apps that weren't on the restoration (most of them), and then put the data back. The Gateway is better than new with no data loss. The overlay was the problem.

Thanks to all...

by maelgwyn

I agree with TheChaz... to check that; boot it up and check for the banner (seagate has a blue one)

If that exists, then we are dealing with an DDR (Direct Drive Overlay). You will have to remove it with the Seagate (or Quantam as you need) utility, FDISK /MBR or a 3rd party util. This can risk loss of data to that drive; so be careful. Another *idea* is to install the DDR onto the newer drive, by physically installing the quantam and making it do it thataway... it is an option, ne? THe final option is networking, which in this case, could be the only answer...

Anywho, sorry for not being much help

Maelgwyn

by sgt_shultz

well, maybe i am completely nuts but--try to boot from the *old* drive in your new system? with the old drive as master, the new drive as slave? i'm thinking you might be able to get it back up well enough to copy the files off...especially in safe mode (which files, btw. the whole os?)...do you care if you hose the old os registry, cause it might. backup the registry on the old one first, then you can always fix it back up...then, according to these other posts, the driver overlay software will kick in and you can copy the stuff you need to the new drive?
if you have the BIOS and the computer recognising the drive, it is not a cabling issue...
let us know if you need help 'networking' or cabling the two pc's together if you decide to go that way...

This discussion is closed to new replies.