Re: [Sheflug] aargh, disk crash

[matt fairtlough <xxxxx [at] xxxxxxxxxxxxxx>]

I wrote:

> Now, I have found out what the jumper settings are.  Currently it is 
> set  to master, and so is my old drive, which might account for why 
> both  drives are not recognised on boot up.  I'd like to set it to 
> slave, but  the cabling is awkward given the slot it now occupies.  Ho 
> hum.  Does it  matter which is master and which slave given that I 
> will be booting up  from the old drive?   There are 16 different 
> jumper settings documented  in tiny print on the end of my 
> IBM-DTLA-307045 (did I say 75G?  That was  optimistic!) and tbh I 
> haven't much of an idea which to use. 

I still don't, but I re-jumpered (or tried to, more on that later) 
according to the documentation I found on the Web: from Maxtor's own 
site.  This time, both disks are recognised (well, usually, but that's 
another story), but I don't seem to be able to write anything to the new 
disk.  I tried under win2k (the disk was correctly identified but I 
couldn't write a signature [whatever that is]) and under linux as below:

bash-2.05# fdisk -l /dev/hdf

Disk /dev/hdf: 16 heads, 63 sectors, 119150 cylinders
Units = cylinders of 1008 * 512 bytes

Disk /dev/hdf doesn't contain a valid partition table
bash-2.05# cfdisk /dev/hdf

FATAL ERROR: Bad signature on partition table
                         Press any key to exit cfdisk

So I'm told this could be because the disk isn't jumpered correctly.  
This is the pin arrangement:

           o o o   o
           o o o o o

note the missing pin!

the 3 settings documented are Master            Slave            Cable 
select
                                _  ___           ___  ___           _   ___
                               |o||o o|   o    o|o o||  o|        o|o|o|  o|
                                   ---           ---  ---               ---
                               |o| o o  o o    o o o  o o         o|o|! o o
                                -                                   -
which makes sense for the master, but not for the cable select or the 
slave positions, because the jumper on the right simply isn't doing 
anything: it doesn't connect anything to anything and cannot be securely 
fastened in the position shown because of the missing pin...

any suggestions?

Matt.

> 
> Another point is that I remember setting everything up originally on 
> the  standard hdd driver, not the Highpoint UDMA/66 controller.  Would 
> that  also apply now, or is it safe to fdisk etc. the new drive on the 
> UDMA  controller once I've got a system installed?  Hmm.

I guess that doesn't matter.

-- 
 ------------------------------------------------
| Matt Fairtlough                                |     
| 22 Harley Road                                 |
| Sheffield S11 9SE UK  tel. 0114 236 2067       |
 ------------------------------------------------

___________________________________________________________________

Sheffield Linux User's Group - http://www.sheflug.co.uk . 
To unsubscribe from this list send mail to 
shef-lug-request@list.sheflug.org.uk with the word
"unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.