Forum Home
Press F1
Thread ID: 24011	2002-09-01 07:45:00	Help please - New Seagate drive	andy (473)	Press F1

Post ID	Timestamp	Content	User
75505	2002-09-01 07:45:00	G'day again. Well it all turned to custard. I fitted the new seagate 80 gig drive today. What a headache. I decided to fit the new drive as primary master, cd writer as pri. slave, old seagate 20 gig drive as sec. master and Zip as sec.slave. The problems started immediately. The Bios will only recognise 32 Gb. No - I am not game to try a BIOS upgrade - last time I tried that it cost me a new MB! The drive can be jumpered to 32 gb max so I tried that and the BIOS saw it but- Fdisk will not recognise that I have any drives at all! I used the Seagate diskwizard software and all appeared to work fine except the cd causes a GP fault as soon as a disk is inserted. I tried the new drive and cd only on separate ide channels - cd still caused the fault. I have now tried all combinations of drives and the only combinations that works is having the old drive as Pri.master, cd as pri slave, new drive as sec master and zip as sec slave. I can use the seagate software to enable the full 80 gb, but only as a data drive. As soon as I try to make it bootable, the cd crashes the system. Fdisk still say I have no drives at all although the BIOS recognises them all! I'm confused, somewhat pissed off, but everything is working - just not how I wanted it, so- Can anyone explain to me what is going on? Can I get what I want or do I have to upgrade my whole system (in the pipeline, but probably 8-10 months away). System - pcchips m741lmrt mb, pIII 550 slot1 cpu, seagate ST380021A 80 gb drive, seagate 20gb drive (not sure of model), Win 98 SE, Acer 8x4x32 cd-rw, zip100 IDE, 390 mb sdram. Cheers, Ray.A.	andy (473)
75506	2002-09-01 07:58:00	For a start I would try to have the new drive as Pri. Master, and the old one as Pri. Slave, with the two drives on sec with CD as master. Then I would check your BIOS manual and the webpage to see if there is a simple setting prob. Then I would post back here with the results. BTW, what makes/models are the HD's, CD, ZIP, mobo, BIOS? Cheers Good Luck Ray. G P	Graham Petrie (449)
75507	2002-09-01 07:58:00	READ the whole post!! sorry, ignore the model request info! G P	Graham Petrie (449)
75508	2002-09-01 08:06:00	Check out the seagate website.. i had the same problem using an 80gig seagate on a VA503 MB which both my machines have. I ended up putting it in sam the suse/linux box, and flashing the bios was the only real solution... Your lucky, i put the 32 gig jumper setting on the 80, and vanessas MoBo would see it, but only as a slave drive!! X-( But i wanted to use it as Vanessas only drive. I got over it... in Sam, my other comp, where i ended up doing the bios flash thingy, it sits as a single drive. B-) Take care, try not to fry the board!	Chris Wilson (431)
75509	2002-09-01 08:13:00	if the BIOS only recognises 32Gb then that is it, unless you are willing to upgrade the BIOS (which you said you were not) you seem to be stuck. One option would be to partition off the first 10-20Gb on the new one, leave blank, use the rest as data with OS on the original drive (the 20Gb). Then when you upgrade the box, put the data drive in it and install an OS on the blank partition. That way you keep the data, and maybe sell the old box with that original drive in. With those sort of BIOS faults going on there seems little point struggling on with setting it up the way you wanted to, you would be asking for trouble later I suspect. You should be able to fdisk and make bootable the new drive if its the only one, you may be able to skip making it bootable if you use another partition manager (and maybe not) The GP fault seems pretty clearly to be a function of the size of the new drive. If the box doesnt take the size there isnt much you can do, apart from accepting less storage space. Can you move buying the new box forward?	allanh (1687)
75510	2002-09-01 08:15:00	Thanks guys, I'll try some of the suggestions tomorrow if poss and get back to you - got to go and do the father's day thing with the kids now. Still not keen on flashing the BIOS, but am totally perplexed with the fdisk status of no drives present! Regards, Ray	andy (473)
75511	2002-09-01 08:22:00	I think you may have it there Allan. I might just have to accept it as a 80 gig data drive - i probably wouldn't see any speed gains from having the new drive as master anyway. I only got the 80 gb because it was an insignificant increase in price from the 40 gig drive. The new system will be an as-well-as when it arrives so this one can stay as it is. Gotta go. Cheers, Ray A.	andy (473)
75512	2002-09-01 08:30:00	sorry to sort of take over this thread but.... well not really, it's kind of relevent. in vanessa i have a retarded 40gig HDD (the jumper is still in to make it a 31gig drive) if i was to pull this jumper, and stick it in a machine which knew what a 40 gig HDD was, would it see the data thats allready there? I figure andy/Ray.A. will have the same problem shortly with the 80.	Chris Wilson (431)
75513	2002-09-01 08:47:00	if i was to pull this jumper, and stick it in a machine which knew what a 40 gig HDD was, would it see the data thats allready there? yes. As long as its a compatible filesystem. you can move drives around and as long as the OS can see it it will be able to read the data. thats why I suggest leaving a blank partition at the beginning to install an OS on, then moving the drive over later.	allanh (1687)
75514	2002-09-01 08:56:00	so if i moved the retarded 40 from my 98 box pulled the jumper and moved it to my linux box, would it see a 40 gig drive with twenty something gig of data?????? Just checking... I'm very new with linux	Chris Wilson (431)
1 2