Mounting from cd9660 failed with error 19

10.2, v9 both fail boot: mount failed with error code 19

newtoFreeBSD

Hello, I would love to start my FreeBSD experience (I’ve heard Mac OSX is based on it, and it has _very_ good security features, plus the screenshots online look great!!)

But, unfortunately I cannot get it to install. I started at 8am, and now it is 1:30am, and I just can’t get the thing to boot from dvd1 or disk1.

Unfortunately, I can’t download anything other than dvd1 or disk1.

Here are my system specs:

z97 motherboard chipset
Intel i3 4-core HD graphics integrated chipset
Corsair Ballistix 1660Hz 16GB (2x8GB) mem
2TB standard internal desktop HDD — plugged into SATA2 on motherboard
CD/DVD Combo drive — plugged into SATA1 on motherboard

I tried all the suggestions from other users having similar problems with versions FreeBSD 9x; namely, I tried turning ACPI support off, then turning off ACPI support and turning on Safe Mode, and then turning off ACPI support and turning on safe mode and single user mode. None of those worked with either v 10.2 or v 9+.

I then tried manually mounting, but none of the suggested mounts worked, and I also tried the following mount:

That also failed to mount with error code 19.

Am I just re***ded or something? I mean, I must be a really, really stupid user if I can’t even get an install CD to boot into a simple DOS-like install prompt.

Sorry, it’s just I’ve been at this exact same error about 20 times now, the first time I waited on auto boot for the first 6 hours of the installation process while it tried the same command over and over when it failed, over, and over, and since it would just run to infinity, I thought I would try some of the other users’ options instead.

Anyway, it’s just I’m pretty frustrated that my first experience with FreeBSD makes me feel like an id*** box. I’ve been at this since 8 yesterday to 2 am this morning.

I guess I could always install Windows 10, but man — FreeBSD IS the Mac OSX, according to a bunch of people, and the government uses it because of its tight security. Surely I can at least install it!

Maybe I should go to the jungle and hump an ape on a full moon?

Rubel

Terry_Kennedy

That’s a bug with a specific virtual CD implementation. I wouldn’t expect to see an error 19 on any «real» hardware — it generally shows up when the BIOS has various tricks (like INT 13 emulation) to make a device bootable. But the minute the FreeBSD kernel (or any other operating system) loads and takes control, the BIOS is no longer managing the device and the kernel gets confused because it was told it booted from a device that no longer exists.

What do you see when you type «?» at:

Reactions: acheron and protocelt

UnixRocks

Quite frustrating and disheartening. Have tried with a DVD and CD in the physical drive as well as all three ISO images (FreeBSD-10.0-RELEASE-amd64-bootonly.iso, FreeBSD-10.0-RELEASE-amd64-disc1.iso, FreeBSD-10.0-RELEASE-amd64-dvd1.iso) connected with ISO Device Redirection on the RMMI window. Every one of these fails eventually with the «error 19» message. What is worse I get a hard hang once I see the «mountroot>» prompt and no amount of key presses or waiting sees any response. I was going to try a USB stick with the FreeBSD-10.0-RELEASE-amd64-memstick.img next. But after reading this thread I am losing hope that we will be able to use FreeBSD on these new servers. I really want to use FreeBSD instead of CentOS on these . so if anyone has another option that might work, please pipe up.

FYI, I had the 10.0 ISO files on hand. If 10.2 will work better, I will gladly try it.

UnixRocks

sstanley

That’s a bug with a specific virtual CD implementation. I wouldn’t expect to see an error 19 on any «real» hardware — it generally shows up when the BIOS has various tricks (like INT 13 emulation) to make a device bootable. But the minute the FreeBSD kernel (or any other operating system) loads and takes control, the BIOS is no longer managing the device and the kernel gets confused because it was told it booted from a device that no longer exists.

What do you see when you type «?» at:

I have same problem on HP EliteBook 2710p + docking station.

