public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raffaele BELARDI <raffaele.belardi@st.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] not amd64 specific - disk failure
Date: Mon, 19 Nov 2007 14:27:12 +0100	[thread overview]
Message-ID: <47418F30.6050607@st.com> (raw)
In-Reply-To: <d257c3560711190352m7e22664dtad52c28cd0b5ef4f@mail.gmail.com>

Beso,

thanks for the links, I've already started reading. I've also got a new
drive to copy the recovered data (if any, cross fingers...)

Most of the resources I've read up to now imply that e.g. /dev/sdc1 is
detected and a 'bad superblock' message displayed when attempting to mount.

In my case the kernel is unable to detect /dev/sdc1, after the long list
of read errors below it ends up with only /dev/sdc.

Does this look like superblock issue, or something worse?

thanks,

raffaele

Beso wrote:
> before doing something on the disk first, read all and then take a
> decision on which options may help you. on my reiserfs filesystem, the
> included utils were enough to let me recover about 98% of the data after
> the full index rebuild. if you've journaled your filesystem, then i
> think that you should be able to recover it. also, it may only be a
> problem of superblock and in that case the second link might help you
> more. anyway, get a disk that can contain all the data that there was on
> the failed one, since you wouldn't want to do stuff on it to avoid loss
> of data.
> try reading this (the ext2/3 part):
> http://edseek.com/archives/2004/02/25/ext3-filesystem-bad-superblock-recovery/
> and this:
> http://forums.gentoo.org/viewtopic-t-569462-highlight-ext3+recover.html
> or you might try this utility:
> http://www.cgsecurity.org/wiki/PhotoRec
> 
> 2007/11/19, Raffaele BELARDI <raffaele.belardi@st.com
> <mailto:raffaele.belardi@st.com>>:
> 
>     Yesterday evening I had one 250Gb SATA disk Maxtor MaXLine Plus II fail.
>     The drive is formatted as ext3, single partition (sdc1), no RAID, used
>     as an archive of divx movies, completely full with data. Motherboard is
>     ASUS M2NPV-VM (Nvidia Nforce 430 chipset), I can easily mount it on an
>     ASUS K8V SE (Via K8T800 chipset) if it helps.
> 
>     At boot the syslog shows (more or less):
> 
>     I/O buffer read error: logical block 0
>     I/O buffer read error: logical block 1
> 
>     Any attempt to mount /dev/sdc1 results in tens of the above message
>     (plus other details I don't remember right now) and finally fails.
> 
>     fdisk -l shows the partition table as it should be.
> 
>     It was late night so I gave up. Are there any chances to recover my data
>     by e.g. specifying a different superblock (whatever that is)? Any links
>     to help me?
> 
>     thanks,
> 
>     raffaele
> 
>     PS I bought the drive in 2005 and I've used it only to archive movies,
>     so very little. It' the last Maxtor I buy (ok, also because it's Seagate
>     now..)
>     --
>     gentoo-amd64@gentoo.org <mailto:gentoo-amd64@gentoo.org> mailing list
> 
> 
> 
> 
> -- 
> dott. ing. beso
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-11-19 13:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 10:05 [gentoo-amd64] not amd64 specific - disk failure Raffaele BELARDI
2007-11-19 11:52 ` Beso
2007-11-19 13:27   ` Raffaele BELARDI [this message]
2007-11-19 13:56     ` Beso
2007-11-19 17:14     ` [gentoo-amd64] " Duncan
2007-11-20  7:47       ` Raffaele BELARDI
2007-11-20  9:01         ` Beso
2007-11-20 10:06           ` Raffaele BELARDI
2007-11-20  9:41         ` Duncan
2007-11-20 10:25           ` Raffaele BELARDI
2007-11-21  9:24         ` Raffaele BELARDI
2007-11-21 10:20           ` Raffaele BELARDI
2007-11-22  9:36             ` [gentoo-amd64] Re: not amd64 specific - disk failure - SUCCESS Raffaele BELARDI
2007-11-23 10:07               ` Duncan
2007-11-21 14:45           ` [gentoo-amd64] Re: not amd64 specific - disk failure Billy Holmes
2007-11-21 15:24             ` Raffaele BELARDI

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=47418F30.6050607@st.com \
    --to=raffaele.belardi@st.com \
    --cc=gentoo-amd64@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