possible NVME issues (unconfirmed)

[vcesinger]

Setup:

• Windows10
• Raspberry Pi 5
• NVME Device 512GB
• 04/03/24
• Raspberry Pi OS

The installscript ends with :
yad:26876: Gdk-CRITICAL ** gdk_x11_windows_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed

The installation does not work.

[Botspot]

That warning is normal on PiOS Bookworm and any Wayland system, is non-fatal, and should not affect functionality.

The installation does not work.

If you want help with that, then you will need to be specific on what actually happened.

[vcesinger]

Hi,
thanks for getting back to me. I thought this error was the problem, that i can not install it on a SSD. I am using a GeeekPi N05 M.2 M-Key NVMe HAT für Raspberry Pi 5 with a 512 GB SSD.
Installation of PI OS works with no errors, the WOR-Flasher results in a missing boot device.
Any idea?

[Botspot]

Hi, thanks for getting back to me. I thought this error was the problem, that i can not install it on a SSD. I am using a GeeekPi N05 M.2 M-Key NVMe HAT für Raspberry Pi 5 with a 512 GB SSD. Installation of PI OS works with no errors, the WOR-Flasher results in a missing boot device. Any idea?

Did wor-flasher actually give you an error?
Or did you encounter an error after booting the drive flashed with wor?

[vcesinger]

Hi, i made a step forward. I discovered that the WOR-Flasher uses the 0.2 UEFI version which does not support NVME, now i managed to get it to 0.3 but after starting the windows installer is returning an error that it misses a drive to install to.

[Botspot]

I've updated wor-flasher to use the 0.3 version of Pi5 UEFI. Any updates on this?

[endme2085]

I tried this with the same warning and the usb(which is a nvme reader) got three partitions,one is the uefi, the second is 18GB partition with a file "install.wim", but the other one can't be seen even in diskgenius.

[vcesinger]

I am facing the same issue...

[SeaDog58]

BotSpot,
Some weeks ago I used WOR Flasher to create a Windows Pro 11 installation on a Raspberry Pi 5 on a 500 gb USB drive successfully.
Now I have been trying the same installation process to put Windows Pro 11 on an NVME drive. I have been unsuccessful. Here are the hardware details.
• Raspberry Pi 5 running Raspberry OS on a 32gb SD
• Hat: GeeekPi N04 M.2 NVMe to PCIe Adapter for Raspberry Pi 5, Support M.2 NVMe SSD
• SSD: Western Digital 1TB SN750 NVMe Internal Gaming SSD Solid State Drive - Gen3 PCIe, M.2
I had been getting the critical error on GDK as reported above but now understand that is not an issue.
I was having problems with not being able to find a boot device. Since you reported you have updated wor-flasher to use the 0.3 version of Pi5 UEFI, I used “git clone https://github.com/Botspot/wor-flasher” today to update my files.
I ran the gui version of Flasher. I selected the NVME drive for flashing Windows Pro 11 and it completed without obvious errors. After flashing and rebooting, I noted in the Raspberry OS desktop, it showed an 18gb drive with a file install.wim.
After that, I waited a long time, and nothing happened. So I did sudo raspi-config and selected option 2 for booting from NVME, USB, and SD in that order. Rebooted.
After some time, WOR-PE reported it couldn’t find the installation disk. The log showed:
• Disk 0 now the selected disk.
• Virtual disk service error.
• The disk not initialized. Exit code 2147212265
• Couldn’t mount the partition.
• Couldn’t fine the PE disk
After flashing should I just let it sit there without rebooting? Could that be the problem?
John

[chrisgch]

I have the same problem with WoR from the pi-apps store. I have installed Windows 11 from Raspbian to the official 256GB Raspberry NVMe SSD, which ended with the same 'GDK_IS_X11_WINDOW (window)' failed error. I then tried booting from the SSD, which resulted in error "Could not find the installation disk!". The log is the same as reported by SeaDog58 in May. Any ideas?

[chrisgch]

Another test with the PI5: I installed WoR to a USB flash drive and booted from that. This let me choose the NVMe drive as installation target, but unfortunately dispart then failed with an error. The log file is attached. I also tried replacing storahci.sys and stornvme.sys in boot.wim from the download in this post but got the same results.
WoR-PE.log