NO, this is not only virtual, real hardware problem.
In details — broken ISO — hosted or wrong downloaded(changed a bit). ISO dated @08-19-2015 disc1 (i386, AMD64) and even dvd version always same error. 3 iso’s, all downloaded from freebsd official ftp az .xz files at @09 January 2016
All successfuly unpacked by 7zip 15.10 on Windows machine.
99.99% problem was made on host site.

FreeBSD 11 28 November 2015 works on virtualbox
Seems that ^^ (post above) memstick image for 10.2 also works.

In my case: When i type «?» command on elitebook i see /dev/iso9660/. _AMD64_DVD cd0 (instead acd0) and my current ntfs harddisk(Windows 10). After escape to sh there is /dev/iso9660/10_2_. I can mount it, mount -t cd9660 /dev/iso.. and ls shows the files. But i don’t know what to do next.

I think it doesn’t matter because attempt on HP s7600 series loads crashes. Same thing on HP T3000 (ata cdrom), it crashes(turns off PC) 1 second after kernel mounts iso image. It also crashes VirtualBox attempt, it even runs up the installer, except for the step after choosing keyboard. Then VB shows «unrecoverable error OK/Ignore». Game Over.

sstanley

After error appeared i’ve wrote mountroot>cd9600:/dev/acd0 ro and medium was discovered properly as cd-rom started spin up. Despite it’s even not tried to read yet, error 19 came out just in second. With older version with old boot loader with damaged data layer got same error 19, after some time, but system at least tried to read a lot until error.

All FreeNAS, FreeBSD’s since 10.2, PCBSD since 10.3 all images uses BTX CD Loader. For all BTX based got same «error 19». Older ones worked. In theory it’s an error reading of medium. But according to DVD behavior — BTX wouln’t even give a bit of chance drive to read because it’s not even starting to spin up enough. USB stick is workaround to this problem but not ultimate — need to be fast. For me it works run ISO in VirtualBox, worked on USB stick bare hardware but not on DVD. And for some people even USB stick speed wasnt enought.

Solution worked also 10.3. Increase delay to 30s so DVD will have more time to spin up. On the BTX loader menu Select 3: Escape to loader prompt and write those 2 lines:
set kern.cam.boot_delay=»30000″
boot
and hit Enter!

Already tested. worked

Confirmed still an issue with VirtualBox under macOS and 11.1-RELEASE as of May, 2018, using ICH6 virtual controller.

The above work-around does not work in this case.

Suggested workaround for VirtualBox is to mount the CD image on a SATA controller.

Источник

Solved Installing 9.0-RELEASE: Mounting DVD failed with error 19

Z0vsky

This is my first post in an English-speaking [Free]BSD community and I’m really excited and happy to join it
I’d have loved to start with a more positive post, but unfortunately this one has to deal with an installation issue.

Context:
I’ve just got a new dedicated server (my first one), ordered from a French hosting provider that doesn’t offer any FreeBSD installation services (I don’t mind, I prefer to do things myself). I gave them a link so they can download the installation ISO file, burn it and put it in a DVD drive that would be plugged to the server.
I now have a KVM over IP access so I can proceed with the installation.

For your information, the target machine is a dedicated server with:

• Intel Xeon 3000
• 4GB of RAM
• 250 GB hard-drive

I chose to install the FreeBSD 9.0-RELEASE amd64 version as I wanted to try out the new BSDInstall. I gave the hosting provider the link to download the FreeBSD-9.0-RELEASE-amd64-dvd1.iso file.

Issue:
Here is the error message that I’ve got:

The system seems to recognize the DVD drive but is unable to mount the media correctly.

Ideas & link (so far):
I’ve done some research and this problem is relatively common with the 9.0-RELEASE:

• [Solved]Install FreeBSD 9.0 rc1 from USB Flash
• [Solved]Corrupted FreeBSD install prevents re-install CD or USB key seeing drives
• [Solved]New install of v9.0 fails
• FreeBSD 9 installation wont start(error 22)

In these threads, most people are having this issue during an upgrade. They can troubleshoot using their currently installed system. I can’t.

