Bug #8242: LSI Logic 53c1030 from VirtualBox fails to find rootfs in bootloader sometimes - illumos gate - illumos

Actions

Copy link

Bug #8242

open

LSI Logic 53c1030 from VirtualBox fails to find rootfs in bootloader sometimes

Added by Michal Nowak about 6 years ago. Updated over 5 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Start date:

2017-05-16

Due date:

% Done:

Estimated time:

Difficulty:

Medium

Tags:

needs-triage

Gerrit CR:

External Bug:

Description

OpenIndiana 2017.04 ISO attached to LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI from VirtualBox 5.1.22 sometimes fails in bootloader with

"No rootfs module provided, aborting", or
"can't open /boot/forth/beastie.4th: no such file or directory"

This is how the VM is created:

VBoxManage  createvm --name SUT-1 --register
VBoxManage  modifyvm SUT-1 --ostype Solaris11_64 --longmode on
VBoxManage  modifyvm SUT-1 --memory 1536 --cpus 1
VBoxManage  modifyvm SUT-1 --boot1 disk --boot2 dvd
VBoxManage  modifyvm SUT-1 --vrdeproperty VNCPassword=nots3cr3t
VBoxManage  modifyvm SUT-1 --vrde on --vrdeaddress '' --vrdeport 5901
VBoxManage  modifyvm SUT-1 --vram 4 --accelerate3d off --audio pulse --audiocontroller ac97
VBoxManage  modifyvm SUT-1 --nic1 nat --nictype1 82540EM --cableconnected1 on
VBoxManage  modifyvm SUT-1 --mouse usbtablet
VBoxManage  modifyvm SUT-1 --ioapic on --apic on --x2apic off --acpi on --biosapic=apic --pae off --rtcuseutc on
VBoxManage  modifyvm SUT-1 --chipset ich9
VBoxManage  modifyvm SUT-1 --uart1 0x3F8 4
VBoxManage  modifyvm SUT-1 --uartmode1 tcpserver 12341
VBoxManage  storagectl SUT-1 --name SCSI --add scsi --controller lsilogic --bootable on --hostiocache on
VBoxManage  storageattach SUT-1 --storagectl SCSI --port 0 --device 0 --type dvddrive --medium OI-hipster-text-20170502.iso
VBoxManage  createhd --filename SUT-1_1 --size 20480
VBoxManage  storageattach SUT-1 --storagectl SCSI --port 1 --device 0 --type hdd --medium SUT-1_1.vdi
VBoxManage  startvm SUT-1 --type headless

Even if it's able to install the system, it than fails to boot from it.

Screenshots attached. prtconf -v as well.

Files

Download all files

beastie-4th.png (16.5 KB) beastie-4th.png		Michal Nowak, 2017-05-16 04:59 PM
no-rootfs.png (14.4 KB) no-rootfs.png		Michal Nowak, 2017-05-16 05:00 PM
prtconf.txt (75.1 KB) prtconf.txt		Michal Nowak, 2017-05-16 05:01 PM

Actions

Copy link

Updated by Toomas Soome about 6 years ago

Michal Nowak wrote:

OpenIndiana 2017.04 ISO attached to LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI from VirtualBox 5.1.22 sometimes fails in bootloader with

"No rootfs module provided, aborting", or

"can't open /boot/forth/beastie.4th: no such file or directory"

This is how the VM is created:
[...]

Even if it's able to install the system, it than fails to boot from it.

Screenshots attached. prtconf -v as well.

This does sound quite interesting - as you can see from the rootfs error, it did fail to gunzip the boot_archive, also other errors point to random IO issues. In this case, I would first check if the vbox itself is recent enough and also it probably is good idea to check if there is any difference about changing HBA type there.

Actions

Copy link

Updated by Toomas Soome about 6 years ago

just tested with the same config you have pasted (used the same commands), and can not reproduce.

virtualbox 5.1.18 r114002 (Qt5.6.2) on macOS

Tested both by installing 2016.10 and pkg update to latest and then installed 2017.05.

Actions

Copy link

Updated by Michal Nowak about 6 years ago

Well, I can't reproduce it as well anymore. Running VirtualBox 5.1.22 on openSUSE Leap 42.2 on SSD disk. It happened with both LSI SCSI & SAS, the rest - SATA & IDE - are fine.

Is there something I can run on ok prompt to gather more info, should it happen again?

Actions

Copy link