[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sheflug] aargh, disk crash



Baz,

Hmm, doesn't seem so simple after all.  It will seem to be once I've 
been through the process a couple of times I suppose.

Barrie Bremner wrote:

> Matt wrote:
> 
>> yes, badblocks tells me I've about 10 bad blocks.  I'll need an hdd
>> while the knackered one is out for replacement anyway; and then I'll
>> want to keep it for backups (I've not been burned so badly yet, but I
>> could have lost more and still could) since I need a quick and simple
>> way of making incremental backups [presumably some cron scripts using
>> find etc. would be enough for that?]
> 
> 
> Try rsync an job - it can be run from one disk to another, not just across 
> hosts.

rsync and ?job what's job though?

> 
>> would a block size of 1k be sensible?  and is it relatively simple to
>> fit an internal hdd (I assume that it is a matter of a screwdriver and
>> plugging in some connectors)?
> 
> 
> Dunno about the block size - just stick to defaults, I'm not doing anything so 
> fancy that I have to tweak it that much.
> 
> Yes - fitting a harddrive is a 5 minute jon at the most. Check the jumper 
> settings, plug the interface cable in and stick in the power cable.
> You might need to mess about in BIOS to get it to recognise the new drive - 
> it's also fairly easy.

I think it took me rather longer than 5 minutes...not being experienced 
in fiddling with hardware: I had to take the memory out and move several 
cables to make room to fit the disk.  But that was the easy bit...

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 think 
maybe I'd better leave the old drive as master and bite the bullet with 
the cabling.  The jumpers look very fiddly though...  Then I don't 
really know what BIOS settings need altering but I guess there are FAQs 
out there.

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.

> 
> After that, fdisk, mkreiserfs/mk22fs and mount the drive.

and that's probably when the fun starts.  [I'll probably still be on 
this job when I bring my machine in to the Sheflug meeting on Saturday: 
but the meeting gives me a lot of hope for eventual success]

ta again for your help,

Matt.

> 

-- 
 ------------------------------------------------
| 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.