On Sat, 4 Jun 2011, claudiu vasadi wrote:
Try booting into single user mode and then:
# mount -u /
# tunefs -L root /dev/ad6s1a
# reboot
Single user yes, but don't remount the filesystem. Just label it and
reboot.
___
freebsd-questions@freebsd.or
Try booting into single user mode and then:
# mount -u /
# tunefs -L root /dev/ad6s1a
# reboot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-
On 4/6/11 3:09 PM, Warren Block wrote:
On Sat, 4 Jun 2011, Erik Nørgaard wrote:
Thanks, I tried to add labels, and all file systems are labeled,
except the root file system, it gives an error
alpha# tunefs -L root /dev/ad6s1a
tunefs: /dev/ad6s1a: failed to write superblock
The filesystem has
On Sat, 4 Jun 2011, Erik Nørgaard wrote:
On 4/6/11 10:48 AM, Polytropon wrote:
On Sat, 04 Jun 2011 10:31:18 +0200, Erik Nørgaard
wrote:
The first problem is that I have no idea how my disk will be recognized,
now the root partition is on /dev/ad6s1a.
A good approach is to apply a label or us
On Sat, 4 Jun 2011 10:48:12 +0200
Polytropon wrote:
> On Sat, 04 Jun 2011 10:31:18 +0200, Erik Nørgaard
> wrote:
> > The first problem is that I have no idea how my disk will be
> > recognized, now the root partition is on /dev/ad6s1a.
>
> A good approach is to apply a label or use the UFSID of
On Sat, 04 Jun 2011 11:12:28 +0200, Erik Nørgaard wrote:
> Thanks, I tried to add labels, and all file systems are labeled, except
> the root file system, it gives an error
>
> alpha# tunefs -L root /dev/ad6s1a
> tunefs: /dev/ad6s1a: failed to write superblock
>
> Can I use the fsid in fstab?
>
On 4/6/11 10:48 AM, Polytropon wrote:
On Sat, 04 Jun 2011 10:31:18 +0200, Erik Nørgaard wrote:
The first problem is that I have no idea how my disk will be recognized,
now the root partition is on /dev/ad6s1a.
A good approach is to apply a label or use the UFSID of
the partitions (which don't
On Sat, 04 Jun 2011 10:31:18 +0200, Erik Nørgaard wrote:
> The first problem is that I have no idea how my disk will be recognized,
> now the root partition is on /dev/ad6s1a.
A good approach is to apply a label or use the UFSID of
the partitions (which don't depend on controller position)
inste
Hi:
I'm moving my server to new hardware, but I will preserve the disk
making the necessary changes to the configuration before the move.
The first problem is that I have no idea how my disk will be recognized,
now the root partition is on /dev/ad6s1a.
The second problem is that the server