Hi Henrich,
> To be clear, fscking does not correct the issue with /bsd? It's still
> just several KB? Is this random, or do you have the ability to readily
> reproduce it?
Correct. I looked into the issue more today and believe I've achieved
100% reproducibility. However, the problem is entirely
On Sun, 2025-05-11 at 16:25 +, H. Hartzer wrote:
> Lloyd wrote:
> > I've run across this a few times, where I've improperly shut down
> > a VM (tapped the wrong button for power off vs ACPI shutdown) and
> > this lead to an unbootable image with the message before boot:
> >
> > booting hd0a:/b
Lloyd wrote:
> I've run across this a few times, where I've improperly shut down
> a VM (tapped the wrong button for power off vs ACPI shutdown) and
> this lead to an unbootable image with the message before boot:
>
> booting hd0a:/bsd: hd0a:/bsd: Inappropriate file type or format
> failed(79). wil
On Sun, May 11, 2025 at 03:22:39AM +, Lloyd wrote:
> Nick Holland wrote:
>
> > wild guess: you have a "single partition" model, rather than the
> > suggested, so rather than the root file system being fairly quiet
> > during normal operation, you have a lot of overall filesystem
> > churn tak
Nick Holland wrote:
> wild guess: you have a "single partition" model, rather than the
> suggested, so rather than the root file system being fairly quiet
> during normal operation, you have a lot of overall filesystem
> churn taking place. (I'm not a FS person...so I may be full of
> ).
Eh n
On 5/10/25 14:45, Lloyd wrote:
I've run across this a few times, where I've improperly shut down
a VM (tapped the wrong button for power off vs ACPI shutdown) and
^^ well, an alarm bell just went off in my head. :)
this lead to an unbootable image with the message before boot:
booting hd0
6 matches
Mail list logo
