Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#46242 - [syslinux] `syslinux-install_update -m` misinterprets disks with numerics in names
Attached to Project:
Arch Linux
Opened by Tim Popham (popham) - Wednesday, 09 September 2015, 23:07 GMT
Last edited by Anatol Pomozov (anatolik) - Sunday, 28 February 2016, 17:14 GMT
Opened by Tim Popham (popham) - Wednesday, 09 September 2015, 23:07 GMT
Last edited by Anatol Pomozov (anatolik) - Sunday, 28 February 2016, 17:14 GMT
|
DetailsDescription:
I'm on a Chromebook with an SSD that shows up as `/dev/mmcblk0` with partitions `/dev/mmcblk0p1`, etc. `syslinux-install_update -m` goofs the install and then reports success :(. Following the wiki's manual instructions works. I'm using GPT, but `syslinux-install_update -m` writes `mbr.bin` to the master boot record instead of `gptmbr.bin`. It reports that everything completed successfully, but then I reboot and ...nope: "Operating system not found" or "OS not found" (I'm 90% sure that it's the former). (When I was dropping random `echo`s in the script, I saw an `mmcblk` without the trailing `0` blow by. I figured that some pattern matching that is intended to take `sda5` to `sda` is taking `mmcblk0p1` to `mmcblk` and that the error goes unnoticed.) Additional info: * Build Date: 2015-03-26 16:40 UTC Steps to reproduce: * Basic setup of GPT partition table with a ext2, 100 MiB /dev/mmcblk0p1 and ext4, 2000000 MiB /dev/mmcblk0p2 (I'm using gdisk). * `mount /dev/mmcblk0p2 /mnt && mkdir /mnt/boot && mount /dev/mmcblk0p1 /mnt/boot` * `syslinux-install_update -c /mnt -i` * Update /mnt/boot/syslinux/syslinux.cfg to reflect the root filesystem at /dev/mmcblk0p2. * `syslinux-install_update -c /mnt -m` |
This task depends upon
Closed by Anatol Pomozov (anatolik)
Sunday, 28 February 2016, 17:14 GMT
Reason for closing: Fixed
Additional comments about closing: 6.04-5
Sunday, 28 February 2016, 17:14 GMT
Reason for closing: Fixed
Additional comments about closing: 6.04-5
- there is similar "local disk="${bootpart%%[[:digit:]]*}"" code just a few lines above in the raid checking section. Do we need to fix it the same way?
- we need to have a guard that checks $disk is a valid storage device to prevent this kind of issues in the future.
I am away from my workstation and will be available to test it only in 2 weeks.
Also, I'd change the error message back, since a partition is also a block device. There is no such thing as a "block partition".
Please see attached patch.