Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Jan 2004 21:08:27 -0800 (PST)
From:      "Scott I. Remick" <scott@sremick.net>
To:        Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru>, Malcolm Kay <malcolm.kay@internode.on.net>
Cc:        FreeBSD <freebsd-questions@freebsd.org>
Subject:   Re: "Cannot find file system superblock" error - how to recover?
Message-ID:  <20040106050827.95860.qmail@web41101.mail.yahoo.com>
In-Reply-To: <20040106073519.54620420.doublef@tele-kom.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

--- Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> wrote:
> > I wonder whether editing the label and setting both offsets to 0
> > might solve the problem.
> 
> It definitely seems like that, as the actual offset of the partition is
> 0, as dd shows.

Ok, sounds like a plan. Not that I know what I'm doing. Should I use
something like the following command to save my current disklabel?

bsdlabel /dev/ad6s1c > disklabel.ad6s1c.backup

Then do I just edit a copy of that textfile, change the offsets to 0, then
write it back like this?

bsdlabel -R /dev/ad6s1c dislabel.ad6s1c.new

And lastly... your talk about offsets. The man page for bsdlabel describes
using it on the whole disk (ad6) and not a slice or partition. If I run it
on  ad6, I get:

bsdlabel: /dev/ad6: no valid label found

If I run it on the slice ad6s1 I get:

# /dev/ad6s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 156344517        0    unused        0     0         # "raw" part, don't
edit
  e: 156344517        0    4.2BSD     2048 16384    89

And there I see the offset of 0 you might be talking about...? Are we
looking at the proper label? Just want to make sure before I mess things up.

Thanks!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040106050827.95860.qmail>