From: Matthias Bethke <matthias@towiski.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard Drive Crash - Please Help
Date: Thu, 25 Jan 2007 18:55:07 +0100 [thread overview]
Message-ID: <20070125175507.GA11364@huxley> (raw)
In-Reply-To: <49bf44f10701250820n4ad79b8dudcdba5a8e584545@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
Hi Grant,
on Thursday, 2007-01-25 at 08:20:37, you wrote:
> I successfully wrote an iso of some important files after booting up
> normally (minus hald, X, and vi) so that's good. Is there a utility I
> can run on the disk to see if there is permanent damage? Should I try
> re-emerging packages that are having trouble or should I try to emerge
> -e world?
As Thomas said, use the manufacturer's tools. Maybe smartmontools if
you don't have anything more specialized.
> I suppose I should see if I can write and burn iso's of everything in
> /home/grant/ right away. Is there a good way to get a bunch of data
> into multiple iso's that are each no larger than 650MB? Also, I've
> read man mkisofs and experimented before with trying to preserve
> filenames perfectly but it never comes out quite right. Can anyone
> recommend mkisofs options for preserving filenames perfectly?
I'd recommend trying it over a network or USB/IEEE1394 to another disk
if at all possible. If the HD is dying anyway, writing ISOs to it while
reading many files from another region of the disk at the same time will
kill it very quickly. Same thing with a damaged file system: the more
you write, the greater the damage. I'd try to connect an external HD or
export a partition on some machine on the net, mount the partition
read-only and back it up using tar. Then it's at least reformat/restore
if not swap HD/format/restore.
good luck!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-01-25 18:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 16:20 [gentoo-user] Hard Drive Crash - Please Help Grant
2007-01-25 17:22 ` Thomas Lingefelt
2007-01-25 18:20 ` Grant
[not found] ` <49bf44f10701251028n5813295cycdd61aea0cc08347@mail.gmail.com>
2007-01-25 19:16 ` Etaoin Shrdlu
2007-01-25 21:19 ` Kent Fredric
2007-01-26 17:47 ` Grant
2007-01-26 18:16 ` Grant
2007-01-26 20:24 ` Randy Barlow
2007-01-26 20:20 ` Neil Bothwick
2007-01-26 22:16 ` kashani
2007-01-26 22:43 ` Matthias Bethke
2007-01-27 1:53 ` Grant
2007-01-27 16:38 ` Grant
2007-01-27 18:23 ` Mick
2007-01-27 18:51 ` Grant
2007-01-27 19:43 ` Michal 'vorner' Vaner
2007-01-27 20:10 ` Grant
2007-01-27 20:33 ` Mark Kirkwood
2007-01-27 21:01 ` Grant
2007-01-27 21:19 ` Mark Kirkwood
2007-01-27 22:39 ` Grant
2007-01-27 23:03 ` Mark Kirkwood
2007-01-28 0:01 ` Grant
2007-01-28 6:54 ` Mark Kirkwood
2007-01-28 4:36 ` Grant
2007-01-28 6:26 ` Kent Fredric
2007-01-28 6:20 ` Kent Fredric
2007-01-28 6:17 ` Kent Fredric
2007-01-27 23:09 ` Neil Bothwick
2007-01-27 23:20 ` Neil Bothwick
2007-01-28 0:05 ` Grant
2007-01-28 10:37 ` Neil Bothwick
[not found] ` <20070127171100.GF11364@huxley>
2007-01-27 17:34 ` Grant
2007-01-28 15:55 ` Matthias Bethke
2007-01-28 17:15 ` Grant
2007-01-28 17:40 ` Uwe Thiem
2007-01-28 17:58 ` Mark Knecht
2007-01-29 16:08 ` Grant
2007-01-25 17:55 ` Matthias Bethke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070125175507.GA11364@huxley \
--to=matthias@towiski.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox