I connect using ssh to a FreeBSD host and run bhyve. so Alt+Fn is not
applicable. But your idea is applicable. :-)

Running df -h in the "emergency shell" in the ubuntu installer (after it
failed installing the grub bootloader) gives:

~ # df -h

Filesystem                Size      Used Available Use% Mounted on

none                    200.3M    148.0K    200.1M   0% /run

devtmpfs                995.7M         0    995.7M   0% /dev

/dev/sr0                672.0M    672.0M         0 100% /cdrom

/dev/mapper/c--182--181--143--31--vg-root

                        960.4M    936.1M         0 100% /target

/dev/vda1               235.3M     29.1M    194.1M  13% /target/boot

/dev/mapper/c--182--181--143--31--vg-home

                        495.8M    408.0K    459.0M   0% /target/home

/dev/sr0                672.0M    672.0M         0 100% /target/media/cdrom
devtmpfs                995.7M         0    995.7M   0% /target/dev






On Thu, Jan 23, 2014 at 12:38 PM, Lars Engels <lars.eng...@0x20.net> wrote:

> Am 2014-01-23 11:53, schrieb Jonas Bülow:
>
>  FWIW, I extracted the syslog for the failing ubuntu installation. The
>> failing grub install shows up as:
>>
>> Jan 23 10:51:08 grub-installer: info: architecture: amd64/generic
>> Jan 23 10:51:08 in-target: Reading package lists...
>> Jan 23 10:51:08 in-target: Reading package lists...
>> Jan 23 10:51:08 in-target:
>> Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on
>> device)
>> Jan 23 10:51:08 in-target: E: Can't mmap an empty file
>> Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9:
>> Bad file descriptor)
>> Jan 23 10:51:08 in-target: E: The package lists or status file could
>> not be parsed or opened.
>> Jan 23 10:51:08 grub-installer: info: Identified partition label for
>> /dev/vda1: msdos
>> Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute
>> 'grub-probe': No such file or directory
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No
>> space left on device
>> Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute
>> 'grub-probe': No such file or directory
>> Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3
>> (pipe:[7196]) leaked on lvdisplay invocation.
>> Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735:
>> /bin/sh
>> Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4
>> (/dev/ttyS0) leaked on lvdisplay invocation.
>> Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735:
>> /bin/sh
>> Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5
>> (/dev/ttyS0) leaked on lvdisplay invocation.
>> Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735:
>> /bin/sh
>> Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6
>> (/dev/ttyS0) leaked on lvdisplay invocation.
>> Jan 23 10:51:08 main-menu[211]: (process:18530):  Parent PID 18735:
>> /bin/sh
>> Jan 23 10:51:08 main-menu[211]: (process:18530):
>> Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group "vda" not
>> found
>> Jan 23 10:51:08 main-menu[211]: (process:18530):
>> Jan 23 10:51:08 main-menu[211]: (process:18530):
>> Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group vda
>> Jan 23 10:51:08 main-menu[211]: (process:18530):
>> Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver
>> "config": could not write /var/cache/debconf/config.dat-new: No space
>> left on device
>> Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring
>> 'grub-installer' failed with error code 1
>> Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer'
>> failed.
>> Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit
>> from 'medium' to 'low'
>> Jan 23 10:51:09 debconf: Setting debconf/priority to low
>> Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected
>>
>>
>>
>>
> Normally you can switch to another virtual console with Alt+F1 to F4
> (IIRC), I don't know if
> that's also possible in bhyve.
> If it works, please open a shell and see with "df" which filesystem is
> full.
>
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-
> unsubscr...@freebsd.org"
>
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to