FS#69031 - [archiso] not able to automatically find and mount itself during bootup process.

Attached to Project: Release Engineering
Opened by Nathaniel Chin (nathanielcwm) - Saturday, 19 December 2020, 02:53 GMT
Last edited by David Runge (dvzrv) - Friday, 18 February 2022, 18:23 GMT
Task Type Bug Report
Category ArchISO
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When burnt to a CD the ISO is unable to automatically find itself during the bootup process. This results in it falling back to an interactive prompt.

This can be circumvented by mounting the disc drive manually to /run/archiso/bootmnt. After mounting you need to exit twice as the first time it would give an error about it being mounted; the second time you exit will actually boot the ISO.

The issue occurs under the December and October 2020 ISOs. Both were burned with an Acer branded Slim DVD burner, the firmware reports it as a Hitachi burner, and they were read from a Matsushita Desktop DVD burner. The motherboard is in UEFI only mode. I believe the October ISO was burnt using k3b; the December ISO was burnt using the built in Windows Burning Program.
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 18 February 2022, 18:23 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Please report further issues at https://gitlab.archlinux.org/archlinux/a rchiso/-/issues
Comment by Nathaniel Chin (nathanielcwm) - Saturday, 19 December 2020, 03:00 GMT
It may actually be an issue with the Matsushita burner as I've just tested it on the Acer and it boots no issue.

I've tested the Acer burners on two machines with the October ISO and it boots without issue.
Comment by Brandon Raymond (braraym) - Friday, 25 December 2020, 16:23 GMT
I also have this issues trying to boot the ISO in a virtual machine. (Screenshot attached)

Earlier this week I also used the ISO to boot on a UEFI machine and I had no problem. So maybe it is only happening when booting with BIOS? (My virtual machine is booting from BIOS)
Comment by Nathaniel Chin (nathanielcwm) - Saturday, 26 December 2020, 04:58 GMT
btw the Matsushita drive is a SW-9588-C manufactured in November 2006.
Comment by David Runge (dvzrv) - Friday, 02 July 2021, 12:06 GMT
@nathanielcwm: Thanks for the report and the long response time.

Your issue appears to be hardware specific(?). Is it still happening with more recent installation media?

@braraym: I am not sure if your issue is actually related, as the OP specified this to be a problem in the context of the image being burned to CD/DVD (and your example attempts to boot in a virtualized environment which may have plenty other issues).
Comment by Nathaniel Chin (nathanielcwm) - Saturday, 03 July 2021, 15:28 GMT
Haha np.

Ye seems to be a specific issue with this drive lol, most recent i've tried is 2020 Dec, which is admittedly very old, and it was still present.
Comment by Nathaniel Chin (nathanielcwm) - Sunday, 04 July 2021, 08:28 GMT
Haha np.

Ye seems to be a specific issue with this drive lol, most recent i've tried is 2020 Dec, which is admittedly very old, and it was still present.
Comment by Nathaniel Chin (nathanielcwm) - Sunday, 04 July 2021, 10:09 GMT
Haha np.

Ye seems to be a specific issue with this drive lol, most recent i've tried is 2020 Dec, which is admittedly very old, and it was still present.
Comment by Nathaniel Chin (nathanielcwm) - Friday, 09 July 2021, 03:05 GMT
Haha np.

Ye seems to be a specific issue with this drive lol, most recent i've tried is 2020 Dec, which is admittedly very old, and it was still present.
Comment by David Runge (dvzrv) - Friday, 18 February 2022, 18:22 GMT
@nathanielcwm: If this issue still persists, please open a ticket in the archiso issue tracker: https://gitlab.archlinux.org/archlinux/archiso/-/issues

The Release Engineering issue tracker here on flyspray will be shut down.

Loading...