Hej Marcel,
On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com
wrote:
Yes, if you have ad2a and not ad2s1a, then you have a
proper dangerously dedicated disk and FreeBSD 8.x will
work correctly with your disk.
If you installed dangerously dedicated and ended up
with
on 16/12/2009 11:28 Marian Hettwer said the following:
Hej Marcel,
On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com
wrote:
Yes, if you have ad2a and not ad2s1a, then you have a
proper dangerously dedicated disk and FreeBSD 8.x will
work correctly with your disk.
If
If you installed dangerously dedicated and ended up
with ad0s1a (note the s1), then you have an invalid
partitioning and FreeBSD 8.x will not give you what
you've been getting on FreeBSD 7.x. Most of the time
you only need to wipe out the second sector on the
disk to clean it up and have
Hej Ho,
On Wed, 16 Dec 2009 12:55:38 +0200, Andriy Gapon a...@icyb.net.ua wrote:
on 16/12/2009 11:28 Marian Hettwer said the following:
Hej Marcel,
On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com
wrote:
Yes, if you have ad2a and not ad2s1a, then you have a
proper
Quoth sth...@nethelp.no:
If you installed dangerously dedicated and ended up
with ad0s1a (note the s1), then you have an invalid
partitioning and FreeBSD 8.x will not give you what
you've been getting on FreeBSD 7.x. Most of the time
you only need to wipe out the second sector on the
If you installed dangerously dedicated and ended up
with ad0s1a (note the s1), then you have an invalid
partitioning and FreeBSD 8.x will not give you what
you've been getting on FreeBSD 7.x. Most of the time
you only need to wipe out the second sector on the
disk to clean it up
On Wed, Dec 16, 2009 at 12:27:15PM +0100, Marian Hettwer wrote:
but, hm, whats that?
r...@talisker:/root# fsck /dev/ad8s1a
fsck: Could not determine filesystem type
If you don't have an entry for /dev/ad8s1a in your fstab, you need to
specify the filesystem type with -t.
Jeff
On Dec 16, 2009, at 3:27 AM, Marian Hettwer wrote:
gee, thanks!
That worked.
r...@talisker:/root# ls /dev/ad8*
/dev/ad8/dev/ad8s1 /dev/ad8s1a
r...@talisker:/root# mount /dev/ad8s1a /BACKUP/
r...@talisker:/root# umount /BACKUP/
but, hm, whats that?
r...@talisker:/root# fsck
On Dec 16, 2009, at 2:33 AM, sth...@nethelp.no wrote:
If you installed dangerously dedicated and ended up
with ad0s1a (note the s1), then you have an invalid
partitioning and FreeBSD 8.x will not give you what
you've been getting on FreeBSD 7.x. Most of the time
you only need to wipe out
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 16, 2009, at 3:27 AM, Marian Hettwer wrote:
gee, thanks!
That worked.
r...@talisker:/root# ls /dev/ad8*
/dev/ad8/dev/ad8s1 /dev/ad8s1a
r...@talisker:/root# mount /dev/ad8s1a /BACKUP/
r...@talisker:/root# umount /BACKUP/
Quoth sth...@nethelp.no:
So what's an easy recipe we can run on 7.x hosts to see whether we
would have problems with 8.x?
From what's been said so far: If you have adXsY devices in 7, *and*
bsdlabel adX
finds a valid label (*note*: that is the whole disk, not the
Hi Folks,
today I did an update from 7.2-RELEASE-p4 to 8.0-RELEASE using
freebsd-update.
Everything went smooth, apart from the fact that I can't mount my second
disk.
It's all a bit puzzling...
Here are the facts:
[r...@talisker ~]# cat /etc/fstab
# DeviceMountpointFStype
On Tuesday 15 December 2009 04:42:06 pm Marian Hettwer wrote:
Hi Folks,
today I did an update from 7.2-RELEASE-p4 to 8.0-RELEASE using
freebsd-update.
Everything went smooth, apart from the fact that I can't mount my second
disk.
It's all a bit puzzling...
Here are the facts:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously dedicated disk, as demonstrated by doing:
# fdisk ad8
(shows FreeBSD slice
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously dedicated disk, as demonstrated by doing:
# fdisk
On Tue, Dec 15, 2009 at 4:08 PM, Ben Morrow b...@morrow.me.uk wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
On Dec 15, 2009, at 4:08 PM, Ben Morrow wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously
Quoth Xin LI delp...@gmail.com:
On Tue, Dec 15, 2009 at 4:08 PM, Ben Morrow b...@morrow.me.uk wrote:
Are you able to clarify exactly what is no longer working in 8? I've
read things here and there about dangerously dedicated disks no longer
being supported, but no detail about what
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 4:08 PM, Ben Morrow wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that
On Wed, 16 Dec 2009, Xin LI wrote:
My $0.02: what about labelling them, say, tunefs -L on UFS
partitions, and glabel for swap, then change corresponding entry in
fstab. Say:
- Start into single user
- tunefs -L root /
- reboot into single user --- reboot required after tuning /
-
20 matches
Mail list logo
