Comment 7 for bug 1648561

I'm claiming this bug for myself since I know about os-prober and have other grub/os-prober updates in flight. Targetting to ubuntu-17.01.

Is this HTX thing doing read/write operations directly on the disk, or does it use a filesystem? Is it using a known filesystem or its own format?

"This caused write fails for sda1, sdb1 disks along with nvme disks and also logged Linux errors."

Do you mean write errors as reported by HTX?

The os-prober errors listed are just cosmetic, caused by the fact that os-prober, when run (this is run by grub/update-grub to detect possible other OSes on the system), will "probe" the filesystems: first detecting the available partitions, then attempting to "mount" them to finish probing. This is normally done by "grub-probe" and "grub-mount", which should be relatively safe, but also *had* another code path to use straight "mount" which has shown issues (a fix is available in xenial-proposed for it, should be made available in updates soon).

What version of os-prober do you have installed on this system? (use dpkg -l os-prober)

If all else fails, we could disable os-prober altogether; there's another fix coming up that does so on PowerNV due to the effect on Petitboot.