I have a situation where os-prober when mounting an ext4 partition takes up CPU 100% and does not come out.
1) Partitions [ EFI ] [ WIn Reserved ] [Win ] [ empty ] [swap ] [arch] [ ntfs ]
2) Arch is already installed in 'sda6'
3) Arch partition is NOT mounted <- important
4) os-prober is enabled
5) fstab does not have an entry for sda6
Each time I run 'grub-mkconfig', the process grub-mount /dev/sda6' - which is arch partition - gets stuck. It happens each time.
Workaround I've found is to mount sda6 manually somewhere. In this case grub-mount identifies arch and comes out immediately.
**update** : ran os-prober standalone. Once while arch's partition is mounted, and once when it isn't. When mounted, os-prober detects and comes out immediately. When not mounted, grub-mount /dev/sda6 waits forever - taking almost 100% cpu
Any idea what might be happening? TIA
1) Partitions [ EFI ] [ WIn Reserved ] [Win ] [ empty ] [swap ] [arch] [ ntfs ]
2) Arch is already installed in 'sda6'
3) Arch partition is NOT mounted <- important
4) os-prober is enabled
5) fstab does not have an entry for sda6
Each time I run 'grub-mkconfig', the process grub-mount /dev/sda6' - which is arch partition - gets stuck. It happens each time.
Workaround I've found is to mount sda6 manually somewhere. In this case grub-mount identifies arch and comes out immediately.
**update** : ran os-prober standalone. Once while arch's partition is mounted, and once when it isn't. When mounted, os-prober detects and comes out immediately. When not mounted, grub-mount /dev/sda6 waits forever - taking almost 100% cpu
Any idea what might be happening? TIA
Statistics: Posted by Ravi Joshi — 2024-11-09 21:50 — Replies 2 — Views 59