Bug 23966

Summary:	won't format disk sda1 (Can't call method "val" on an undefined value.)
Product:	Mageia	Reporter:	Lloyd Osten <lloyd.osten>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED INVALID	QA Contact:
Severity:	major
Priority:	Normal	CC:	isobuild, lloyd.osten, marja11, pterjan, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Lloyd Osten 2018-12-08 14:34:13 CET

I just tried installing Mageia 7 beta 1 64 bit under VirtualBox (on Mageia 6)

I created a 40Gig virtual hard drive. When it started to format the disk with ext4, a message came up that said, "can't call method "val" on an undefined value." So Formatting failed. It did get past this error one time and actually started installing, but died pretty early in the package installation process. It just stopped. Removing and re-creating the virtual hard disk produced the same results. I tried it several times...without success.

Comment 1 Marja Van Waes 2018-12-09 12:11:05 CET

Thanks for the bug report.

Please reproduce the issue, switch to tty2 inside VirtualBox, insert a USB key and type "bug", so that report.bug gets written to the USB key.

Then attach report.bug to this bug report. Compress with xz if it's too large to attach.

Thanks :-)

CC: (none) => isobuild, marja11, pterjan
Summary: won't format disk sda1 => won't format disk sda1 (Can't call method "val" on an undefined value.)
Assignee: bugsquad => mageiatools

Comment 2 Lloyd Osten 2018-12-09 15:02:12 CET

As it turns out, this IS NOT a bug after all. I made a couple of tweaks to my VirtualBox settings and then beta 1 installed and ran flawlessly.

Comment 3 Thierry Vignaud 2018-12-11 11:11:00 CET

For the record, what was the vbox setting change that causes it?

CC: (none) => thierry.vignaud

Comment 4 Lloyd Osten 2018-12-11 13:05:20 CET

This is what I changed in VirtualBox. I changed the default virtualization setting from "default" to "Hyper-V" and the type of drive from "solid state" to "normal"...i.e, I unchecked the box for "solid-state drive." (it actually IS on an SSD...I changed it back after beta 1 was installed.)

CC: (none) => lloyd.osten

Comment 5 Marja Van Waes 2019-08-06 19:16:06 CEST

(In reply to Lloyd Osten from comment #2)
> As it turns out, this IS NOT a bug after all. I made a couple of tweaks to
> my VirtualBox settings and then beta 1 installed and ran flawlessly.

Closing, then

Status: NEW => RESOLVED
Resolution: (none) => INVALID