Re: [linux-apfs/linux-apfs-oot] bad node only when mounting volume 0 (#3)

[Ernesto A. Fernández]

Thanks for the thorough report.

> Container keybag: odd inconsistency (may not be corruption).
> Volume superblock: unknown optional feature

One of your volumes has an undocumented feature but it's compatible, so that
shouldn't be the cause of your problem. The apfsck stops running as soon as
it finds anything to report so, if you can, try running it without the -u
flag next.

> bad node in block 0xad22
> unable to read catalog root node

It would be useful to take a look at this image; if it has private
information, would you mind sharing at least a couple of blocks, such as
0x0 and 0xad22?

[Ernesto A. Fernández]

> running `apfsck -w ...` gives the same output. `apfsck -c` doesn't give any output. Perhaps I'm using the programs wrong, but I read the manpage and it seemed like nothing else of value could be gained from this.

No output means everything looks fine. That's very strange, it seems that
the fsck is finding the catalog root without any problem, unlike the
module.

> I could absolutely share some information, this is a fresh install.

That's good to hear.

> But how to do so I don't know. Can you give me instructions?

Sure. You can copy the first 1gb from the container with the following
command (as root):

dd if=<input_device> of=<output_file> bs=4096 count=262144

Replace <input_device> with the path to the device file for your container,
and <output_file> with the name you want for the output file. Then upload
this file somewhere, and send me the link.

Hopefully 1gb will be enough. Let me know if you are having trouble with
something.