bad sector
2023-06-01 16:57:52 UTC
Execution of command "[["/usr/sbin/grub2-mkconfig", "-o",
"/boot/grub2/grub.cfg"]]" failed.
Exit code: 139
Error output: Generating grub configuration file ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "en_US.UTF-8",
LC_TIME = "Default.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Found linux image: /boot/vmlinuz-5.14.21-150400.24.63-default
Found initrd image: /boot/initrd-5.14.21-150400.24.63-default
Found linux image: /boot/vmlinuz-5.14.21-150400.22-default
Found initrd image: /boot/initrd-5.14.21-150400.22-default
Found memtest image: /boot/memtest.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create
new boot entries.
Found Artix Linux (rolling) on /dev/sda1
Found Devuan GNU/Linux 4 (chimaera) on /dev/sda2
Found Slackware 15.0 x86_64 on /dev/sda3
Found openSUSE Tumbleweed on /dev/sda5
Found Ubuntu 22.04.2 LTS (22.04) on /dev/sda6
Found MX 21.3 Wildflower (21.3) on /dev/sda7
Found openSUSE Leap 15.5 Beta on /dev/sda8
I have 'locale' citations from time to time in various failed tasks but
this is the first time that booting is involved. First of all WTF does
locale have to do with booting AT ALL? I normally set such prefs during
install, for example North-America, keyboard US-english, Pangnirtung
Canada, Zulu -5h time (Eastern with daylight saving). Then, how does
"unset" get to be "supported" on a system? While on the topic, why does
Yast check for software repos and for 'trust' for a boot setup? Useless
foreign fluff should not be allowed at all within 50 miles of anything
having to do with booting. KISS!
"/boot/grub2/grub.cfg"]]" failed.
Exit code: 139
Error output: Generating grub configuration file ...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "en_US.UTF-8",
LC_TIME = "Default.UTF-8",
LANG = "C"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Found linux image: /boot/vmlinuz-5.14.21-150400.24.63-default
Found initrd image: /boot/initrd-5.14.21-150400.24.63-default
Found linux image: /boot/vmlinuz-5.14.21-150400.22-default
Found initrd image: /boot/initrd-5.14.21-150400.22-default
Found memtest image: /boot/memtest.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create
new boot entries.
Found Artix Linux (rolling) on /dev/sda1
Found Devuan GNU/Linux 4 (chimaera) on /dev/sda2
Found Slackware 15.0 x86_64 on /dev/sda3
Found openSUSE Tumbleweed on /dev/sda5
Found Ubuntu 22.04.2 LTS (22.04) on /dev/sda6
Found MX 21.3 Wildflower (21.3) on /dev/sda7
Found openSUSE Leap 15.5 Beta on /dev/sda8
I have 'locale' citations from time to time in various failed tasks but
this is the first time that booting is involved. First of all WTF does
locale have to do with booting AT ALL? I normally set such prefs during
install, for example North-America, keyboard US-english, Pangnirtung
Canada, Zulu -5h time (Eastern with daylight saving). Then, how does
"unset" get to be "supported" on a system? While on the topic, why does
Yast check for software repos and for 'trust' for a boot setup? Useless
foreign fluff should not be allowed at all within 50 miles of anything
having to do with booting. KISS!