Some folks suggest to use the disc1.iso or the bootonly.iso or even some but as I said I don’t have physical access to the server. It doesn’t seem to solve the problem everytime. Moreover, I can only ask the provider to burn an ISO, put it in a DVD drive and plug it to the server. Each time I’d asked them to do such an action, I’d been charged with installation fees so I cannot easily try anything without been pretty sure of the result before.

So I posted here to see if you may have some ideas or suggestions. I’ll keep investigating.

Источник

New install of v9.0 fails

Absolon

I’m trying to do a fresh install on a new computer with the DVD ISO. I’m using a USB DVD and have tried with two different ones, but I get the same problem when I boot. I also tried the CD version but I got the same error.

SirDice

Administrator

Absolon

Seems that it won’t boot on a USB stick either. Just stands there. Never had this problem with older releases before. I don’t know if going down to 8.x and then upgrade by compiling is a way to go in my case. I’m totally lost here.

shakky4711

Try to burn the setup CD1 to a regular CD and boot with this medium, have successful installed 9.0 a few days before this way.

I have had many more problems with burned DVDs than with CDs.

Absolon

After I get the above error message it seems to probe my DVD and I get the following lines

So doesn’t this mean that it does indeed find my DVD? Just don’t know why it prints this out after the error? I tried the CD with same results.

wblock@

Absolon

I changed the USB to behave like a floppy and got it to work! But the boot/install process is far from stable at this time IMO.

I don’t see the big difference between the old sysinstall and the new one other the I had way more option with sysinstall besides bsdinstall?
Maybe I’m missing out on something here?

Источник

Error 19 — Installing FreeNAS 11.1

remmert1

Cadet

Howdy All,
I am new to FreeNas and this is my first post so please be gentle :).
I have done several searches on «Error 19» but did not seem to find any real solutions so I am looking here for some help.

Hardware:
American Megatrends Sabertooth X58 Motherboard
Intel Core i7
12GB Ram
8GB San Disk USB thumb drive

I have FreeNAS-11.1-U4.iso and used ImgBurn on my Windows 10 system to create a boot CD.
When I boot the system everythings starts normal. I get the first screen and select FreeNAS Installer.
It then proceeds for several minutes with what I «assume» are standard boot messages.
Finally the following happens:

Trying to mount root from cd9660:/dev/iso9660/FreeNAS [].
mountroot: waiting for device /dev/iso9660/FreeNAS.
Mounting from cd9660:/dev/iso9660/FreeNAS failed with error 19.

I have tried with other USB thumb drives with the same result.
I have also tried with downloading the image a second time and burning a new CD, again with the same result.
I also took the same image and tried to install it on a VM on my Windows box and it worked fine up to FreeNAS Console Setup screen. I did not take the install any farther than that.

Does anyone have a suggestion or did I miss a post in my search?

Источник

Installation does not detect hard disk

aidin36

I downloaded the FreeBSD-9.0-RELEASE-amd64-memstick.img and wrote it on a 8GB flash disk with dd.

It booted successfully. But when it comes to partitioning the hard disk, it only detects one hard disk: the flash disk, as /dev/da0

I‘ve done these things:

1. Using «Shell» command instead of «Install», I found out that there’s only /dev/da0, and no other disks.
2. I changed my «On board SATA mode» from «AHCI» to «IDE». No new result.
3. I disabled ACPI boot option, but I faced this error at the boot time:

JakkFrosted

JakkFrosted

Uhg. I can’t edit my posts yet. I replied too hastily. I see you mean they aren’t even showing in /dev. Try [CMD=»pciconf»]-lv[/CMD] and determine what your disk controller is. Then enable the correct module in the /boot/loader.conf file. Reboot and if you enabled the correct module the disks should be present.

Reactions: aidin36

aidin36

I found out that I have a SB7x0/SB8x0/SB9x0 SATA Controller

Because the flash disk was mounted as Readonly filesystem, I couldn’t edit /boot/loader.conf

So I’ve done this:
On the boot menu, I pressed ESC, then:

I also try ataahci , and both together. Nothing changed.

But I think that I found out the problem.
On my dmesg I found these lines:

aidin36

JakkFrosted

Reactions: aidin36

aidin36

Thank you Jesse.

