Did you manage to solve the problem with the subject?
Just ha an almost similar problem and badly need your help??
The filesytem is ext3 and have done almost everything.
Regards,
Shepherd
___
freebsd-questions@freebsd.org mailing list
X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd4.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
On Wed, 18 Feb 2004 12:31:55 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
---
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Try
$ hd /dev/...| grep -A 5 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00
00
Well that definitely produced something:
bash-2.05b# hd /dev/ad2s1e | grep -A 5 02 00 00 00 0c 00 04 01 2e 00 00 00
02 00 00
002d 02 00 00 00 0c 00
On Thu, 19 Feb 2004 06:42:22 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Try
$ hd /dev/...| grep -A 5 02 00 00 00 0c 00 04 01 2e 00 00 00 02 00 00
00
Well that definitely produced something:
bash-2.05b#
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Here you should have answered `y' (it doesn't ask you to change
anything yet). Let's try that again, shall we?
Sorry, ok I went through it again, saying Y to all the Continue? prompts
but N to all the ones that talked about changing
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Sorry, you were recovering an 80G disk, and now you say the 80G has 4.9
on it. Did you erase anything? Is this a remote machine?
No, it was not the drive that had the OS on it. It was originally mounted as
/data on a system that had
On Tue, 3 Feb 2004 23:05:05 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Sorry, you were recovering an 80G disk, and now you say the 80G has 4.9
on it. Did you erase anything? Is this a remote machine?
No, it was
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Well, as it's UFS1 as we've figured out, the next logical thing would be
to try mounting /dev/ad2s1c r/o, and if that fails, try fscking it.
bash-2.05b# mount -r /dev/ad2s1c /data
mount: /dev/ad2s1c on /data: incorrect super block
On Wed, 4 Feb 2004 06:06:06 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Well, as it's UFS1 as we've figured out, the next logical thing would be
to try mounting /dev/ad2s1c r/o, and if that fails, try fscking it.
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
And /dev/ad2s1e?
bash-2.05b# mount -r /dev/ad2s1e /data
mount: /dev/ad2s1e on /data: incorrect super block
bash-2.05b# fsck /dev/ad2s1e
** /dev/ad2s1e
BAD SUPER BLOCK: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y
USING
On Wed, 4 Feb 2004 06:37:11 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
And /dev/ad2s1e?
bash-2.05b# mount -r /dev/ad2s1e /data
mount: /dev/ad2s1e on /data: incorrect super block
bash-2.05b# fsck /dev/ad2s1e
**
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Try using fsck -n (answer `no'), and recording what else comes up.
That won't work, because it answers no to the first question of looking for
alternate superblocks, then aborts immediately. So I'm just going to
manually say no to all
On Wed, 4 Feb 2004 08:26:47 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Try using fsck -n (answer `no'), and recording what else comes up.
That won't work, because it answers no to the first question of looking
Hello, gentlemen. For those of you still interested in this little
adventure, I now have the 80GB drive mounted on the 2nd IDE controller in
its own dedicated FreeBSD 4.9-RELEASE system.
ad0: 19092MB WDC WD200BB-75AUA1 [38792/16/63] at ata0-master UDMA100
ad2: 76345MB MAXTOR 6L080J4
On Tue, 3 Feb 2004 16:05:26 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
Hello, gentlemen. For those of you still interested in this little
adventure, I now have the 80GB drive mounted on the 2nd IDE controller in
its own dedicated FreeBSD 4.9-RELEASE system.
ad0: 19092MB
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I mean trying to mount it, to fsck it, using dd|hd to find the
superblock, etc. I just want to be *really* sure we know what
we are doing.
Well, I don't have experience making bootable FreeBSD floppies... it might
be more useful for me
On Tue, 6 Jan 2004 15:05, Sergey 'DoubleF' Zaharchenko wrote:
On Tue, 6 Jan 2004 13:29:26 +1030
Malcolm Kay [EMAIL PROTECTED] probably wrote:
On Tue, 6 Jan 2004 10:59, Scott I. Remick wrote:
Sorry for the delay... holidays had me busy.
Me too:)
Hopefully you're still around
and
On Tue, 6 Jan 2004 19:43:44 +1030
Malcolm Kay [EMAIL PROTECTED] probably wrote:
On Tue, 6 Jan 2004 15:05, Sergey 'DoubleF' Zaharchenko wrote:
On Tue, 6 Jan 2004 13:29:26 +1030
Malcolm Kay [EMAIL PROTECTED] probably wrote:
On Tue, 6 Jan 2004 10:59, Scott I. Remick wrote:
Sorry for
On Tue, 6 Jan 2004 19:57:09 +1030
Malcolm Kay [EMAIL PROTECTED] probably wrote:
On Tue, 6 Jan 2004 15:38, Scott I. Remick wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I wonder whether editing the label and setting both offsets to 0
might solve the problem.
It
--- Malcolm Kay [EMAIL PROTECTED] wrote:
Beware; if you write a disklabel (or presumably bsdlabel; I have no
experience
with 5.x) to ad6 you create a dangerously dedicated
disk, i.e. a disk without slices.
Ok. I am not saying that's what I want to do, I only mentioned it because
the man
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
And maybe prefix that by a
$ bsdlabel -R /dev/ad6s1c dislabel.ad6s1c.new
which would just check your new layout for errors, without writing
anything, and print your file out as disklabel understands it.
So you're saying, run it as
On Tue, 6 Jan 2004 06:31:08 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
And maybe prefix that by a
$ bsdlabel -R /dev/ad6s1c dislabel.ad6s1c.new
Sorry that was to be $ bsdlabel -R -n /dev/ad6s1c
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Sorry that was to be $ bsdlabel -R -n /dev/ad6s1c dislabel.ad6s1c.new :(
No worries... I figured it out :)
Indeed it's not like in 4.x, where they were the same. And what about
# ls -l /dev/ad6s1a /dev/ad6s1b
(these minor numbers
On Tue, 6 Jan 2004 08:32:31 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
I'm in the process of downloading the floppies...
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Sorry that was to be $ bsdlabel -R -n /dev/ad6s1c dislabel.ad6s1c.new :(
No worries... I
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I'm in the process of downloading the floppies...
ok cool
And what about ad4? Does disklabel show different values for the slice
and the `c' partition?
Hmm not only are they different as w/ ad6, but I get the same error on the c
On Tue, 6 Jan 2004 09:12:22 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I'm in the process of downloading the floppies...
ok cool
I can't find a zero-bad floppy in this place! It's all the holidays!
And what
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I can't find a zero-bad floppy in this place! It's all the holidays!
That's what AOL disks (vs. discs) used to be good for. :)
With `c', they're all offset by 63(why?). But still, you can mount the
partitions on the ad4s1, so the
On Tue, 6 Jan 2004 09:48:40 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I can't find a zero-bad floppy in this place! It's all the holidays!
That's what AOL disks (vs. discs) used to be good for. :)
With
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I can't find a zero-bad floppy in this place! It's all the holidays!
That's what AOL disks (vs. discs) used to be good for. :)
With `c', they're all offset by 63(why?). But still, you can mount the
partitions on the ad4s1,
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I think you already have a copy (the data at offset 32 seems to be it).
If you want, do a
# dd if=/dev/ad6s1 skip=16 count=16 of=/some/file
ok, done. Is there a way to use fsck_ufs -b now to fix this? Or is that
premature? And if I
--- Jerry McAllister [EMAIL PROTECTED] wrote:
(is disklabel/bsdlabel only meant to be run on slices and not
bsd-partitions?).
You have it backwards in this question. Disklabel is meant to run
only on bsd partitions and not slices. Slices (1-4) are the major
divisions of the disk
--- Jerry McAllister [EMAIL PROTECTED] wrote:
(is disklabel/bsdlabel only meant to be run on slices and not
bsd-partitions?).
You have it backwards in this question. Disklabel is meant to run
only on bsd partitions and not slices. Slices (1-4) are the major
divisions of
On Wed, 7 Jan 2004 06:09, Scott I. Remick wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I think you already have a copy (the data at offset 32 seems to be it).
If you want, do a
# dd if=/dev/ad6s1 skip=16 count=16 of=/some/file
ok, done. Is there a way to use fsck_ufs
--- Malcolm Kay [EMAIL PROTECTED] wrote:
This is true. That partition is labeled as unused.
I believe you should be trying to mount /dev/ad6s1e.
su-2.05b# mount -r /dev/ad6s1e /data
mount: /dev/ad6s1e on /data: incorrect super block
#/dev/ad6s1c/data ufs rw
On Tue, 6 Jan 2004 15:17:29 -0500 (EST)
Jerry McAllister [EMAIL PROTECTED] probably wrote:
--- Jerry McAllister [EMAIL PROTECTED] wrote:
(is disklabel/bsdlabel only meant to be run on slices and not
bsd-partitions?).
You have it backwards in this question. Disklabel is
On Tue, 6 Jan 2004 11:39:57 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I think you already have a copy (the data at offset 32 seems to be it).
If you want, do a
# dd if=/dev/ad6s1 skip=16 count=16
Sorry for the delay... holidays had me busy. Hopefully you're still around
and interested in picking up where we left off. I think we're definitely
onto something...
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
su-2.05b# hd /dev/ad6s1 | grep 54 19 01 00
1620 54 19 01 00 74
On Tue, 6 Jan 2004 10:59, Scott I. Remick wrote:
Sorry for the delay... holidays had me busy. Hopefully you're still around
and interested in picking up where we left off. I think we're definitely
onto something...
Looking back over some of your e-mails I find:
QUOTE
su-2.05b# disklabel -r
On Tue, 6 Jan 2004 13:29:26 +1030
Malcolm Kay [EMAIL PROTECTED] probably wrote:
On Tue, 6 Jan 2004 10:59, Scott I. Remick wrote:
Sorry for the delay... holidays had me busy.
Me too:)
Hopefully you're still around
and interested in picking up where we left off. I think we're definitely
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] 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
On Mon, 8 Dec 2003 21:52:54 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I wonder what did destroy it. Of course, system crashes can do wonders,
but...
Well, I was trying to save a file to that drive when my
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I wonder what did destroy it. Of course, system crashes can do wonders,
but...
Well, I was trying to save a file to that drive when my system spontaneously
rebooted for no apparent reason.
In fact, there should be a way, because a
On Thu, 4 Dec 2003 21:07:20 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I've got a (probably bad) idea. If you say that the partition was
mounted as /data, then you could do a
# hd /dev/ad6s1 |grep /data
On Thu, 4 Dec 2003 06:17:40 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
[so you want the list cc'd. good...]
Oh yes there are... what's surprising? If you are sure that the problem
is with the superblock, pick any
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
Oh yes there are... what's surprising? If you are sure that the problem
is with the superblock, pick any you wish.
The actual number of superblock copies depends on the disk size and the
parameters you give to newfs.
[...]
It's
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
If you want to be more sure, try dd'ing your (suspectedly damaged)
superblock and some of its (suspectedly OK) copies into different files:
# dd if=/dev/ad6s1e skip=... bs=512 count=16 of=somefile
As /usr/src/sys/ufs/ffs/fs.h
On Thu, 4 Dec 2003 08:24:16 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
If you want to be more sure, try dd'ing your (suspectedly damaged)
superblock and some of its (suspectedly OK) copies into different files:
On Thu, 4 Dec 2003 08:24:16 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] probably wrote:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
If you want to be more sure, try dd'ing your (suspectedly damaged)
superblock and some of its (suspectedly OK) copies into different files:
--- Sergey 'DoubleF' Zaharchenko [EMAIL PROTECTED] wrote:
I've got a (probably bad) idea. If you say that the partition was
mounted as /data, then you could do a
# hd /dev/ad6s1 |grep /data
It should come up soon (the superblock should be close to the beginning
of the drive, right?).
Running 5.1-REL on a system w/ 2 drives. Was saving a file to 2nd drive
(mounts as /data) and system suddenly froze then rebooted. Never good. Fsck
barfed on startup telling me I had to run it manually. The error I'm stuck
with is:
/dev/ad6s1c
Cannot find file system superblock
/dev/ad6s1c: NOT
On Wed, 3 Dec 2003 00:06:12 -0800 (PST)
Scott I. Remick [EMAIL PROTECTED] wrote:
Running 5.1-REL on a system w/ 2 drives. Was saving a file to 2nd drive
(mounts as /data) and system suddenly froze then rebooted. Never good. Fsck
barfed on startup telling me I had to run it manually. The error
--- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote:
FSCK_FFS(8)
NAME
fsck_ffs, fsck_ufs -- file system consistency check and interactive
repair
SYNOPSIS
fsck_ffs [-BFpfny] [-b block#] [-c level] [-m mode] filesystem ...
-b Use the block specified immediately after the
52 matches
Mail list logo
