Thomas Exner wrote:
> when running fsck the first error message is "ROOT INODE UNALLOCATED"
> ...
> Is there a chance to get the data back?
Dunno about current versions, but IIRC some earlier versions of
dump(8) could handle even a badly-corrupted FS. No harm in trying,
since it will not try to
> huff@>> newfs /dev/da3a
> /dev/da3a: 78167.2MB (160086512 sectors) block size 16384, fragment size 2048
> using 426 cylinder groups of 183.77MB, 11761 blks, 23552 inodes.
> super-block backups (for fsck -b #) at:
> 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976
Roland Smith writes:
> > huff@>> fsck /dev/da3a
> > ** /dev/da3a
> > ** Last Mounted on /backup
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ROOT INODE UNALLOCATED
> > ALLOCATE? [yn]
> >
> >a) what's probably happened?
>
> Error messages are expla
On Fri, 6 Feb 2009 14:48:41 -0500, Robert Huff wrote:
>
> Had a power outage recently; when trying to fsck several
> external hard drives I'm getting unexpected errors.
> For example:
>
> huff@>> fsck /dev/da3a
> ** /dev/da3a
> ** Last Mounted on /backup
> ** Phase 1 - Check Blocks a
On Fri, Feb 06, 2009 at 02:48:41PM -0500, Robert Huff wrote:
>
> Had a power outage recently; when trying to fsck several
> external hard drives I'm getting unexpected errors.
> For example:
>
> huff@>> fsck /dev/da3a
> ** /dev/da3a
> ** Last Mounted on /backup
> ** Phase 1 - Check Bl
with a subject this time...
I've used /usr/ports/sysutils/testdisk to recover my BSD partitions, but
it was just a HD failure/MBR nukage, no newfs was run on it - Try that.
]Peter[
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.o
From professional experience as a data recovery technician, I can tell
you that ufs2 drives are among the hardest to recover from after a
there is a little change as UFS2 use lazy inode initialization. so
possibly lots can be recovered. but i don't know any soft that does it.
moving disks from an old server to a new one I suffered from a moment of
brain fade last night and newfs'ed a drive I shouldn't have. One of that
new crop that is so large you won't have an adequate backup for it... :(
no rescue. newfs overwrote inodes that contained your files metadata.
__
>From professional experience as a data recovery technician, I can tell
you that ufs2 drives are among the hardest to recover from after a
format. So far the best applications that I have found for recovering
data in a situation like this are testdisk and Easy Recovery
Professional (by Kroll Ontra
Hi,
> Hi,
>
> I have a personal server with 400Gb of hard disks in various shapes and
> sizes. I don't have enough money for redundant disks, and I would like
> to know what the most efficient way of making sure my data doesn't get
> lost, in case of a hard drive failure. The best would be for
I used to think just like you. I thought I found the perfect balance
between being on a budget and still having some kind of data security
by using the Vinum software raid.
So I stored the first 10 hours of video and 4k of still shots of my
newly borned first child on the raid, and everything went
Even considering repairing an damaged HD as an method to replace
backups is an stupid thought. People who do not backup critical data
are fools. There is no price tag one can put on critical data. You
find some way to backup to flat compressed file format and write to
an removable HD or CDROM or so
John Oxley wrote:
Hi,
I have a personal server with 400Gb of hard disks in various shapes and
sizes. I don't have enough money for redundant disks, and I would like
to know what the most efficient way of making sure my data doesn't get
lost, in case of a hard drive failure. The best would be for
13 matches
Mail list logo
