[wellylug] File recovery after a crash.

[Nathan Cook]

Have you tried running a tool over the hard drive to find any errors, other
than fsck.

As recommended in another topic Ultimate Boot CD will scan your drive with
the manufacturers tools and detect any errors, among other things...

If there are errors we can cross that bridge then.

Regards
Nathan


On Sat, Sep 26, 2009 at 6:50 AM, MDM Productions <thefrasers at clear.net.nz>wrote:

> Jonathan Harker wrote:
> > MDM Productions wrote:
> >
> >> Xav: All the other drives are there, and all have UUID's except for
> >> hda6.  Will that be restored automagically once we get the show on the
> road?
> >>
> >
> > UUIDs are optional. Their only advantage is if you introduce another
> > hard disk, and your Linux kernel decides to shift what used to be your
> > /dev/sda to /dev/sdb or something, and your /dev/sda6 partition becomes
> > /dev/sdb6 which fouls up your /etc/fstab. Using UUIDs instead would
> > prevent that from happening.
> >
> > Depending on your distribution (I think you said Mandriva?) you should
> > be able to see which UUIDs correspond to which devices:
> >
> > ls -l /dev/disk/by-uuid
> >
> > For instance, mine says:
> >
> > bda665d9-eb5e-49c2-9ad4-dd9359eb5778 -> ../../sda1
> > 06B89BA8B89B9531 -> ../../sdb1
> > D0CC7172CC715426 -> ../../sdb5
> > 0277438a-55fa-4fa4-aa5d-80f2e1e08ef0 -> ../../sdb6
> > 06305be6-cafa-449e-b3cb-c79806f76996 -> ../../sdb7
> > 130d8080-5895-4014-88ed-7d8ce139c8d3 -> ../../sdb8
> > 3a18306b-aeee-4933-b137-b14f81bb6fcd -> ../../sdc1
> >
> > I'm using Ubuntu though, so you might have to poke around a bit, not
> > sure if that's a Debian-specific arrangement.
> >
> > Anyway
> >
> > Does the message output say anything about why it is dropping you into a
> > maintenance shell? Is it because the timestamp is wrong? I got this once
> > because it detected the date it was last mounted was "in the future"
> > because of the way Windows and Linux were dual-booting, and one was
> > treating the system clock as GMT, the other as NZST.
> >
> > HTH
> > J
> >
> >
> >
> Dear All,
>
> To clear up a couple of things, the OS,  _/single booting,/_ is PCLOS. I
> had it set up to suspend to disk on lid close which it would do reliably
> about half the time in that it might not wake. I hadn't stopped it doing
> suspend despite best intentions (I just hadn't, OK?) and despite being
> careful about this it might well have been writing something when I shut
> the lid enough to trigger the switch. I believe I had closed out and was
> putting it away and might have just shut the lid a moment too soon.
> What I get on start is now the verbose parade ticking off down to
> Remounting root file system in read-write mode OK, then Invalidating
> stale software suspend images...done, then Checking file systems, then
> fsck.ext3: Unable to resolve 'UUID=454f....etc etc' , then /dev/hda6:
> recovering journal, then /dev/hda6: clean, 4416/13123584 files
> 1629111/26236145 blocks [FAILED] and the drop to shell after ***An error
> occurred... etc.
> Has any of this helped explain further?
> Thanks people.
>
>
> --
> Wellington Linux Users Group Mailing List: wellylug at lists.wellylug.org.nz
> To Leave:  http://lists.wellylug.org.nz/mailman/listinfo/wellylug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wellylug.org.nz/pipermail/wellylug/attachments/20090926/5f244b65/attachment-0001.htm