From: metaverse <metaverse@artikel-140.nl>
To: xfs@oss.sgi.com
Subject: Create superblock
Date: Thu, 19 Jun 2014 23:47:13 -0700 (PDT) [thread overview]
Message-ID: <1403246832932-35023.post@n7.nabble.com> (raw)
Last week a harddrive in a NAS crashed in our office. Long story short: We
have been trying everything. In the end we where able to pull an image of
the hard drive. Also we found out there's no superblock or secondary blocks.
Since I have recovered successfully the data I was wondering if it was
possible to create a new superblock and secondary block. If not I'll create
a new partition and place all the data back.
Scary that only a power outage can do this...
TL;DR: Is it possible to create a new superblock from scratch?
--
View this message in context: http://xfs.9218.n7.nabble.com/Create-superblock-tp35023.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-06-20 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 6:47 metaverse [this message]
2014-06-20 14:27 ` Create superblock Eric Sandeen
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=1403246832932-35023.post@n7.nabble.com \
--to=metaverse@artikel-140.nl \
--cc=xfs@oss.sgi.com \
/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