Bug 27679

Created attachment 12026 [details]
M8 netinstall grub2-install fail

From https://html.duckduckgo.com/html/?q=grub2-install+structure+needs+cleaning&kp=-2&atb=v47-2_y&t=mageia

Looks like an existing file system was chosen, but that file system requires
a fsck to be run on it, since it was not previously shut down cleanly.

If the file system was just created by the net installer, then it's a bug.
If it was previously created and not unmounted properly then it's not a bug,
and this bug report should be resolved as invalid.

CC: (none) => davidwhodgins

Also, if I'm interpreting https://www.kernel.org/doc/html/latest/filesystems/bfs.html correctly, bfs should not be used to install Mageia into.

(In reply to Dave Hodgins from comment #3)
> Also, if I'm interpreting
> https://www.kernel.org/doc/html/latest/filesystems/bfs.html correctly, bfs
> should not be used to install Mageia into.

The install was into a blank USB drive. I instructed the installer to completely erase what was on the drive and start anew. I booted from the installer. The repo
was on a M7.1 system.

I admit I don't fully nderstand what's going on here. I've had many succesful
M8 installs exactly the same way. This one failed for the above.

(In reply to Dave Hodgins from comment #2)
> From
> https://html.duckduckgo.com/html/?q=grub2-
> install+structure+needs+cleaning&kp=-2&atb=v47-2_y&t=mageia
> 
> Looks like an existing file system was chosen, but that file system requires
> a fsck to be run on it, since it was not previously shut down cleanly.
> 
> If the file system was just created by the net installer, then it's a bug.
> If it was previously created and not unmounted properly then it's not a bug,
> and this bug report should be resolved as invalid.

The history of the target USB drive was that it previoulsy had M8 installed. Likely
a netinstall. And it got corrupted during all the M8 changes in the last week.
So I decided to start all over. Again, during the initial menues I instructed
the installer to erase everything on the drive and start all over.

As per comment 3, use a file system that supports linux ownership and permissions, and directory structures, not bfs.

On a usb stick, probably F2FS is the most flash friendly.
https://en.wikipedia.org/wiki/F2FS
Either that or ext2 since it doesn't have journaling.

Closing the bug as invalid since bfs is not a suitable choice for the file
system linux is being installed on.

Resolution: (none) => INVALID
Status: NEW => RESOLVED

Meant to add, feel free to reopen if I've misunderstood anything.

(In reply to Dave Hodgins from comment #7)
> Meant to add, feel free to reopen if I've misunderstood anything.

More testing here tells me that the USB target drive somewhere has been rendered read only.
No matter what I use I cannot "zero" it out. Example in a su terminal:

dd if=/dev/zero of=/dev/sdb bs=1M count=1
comes back with a write error

gparted can't refomat it

isodumper can't reformat it.

there's no little switch on it to make it write only.

Created attachment 12027 [details]
This is what the target drive looks like in gparted

Any other USB device I can change, reforma it
It even still boots to the previous M8 install
I can even write files to it while I'm in the drive

So grub2-install failing to copy to bfs.mod file is just because that was the
file being copied when the drive failed, not because a bfs file system is being
used. Thanks for the update.

Leaving the bug closed since it's a hardware failure, assuming it is a bad
drive. :-)

(In reply to Dave Hodgins from comment #11)

> So grub2-install failing to copy to bfs.mod file is just because that was the
> file being copied when the drive failed, not because a bfs file system is
> being
> used. Thanks for the update.

Thank you David. It's one of those if it can go bad it will things. Murphys Law.