-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[issue]: Unable to detect XFS partition (F2) #2494
Description
Official FAQ
- I have checked the official FAQ.
Ventoy Version
1.0.94
What about latest release
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
No. I didn't try these alternative boot modes.
BIOS Mode
UEFI Mode
Partition Style
GPT
Disk Capacity
500GB
Disk Manufacturer
Seagate
Image file checksum (if applicable)
None
Image file download link (if applicable)
No response
What happened?
Goal
I would like to boot an image from a separate partition, it's formatted as XFS.
An older Ventoy install can do this, but my newer one cannot. Possibly XFS filesystem was created with incompatibility for older kernel XFS drivers, may also affect Ventoy?
Background
Ventoy is installed to external USB SSD (Segate Firecuda 500GB) disk with Ventoy partition (part 1) as exFAT, there is also NTFS (VHD files) and XFS (vDisk .vtoy files) partitions added into the reserved space after Ventoy install.
I installed Ventoy to this disk when Ventoy 1.0.78 was the new release. I would have installed it from Windows. Everything worked fine except the XFS partition was not accessible.
Today I updated via the Linux GUI app with 1.0.94 release. No improvement. Deleted XFS partition, created new XFS partition and exFAT partition, copied .vtoy image to both. Only new exFAT partition was detected by Ventoy F2 menu, XFS missing.
On another disk with BTRFS partition, Ventoy would detect this (but is not supported).
Additional information
I have an older Ventoy install on a Samsung T7 500GB USB disk. It has a separate XFS partition as well but can detect and boot from XFS without issue. This was created around Feb 2022.
I have also noticed some older systems cannot mount XFS from newer systems. Perhaps an incompatibility introduced when XFS partition is created with newer kernels, as updating the older systems kernel it was able to mount my newer XFS partitions.
Ventoy uses GRUB, perhaps the XFS driver also has this issue and needs to be updated?
Environment
The current environment for Ventoy is Windows 11 host with VMWare Workstation Player 17.0.2, VM guest CachyOS (ArchLinux) with 6.4 kernel (VMX file modified to support EFI at OS install). Machine is laptop: ASUS Zephyrus G14 (2023).
Same experience booting Ventoy from UEFI of the laptop directly, or booting Ventoy from the VM guest UEFI.
Presumably, if I connect my older Ventoy (Samsung T7) disk, the new Ventoy (Seagate Firecuda) disk will detect the XFS partition on it and be able to access it.