I tried RAID too. But still the same result.
I’m going to download FreeBSD-9.0-RELEASE-amd64-disc1.iso and see if it works.

aidin36

I tried the disk1.iso.

I still get the same time-out error at the boot time. In addition, the following error happens when it tries to mount root:

And it falls into mountroot. When I type ?, it says:

xeemo

cucu007

jb_fvwm2

pranavrana

I recently downloaded ‘PCBSD-9.img’ and faced the same problem of my SATA hard disk not being detected by the setup. Maybe there was a problem with the hard disk not being mounted. I made a little change in my BIOS which is to ‘enable’ the following options:

• AHCI Mode
• Wake on LAN
• Intel R Speedstep Tech

I don’t know which one of these actually did the trick, but after this my HDD was being detected and I am posting this message form my PC-BSD installation.

PCBSD is based on FreeBSD, this trick may work for FreeBSD as well.

PS: I think ‘AHCI Mode’ is the one.

Hope this helps.

DeliciousD

For what it’s worth, I discovered that the predecessor chipset (SB600) to the A740GM-M (SB700) had a problem with Message Signaled Interrupts according to PR 174985. Suspecting the same condition was preventing the 10.3-RELEASE installation medium from detecting the SATA disks, I set the loader driver hint variable for ahci(4) to disable msi set hint.ahci.0.msi=0 . The result is that the disks are detected and available when the system boots.

The drive is not mountable, however. gpart show will detect the USB attached drives, but the internal one /dev/ada0 appears as a raw disk even though it has gpart partitions and a full 8.4-STABLE installation.

At the moment I have no more time to experiment with the installing the upgrade. I’ll try to remember to post results, but make no promises.

DeliciousD

I have solved the mystery of the inaccessible /dev/ada0. The disk contained old graid(8) data as detailed in the handbook section «18.5 Software RAID Devices». On boot I noticed errors from graid(8) and using graid list -a saw the disk had been identified as a member of a stripe set and the status set to spare. Unfortunately for me, the procedure for clearing this documented in the handbook was unsuccessful. I tried using dd to overwrite the first 10MB of the disk and it is still saying it is part of a stripe set. The workaround is to disable RAID in the kernel.

The RAID stripe setting on the disk may have come from the motherboard’s on board RAID array tool which I used before. The volume showed up in the MB raid utility, and I deleted it, but FreeBSD still sees the data on the disk and tries to use it as a member of a stripe set.

Summary

To install FreeBSD 10.3 on my Elite Group A740GM-M v7.0 motherboard, it was necessary at boot to choose the loader prompt and disable MSI in the ahci(4) driver.
set hint.ahci.X.msi=0
(«X» is the bus number, in my case 0.)

Then, if the disk is generating GRAID errors on boot and you are unable to write to the disk (and your disk is not meant to be part of a RAID array) follow the handbook procedures noted above.

Источник

Hello.

I’m trying to emulate Freebsd for arm64 on my jetson nano (arm64) using qemu and kvm. This is the script that I’m using :

tunctl -t tap0
ifconfig tap0 up
brctl addif virbr0 tap0

/opt/qemu-5.2.0/build/aarch64-softmmu/./qemu-system-aarch64 -m 2048M -cpu cortex-a57 -M virt --enable-kvm 
       -bios /home/zi/Desktop/Work/I9/Virt/qemu/build/pc-bios/edk2-aarch64-code.fd --nographic 
       -drive id=cdrom0,if=none,format=raw,readonly=on,file=/home/zi/Desktop/Work/Android/OS/freebsd/FreeBSD-13.0-RELEASE-arm64-aarch64-disc1.iso 
       -device virtio-scsi-pci,id=scsi0 
       -device scsi-cd,bus=scsi0.0,drive=cdrom0 
       -drive if=none,file=/root/Desktop/zi/Work/Android/OS/freebsd/FreeBSD-13.qcow2,id=hd0 
       -device virtio-blk-device,drive=hd0 
       -device virtio-net-device,netdev=mynet 
       -netdev tap,id=mynet,ifname=tap0,script=no,downscript=no,vhost=on 
       -device virtio-gpu-pci,virgl=on,xres=1024,yres=768 
       -display sdl,gl=on 
       -no-reboot

