From: Richard Waterbeek <richardwbb@versatel.nl>
To: linux-xfs@vger.kernel.org
Subject: non mountable xfs with 2 primary and 2 logical
Date: Wed, 28 Jun 2017 21:43:25 +0000 [thread overview]
Message-ID: <1498686205.13847.1.camel@versatel.nl> (raw)
Hi linux-xfs mailinglist,
I've recently subscribed to this list. I've seen many messages, but have
little understading of the 'XFS' file system. I know about mkfs.xfs.
I've benched my hardware. But, now my harddrive had a collision with the
mbr somehow. [or something]
But, now I've 'hexdumped', the first 512 bytes, [because after a
disaterous reboot, cfdisk is now saying; "/dev/sda empty".
I'm aware of two primary and two logical partitions. I feel that I know
the size of the first and second primary, but the xfs/ sda5 and, xfs
sda6, are no longer appearing. I had to '#' the /etc/fstab, because it
won't boot [long waiting].
Now I would like to restore the first 512 bytes which is the MBR.
I have absolutely no understanding of -where-, "the SuperBlock" [or how
that should be called], happens to be.
But, I feel that 512 bytes missing and no reason to believe a whole
Terabyte would be "ones and/ or zero's", now, I wonder, how to restore
this. I have not made backup of this harddrive, just an rsync, which is
a little outdated and a bit incomplete, because difference in size of
both drives.
I might be able to create a XFS-something [from /dev/sda, for example],
and write that with dd.
But, before I would 'try this out', I would like to gain some
understanding, of what -should- be on the first 512 bytes of a
harddrive, besides what I have now, cfdisk is saying empty.
Hoping to receive a reply, Richard, the Netherlands
next reply other threads:[~2017-06-28 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 21:43 Richard Waterbeek [this message]
2017-06-28 21:52 ` non mountable xfs with 2 primary and 2 logical Eric Sandeen
2017-07-12 12:22 ` Richard Waterbeek
2017-07-12 11:06 ` Brian Foster
2017-07-14 19:31 ` Richard Waterbeek
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=1498686205.13847.1.camel@versatel.nl \
--to=richardwbb@versatel.nl \
--cc=linux-xfs@vger.kernel.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