Unable to parse ARC name error. about quibble HOT 6 OPEN

Make sure you at using the actual partition UUID and not the GPT PARTUUID

from quibble.

I'm having the same issue, though I have checked that the UUID is the one returned by btrfs check (following the README).

It seems I am able to boot using the direct path multi(0)disk(0)rdisk(0)partition(4)\Windows (Windows is on the 4th partition of my first drive) as workaround.

Please note that the path @xAndrei166 has for their debug config (multi(0)disk(1)rdisk(0)partition(2)\Windows) will give the same Unable to parse ARC name error since the beginning of the path MUST be multi(0)disk(0)rdisk( and it's the number following rdisk( that indicates the drive number. (According to the code of the 20210111 release)

from quibble.

I'll poke around more when I get the chance, it's been 2 years since i asked this lol

edit: i just remembered that back when i asked this i had a really unusual VM configuration so that might've been the issue

from quibble.

I encountered the same fault。

from quibble.

Anyone knows what ARC path to use to boot an NTFS windows for an nvme disk? (crashed my windows esp)

parted print all gives the following at the very end (and always at the end of 4 disks)

Model: Samsung SSD 970 EVO Plus 250GB (nvme)
Disk /dev/nvme0n1: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  660MB  659MB   fat32        SS250.ESP                     boot, esp
 3      660MB   676MB  16.8MB               Microsoft reserved partition  msftres
 4      676MB   128GB  128GB   ntfs         Basic data partition          msftdata
 5      128GB   250GB  122GB   ext4         SS250.NIX

from quibble.

I wiped everything (deleted all windows partitions, cleaned the EFI partition), reinstalled Windows from scratch, converted the NTFS partition to Btrfs with ntfs2btrfs version 20220812, extracted release 20210111 of quibble into the EFI partition, and now it seems to be able to parse btrfs() system paths.

In other words, I cannot reproduce this issue anymore.

from quibble.