It does not work. The error message is the following one :

Trying to mount root from cd9660:/dev/iso9660/13_0_RELEASE_AARCH64_CD [ro]...
mountroot: waiting for device /dev/iso9660/13_0_RELEASE_AARCH64_CD...
Mounting from cd9660:/dev/iso9660/13_0_RELEASE_AARCH64_CD failed with error 19.

Loader variables:
  vfs.root.mountfrom=cd9660:/dev/iso9660/13_0_RELEASE_AARCH64_CD
  vfs.root.mountfrom.options=ro

Manual root filesystem specification:
  <fstype>:<device> [options]
      Mount <device> using filesystem <fstype>
      and with the specified (optional) option list.

    eg. ufs:/dev/da0s1a
        zfs:zroot/ROOT/default
        cd9660:/dev/cd0 ro
          (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)

  ?               List valid disk boot devices
  .               Yield 1 second (for background tasks)
  <empty line>    Abort manual input

mountroot> random: unblocking device.

Maybe the solution is here :

https://forums.freebsd.org/threads/installing-9-0-release-mounting-dvd-failed-with-error-19.36579/

Where he says :

You need to get a boot prompt and disable [I]ACPI[/I] support before booting:

# set debug.acpi.disabled =»hostres»

# boot

the problem is that as soon as the qemu window appears,no key pressed inside the window have some effect,so I can’t have access to the boot options and I can’t write those commands. I tried to remove the option «nographic» from qemu,but it does not work. Inside the qemu window I see the message «guest disabled display» and the installation does not procede.

I tried also :

mountroot> cd9660:/dev/cd0 Trying to mount root from cd9660:/dev/cd0 []...

mountroot: waiting for device /dev/cd0...

Mounting from cd9660:/dev/cd0 failed with error 19.

Всё началось с того, что на работе возник таск — освоить новозакупленное серверное железо DEPO Storm 2350L2. В качестве операционной системы подразумевалось использовать FreeBSD 9.1.

На первый взгляд всё элементарно, качаем дистрибутив, заливаем на болванку, грузимся, устанавливаем и…

И тут бац! На этапе разметки диска выясняется, что… а диска-то и нету! Не беда, возможно не собран RAID-массив (ну надо же, и как я забыл проверить). Лезем в настройки контроллера… а не тут-то было, массив собран, и должен работать. Остаётся только одно — вооружаться отвёрткой Итак, вскрытие показало, наличие во внутренностях пациента RAID-контроллера Adaptec RAID 6805. Идём курить Hardware Compatibility List на предмет наличия/отсутствия упоминания о поддержке контроллера данной модели. Ну да, так и есть, поддержки данного устройства в ядре нет. Печаль, значит придётся немного повозиться.

Дальнейшие действия расписываю по шагам, в качестве рабочей ОС, в которой выполнялись все действия, будет так же FreeBSD, на рабочем ПК или на виртуалке, т. к. лично по мне интерфейс nix’овых операционок проще, и ближе:

1. Идём на официальный сайт Adaptec’а за поиском дровишек. Ура! Adaptec ответственно подошла к делу, поддержка нужной ОС у них выполнена, и даже дрова опенсорцные, но это ладно, это лирика, я человек ленивый (что уж греха таить), сам модуль драйвера компилить не буду, а возьму готовый из того же архива, благо он там есть.

Качаем:

# cd /home/user

/home/user # mkdir drivers

/home/user # cd drivers

/home/user/drivers # tar -zxvf aacraid_freebsd_b30034.tgz

В архиве:

— aacu.ko — модуль ядра 32х разряных ОС для поддержки  Adaptec RAID 6805;

— aacu64.ko — модуль ядра 64х разряных ОС для поддержки  Adaptec RAID 6805;

— aac9x-i386.tgz и aac9x-amd64.tgz — соответственно их исходники.

2. Теперь нам надо подготовить дистрибутив, добавить в него поддержку вышеуказанного контроллера, дабы было куда устанавливать систему

