DragonFlyBSD

Why are you installing from one USB stick to another? The original image is
bootable. You can copy the initial image onto both. I realize that's not
the original task you were trying to do, but it would have less problems.

On Sun, Oct 16, 2011 at 6:51 PM, Juan Francisco Cantero Hurtado (via
DragonFly issue tracker) <sinknull@leaf.dragonflybsd.org> wrote:

New submission from Juan Francisco Cantero Hurtado <iam@juanfra.info>:

Steps for reproduce:
- Download the last usb image from the mirrors.
- dd to your usb stick.
- Power off your computer.
- Conect two usb sticks to your computer. The first with the installer of
DragonFly. The seconds will be the destination of your installation.
- Boot the installer.
- Install DragonFly in your second usb stick. Use all the disk and hammer.
- Power off your computer.
- Disconnect the first usb stick.
- Power on your computer.
- Boot your usb stick.
- DragonFly doesn't find your root partition.

The old (usb) disk "da9x" is "da8x" now. Here exists two problems:
- In /etc/fstab the partitions point to "da9x".
- The same for /boot/loader.conf.

The installation in usb disks is useless. With this problem the user can't
use
his or her usb disk in other computers with other order of usb disks. Also
this
is very bad for IT departments.

I think the better solution is the support for UUID.

The same problem for other user:
- http://leaf.dragonflybsd.org/mailarchive/users/2011-09/msg00024.html

----------
keyword: HAMMER, boot/loader, installer
messages: 10202
nosy: juanfra684
priority: bug
status: unread
title: DragonFly doesn't boot from usb stick

_____________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue2151>
_____________________________________________

On Sun, Oct 16, 2011 at 11:29:27PM +0000, Justin C. Sherrill (via DragonFly issue tracker) wrote:

Why are you installing from one USB stick to another? The original image is
bootable. You can copy the initial image onto both. I realize that's not
the original task you were trying to do, but it would have less problems.

I know. I was only testing the speed of my usb stick with hammer and
I discovered the bug. My steps are only a example :)

Some users install the operating systems in usb disks and they will
have this problem. No only a bootable OS like in the usb images, I mean
people with a real systems (tens of GB) in usb disks.

SATA, IDE and SCSI disks have a unique identifier, the serial number.
The USB disks need also a unique identifier.

This is only going to bite people installing from one USB stick to another.
USB-connected drives wouldn't be affected, because they report an actual
serial number from the disk; it's just USB sticks that often do not, since
they are cheap. I may be missing the correct scenario here, but it appears
what you are describing is not likely to happen.

On Sun, Oct 16, 2011 at 10:36 PM, Juan Francisco Cantero Hurtado <
iam@juanfra.info> wrote:

On Sun, Oct 16, 2011 at 11:29:27PM +0000, Justin C. Sherrill (via DragonFly
issue tracker) wrote:

Why are you installing from one USB stick to another? The original image

is

bootable. You can copy the initial image onto both. I realize that's

not

the original task you were trying to do, but it would have less problems.

I know. I was only testing the speed of my usb stick with hammer and
I discovered the bug. My steps are only a example :)

Some users install the operating systems in usb disks and they will
have this problem. No only a bootable OS like in the usb images, I mean
people with a real systems (tens of GB) in usb disks.

SATA, IDE and SCSI disks have a unique identifier, the serial number.
The USB disks need also a unique identifier.

I've tried with a usb disk. You're correct about that. Sorry.

So, the problem only affect to usb sticks with hammer. I don't know if the bug
exists also for the usb sticks with UFS.

On Mon, 17 Oct 2011 22:41:01 +0200, Juan Francisco Cantero Hurtado (via
DragonFly issue tracker) <sinknull@leaf.dragonflybsd.org> wrote:

Juan Francisco Cantero Hurtado <iam@juanfra.info> added the comment:

I've tried with a usb disk. You're correct about that. Sorry.

So, the problem only affect to usb sticks with hammer. I don't know if
the bug
exists also for the usb sticks with UFS.

It has nothing to do with the file system you chose in the installer.

If it was installed to a device that is named differently during
installation vs. booting, it will break sooner or later when trying to
mount.

Sascha

On Mon, Oct 17, 2011 at 09:41:35PM +0000, Sascha Wildner (via DragonFly issue tracker) wrote:

Sascha Wildner <saw@online.de> added the comment:

On Mon, 17 Oct 2011 22:41:01 +0200, Juan Francisco Cantero Hurtado (via
DragonFly issue tracker) <sinknull@leaf.dragonflybsd.org> wrote:

Juan Francisco Cantero Hurtado <iam@juanfra.info> added the comment:

I've tried with a usb disk. You're correct about that. Sorry.

So, the problem only affect to usb sticks with hammer. I don't know if
the bug
exists also for the usb sticks with UFS.

It has nothing to do with the file system you chose in the installer.

If it was installed to a device that is named differently during
installation vs. booting, it will break sooner or later when trying to
mount.

I can't look this now but hammer uses a entry in loader.conf. My comment
is because I don't know if UFS uses a similar behavior for loader.conf.
I guess no, but all my systems have hammer so I'm not sure.

And yes, the problem in fstab is for all types of FS.

I've had now other problem. I use a usb disk for daily backups of my Linux system
in my box. The usb disk is always connected. With the last usb image I can't boot
if I also have the usb disk connected.