need help

[Michael S]

I've tried both. fsck_ffs /dev/ad0s1a also exits because of bad superblocks.

On 3/17/06, Glenn Dawson <glenn at antimatter.net> wrote:
> At 09:46 PM 3/16/2006, Andrew Pantyukhin wrote:
> >On 3/17/06, Michael S <msherman77 at gmail.com> wrote:
> > > Hi.
> > >
> > > I am relatively new to FreeBSD, have been running it since 5.1.
> > > Nothing like what I experienced today had happened previously.
> > > My machine crashed and I wasn't able to boot it back, the boot
> > > processes wasn't able to find the kernel. I then booted with the 6.0
> > > Release CD and went into the FIXIT mode.
> > > I wasn't able to mount /dev/ad0s1a (I have an IDE drive), I then tried
> > > fsck_ffs /dev/ad0s1 and the message was:
> > > CAN'T READ BLCK 128
> > > ioctl Inappropriate ioctl for device
> > > fsck_ffs: /dev/ad0s1 can't read disk label.
> > >
> > > That machine was 6.0 p-1 (patched once) with slightly modified kernel.
> > >
> > > Is my data lost? Can anything be done still?
> > > Any help would be appreciated.
> > >
> > > Michael
> > > _______________________________________________
> > > freebsd-questions at freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe at freebsd.org"
> > >
> >
> >The bad news is that at least some data is lost and the
> >HDD is toast. You might also want to try and mount the
> >partitions read-only (this way they don't have to be clean).
> >Some data might still be accessible.
>
> I think he would have much greater success by fsck'ing /dev/ad0s1a
> instead of /dev/ad0s1.  (note the lack of an 'a' in the device name
> in the output above.
>
> -Glenn
>
> >_______________________________________________
> >freebsd-questions at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>