Качаем однодисковый дистрибутив в формате iso.

# cd /home/user

/home/user # wget ftp://ftp2.ru.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/9.1/FreeBSD-9.1-RELEASE-amd64-disc1.iso

/home/user # mkdir freebsd-9.1

/home/user # cd freebsd-9.1

Определяем iso-образа как memory disk (md0):

/home/user/freebsd-9.1 # mdconfig -a -t vnode -f ../FreeBSD-9.1-RELEASE-amd64-disc1.iso -u 0

Монтируем md0 как cd-rom:

/home/user/freebsd-9.1 # mount -t cd9660 /dev/md0 /mnt

Копируем содержимое каталога /mnt в другой каталог:

/home/user/freebsd-9.1 # tar -C /mnt -cf — . | tar -xf —

Добавляем модуль (в нашем случае) aacu64.ko в дистрибутив:

/home/user/freebsd-9.1 # cp /home/user/drivers/freebsd9/driver/aacu64.ko /home/user/freebsd-9.1/boot/modules/

В файл loader.conf добавляем  соответствующую строчку:

/home/user/freebsd-9.1 # vi boot/defaults/loader.conf
 

##############################################################

###     Other modules     ##########################################

##############################################################

aacu64_load=»YES» # Adaptec RAID 6805

Удаляем директорию .rr_moved:

/home/user/freebsd-9.1 # rm -Rf rr_moved

Устанавливаем (если до сих пор не был установлен) cdrtools-3.00_2, иначе утилита mkisofs будет недоступна:

/home/user/freebsd-9.1 # cd /usr/ports/sysutils/cdrtools

/usr/ports/sysutils/cdrtools # make install clean

Собираем новый iso-образ:

/usr/ports/sysutils/cdrtools # cd /home/user/freebsd-9.1

/home/user/freebsd-9.1 # mkisofs -V FreeBSD-9.1 -J -R -b boot/cdboot -no-emul-boot -o FreeBSD-9.1.iso

Записываем созданный образ:

/home/user/freebsd-9.1 # growisofs -Z /dev/cd0=FreeBSD-9.1.iso

3. Грузимся. Если процесс загрузки тормознёт с ошибкой:

Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19

….

mountroot>

Монтируем cd-привод вручную:

mountroot>cd9660:/dev/cd0

Загрузка продолжится без проблем.

4. Установка проходит как обычно. Единственное, на что надо обратить внимание — это на диски при их разметке, всё дело в том, что данный драйвер позволяет одновременно видеть из ОС как сам собранный массив, так и диски по отдельности, не ошибитесь при выборе

5. Но и это ещё не всё, погодите радоваться Даю гарантию 99%, что после ребута фряшка не сможет загрузиться самостоятельно. В чём проблема? А в том, что наш «умный» инсталлер не скопировал наши изменения и модули в установленную ОС. Как исправить? А просто. Вставляем установочный диск снова. Запускаем комп. В mountroot’е в который нас наверняка выкинет при неудачной загрузке  монтируем cd, как в пункте 3 (mountroot>cd9660:/dev/cd0). Загружаемся в LiveCD.

На флешку предварительно копируем aacu64.ko.

Далее вставляем и монтируем флешку:

# mount_msdosfs -o rw /dev/da4 /mnt

Теперь на неё смонтируем корневой раздел нашей ФС на RAID’е:

# cd /mnt

/mnt # mkdir hdisk

/mnt # mount -t ufs -o rw /dev/da0p2 /mnt/hdisk

Копируем модуль и правим loader.conf так же как и в п.2:

/mnt # cp aacu64.ko /mnt/hdisk/boot/modules

/mnt # vi /mnt/hdisk/boot/defaults/loader.conf
 

##############################################################

###     Other modules     ##########################################

##############################################################

aacu64_load=»YES» # Adaptec RAID 6805

Возможно ещё понадобится добавить флаг загрузки разделу da0p1:

/mnt # gpart set -a bootme -i 1 da0

6. Перезагружаемся. Вытаскиваем диски и флешки. Всё должно завестись.