On Mon, Feb 12, 2007 at 08:14:28PM -0500, Marty Landman wrote:
On 2/12/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 04:48:44PM -0500, Marty Landman wrote:
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165
On Fri, Feb 09, 2007 at 04:48:44PM -0500, Marty Landman wrote:
On 2/9/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 12:06:20PM -0500, Marty Landman wrote:
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
On 2/12/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 04:48:44PM -0500, Marty Landman wrote:
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 490223412 (239366 Meg), flag 80 (active)
On 2/8/07, Pieter de Goeje [EMAIL PROTECTED] wrote:
If the slice and partition table are still intact (as they were before the
outage), a normal fsck -F on /dev/ad1s1a will get the pc booting again.
Well I managed to get the machine booting by editing /etc/fstab
%cat /etc/fstab
# Device
On Fri, Feb 09, 2007 at 07:46:10AM -0500, Marty Landman wrote:
On 2/8/07, Pieter de Goeje [EMAIL PROTECTED] wrote:
If the slice and partition table are still intact (as they were before the
outage), a normal fsck -F on /dev/ad1s1a will get the pc booting again.
Well I managed to get the
On 2/9/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 07:46:10AM -0500, Marty Landman wrote:
%sudo fsck -F ad1s1c
fsck: exec fsck_unused for /dev/ad1s1c in /sbin:/usr/sbin: No such file
or
directory
fsck: exec fsck_unused for /dev/ad1s1c in /sbin:/usr/sbin: No such
On Fri, Feb 09, 2007 at 12:06:20PM -0500, Marty Landman wrote:
On 2/9/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 07:46:10AM -0500, Marty Landman wrote:
%sudo fsck -F ad1s1c
fsck: exec fsck_unused for /dev/ad1s1c in /sbin:/usr/sbin: No such file
or
directory
On 2/9/07, Jerry McAllister [EMAIL PROTECTED] wrote:
On Fri, Feb 09, 2007 at 12:06:20PM -0500, Marty Landman wrote:
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 490223412 (239366 Meg), flag 80 (active)
On Thursday 08 February 2007 03:08, Marty Landman wrote:
On 2/7/07, Pieter de Goeje [EMAIL PROTECTED] wrote:
ad1s1c is a partition that contains the entire disk or slice in this
case. Dangerously dedicated is when you have no slices: ad1a, ad1b, ad1c
etc. You
should _only_ fsck the
On Wednesday 07 February 2007 03:06, Marty Landman wrote:
Jerry McAllister wrote:
Well, do as it says - choose a shell and run fsck manually.
Heh, for starters I assumed (always a bad thing) that fsck wasn't available
because I did a 'which fsck' and got 'which not found' as a response. But
On Tue, Feb 06, 2007 at 09:06:05PM -0500, Marty Landman wrote:
Jerry McAllister wrote:
Well, do as it says - choose a shell and run fsck manually.
Heh, for starters I assumed (always a bad thing) that fsck wasn't available
because I did a 'which fsck' and got 'which not found' as a
On 2007/02/06 17:06, Marty Landman seems to have typed:
Jerry McAllister wrote:
Just run /sbin/fsck /dev/ad1s1c. Actually that would be a somewhat
unusual address - what they call a 'dangerously dedicated' disk.
Can you explain or point me to more info on why that was a poor choice on my
On 2/7/07, Pieter de Goeje [EMAIL PROTECTED] wrote:
ad1s1c is a partition that contains the entire disk or slice in this case.
Dangerously dedicated is when you have no slices: ad1a, ad1b, ad1c etc.
You
should _only_ fsck the individual partitions (ad0s1a), never the complete
disk (ad0) or
My fbsd 6.0 box is having filesystem problems on boot since a blackout
yesterday. Here's a synopsis:
/dev/ad0s1a: clean
/dev/ad0s1d: DEFER FOR BACKGROUND CHECKING
...repeats for ad0s1f e
then reports error=40UNCORRECTABLE for ad1 (twice) and reports an
unexpected inconsistency for my ad1s1c
In response to Marty Landman [EMAIL PROTECTED]:
My fbsd 6.0 box is having filesystem problems on boot since a blackout
yesterday. Here's a synopsis:
/dev/ad0s1a: clean
/dev/ad0s1d: DEFER FOR BACKGROUND CHECKING
...repeats for ad0s1f e
then reports error=40UNCORRECTABLE for ad1 (twice)
On Tue, Feb 06, 2007 at 11:54:17AM -0500, Marty Landman wrote:
My fbsd 6.0 box is having filesystem problems on boot since a blackout
yesterday. Here's a synopsis:
/dev/ad0s1a: clean
/dev/ad0s1d: DEFER FOR BACKGROUND CHECKING
...repeats for ad0s1f e
then reports error=40UNCORRECTABLE for
Jerry McAllister wrote:
Well, do as it says - choose a shell and run fsck manually.
Heh, for starters I assumed (always a bad thing) that fsck wasn't available
because I did a 'which fsck' and got 'which not found' as a response. But
fsck itself is there.
Just run /sbin/fsck /dev/ad1s1c.
17 matches
Mail list logo
