Gentoo Archives: gentoo-amd64

From: Raffaele BELARDI <raffaele.belardi@××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] not amd64 specific - disk failure
Date: Mon, 19 Nov 2007 13:27:20
Message-Id: 47418F30.6050607@st.com
In Reply to: Re: [gentoo-amd64] not amd64 specific - disk failure by Beso
1 Beso,
2
3 thanks for the links, I've already started reading. I've also got a new
4 drive to copy the recovered data (if any, cross fingers...)
5
6 Most of the resources I've read up to now imply that e.g. /dev/sdc1 is
7 detected and a 'bad superblock' message displayed when attempting to mount.
8
9 In my case the kernel is unable to detect /dev/sdc1, after the long list
10 of read errors below it ends up with only /dev/sdc.
11
12 Does this look like superblock issue, or something worse?
13
14 thanks,
15
16 raffaele
17
18 Beso wrote:
19 > before doing something on the disk first, read all and then take a
20 > decision on which options may help you. on my reiserfs filesystem, the
21 > included utils were enough to let me recover about 98% of the data after
22 > the full index rebuild. if you've journaled your filesystem, then i
23 > think that you should be able to recover it. also, it may only be a
24 > problem of superblock and in that case the second link might help you
25 > more. anyway, get a disk that can contain all the data that there was on
26 > the failed one, since you wouldn't want to do stuff on it to avoid loss
27 > of data.
28 > try reading this (the ext2/3 part):
29 > http://edseek.com/archives/2004/02/25/ext3-filesystem-bad-superblock-recovery/
30 > and this:
31 > http://forums.gentoo.org/viewtopic-t-569462-highlight-ext3+recover.html
32 > or you might try this utility:
33 > http://www.cgsecurity.org/wiki/PhotoRec
34 >
35 > 2007/11/19, Raffaele BELARDI <raffaele.belardi@××.com
36 > <mailto:raffaele.belardi@××.com>>:
37 >
38 > Yesterday evening I had one 250Gb SATA disk Maxtor MaXLine Plus II fail.
39 > The drive is formatted as ext3, single partition (sdc1), no RAID, used
40 > as an archive of divx movies, completely full with data. Motherboard is
41 > ASUS M2NPV-VM (Nvidia Nforce 430 chipset), I can easily mount it on an
42 > ASUS K8V SE (Via K8T800 chipset) if it helps.
43 >
44 > At boot the syslog shows (more or less):
45 >
46 > I/O buffer read error: logical block 0
47 > I/O buffer read error: logical block 1
48 >
49 > Any attempt to mount /dev/sdc1 results in tens of the above message
50 > (plus other details I don't remember right now) and finally fails.
51 >
52 > fdisk -l shows the partition table as it should be.
53 >
54 > It was late night so I gave up. Are there any chances to recover my data
55 > by e.g. specifying a different superblock (whatever that is)? Any links
56 > to help me?
57 >
58 > thanks,
59 >
60 > raffaele
61 >
62 > PS I bought the drive in 2005 and I've used it only to archive movies,
63 > so very little. It' the last Maxtor I buy (ok, also because it's Seagate
64 > now..)
65 > --
66 > gentoo-amd64@g.o <mailto:gentoo-amd64@g.o> mailing list
67 >
68 >
69 >
70 >
71 > --
72 > dott. ing. beso
73 --
74 gentoo-amd64@g.o mailing list

Replies

Subject Author
Re: [gentoo-amd64] not amd64 specific - disk failure Beso <givemesugarr@×××××.com>
[gentoo-amd64] Re: not amd64 specific - disk failure Duncan <1i5t5.duncan@×××.net>