Search results

Testing a windows 11 iot enterprise ltsc VM and every time I shutdown the server cold when I restart I do not get a display, at first it looks like it's frozen here, but the machine is up and running as I can use remote desktop and get into it. Failed boots look like this spinning dots It...

Well I found my future server CPU... Can't wait for this... Next month maybe? hopefully will work in Proxmox? :) EPYC 4344P maybe.

Check the real root /mnt you may have written to it before it was mounted... To do that, #umount /mnt then go into /mnt and use the ncdu or df and see whats in there, surprise surprise? Try unmounting /mnt then checking the real root /mnt

Can you " cd /" and run ncdu (You are currently in /root)

apt install ncdu then run ncdu and see where the space is being used.

Balloon off will help regardless but if its this sluggish must be something else, I wonder if you install a clean windows with nothing. Must be something with the gpu?

Whats the cpu usage / etc in task manager inside the VM? ie whats using the % .. Could it be doing any updates?

I've been applying updates so it probably got overrwritten. If it is coming then I am fine with waiting, I thought it was already live and maybe it was reversed. Thank you!

The latest backup-client update caused this to fail again (April 2, 2024)

You were on to something when you tried the read only.. just that message wasnt good.. was thos zfs damaged when removed somehow...

Thank you the provided test fix worked in the other thread!!

Thank you this worked!!

Hi, thanks. Just to be clear I am overwriting the standard files with this? Should I backup the old ones.

Try : zpool import -f -FX bulk_storage -n was dry run

lsblk -f ? zpool import -f -FXn bulk_storage ?

zpool import -f bulk_storage ?

Cannot do file level restore on one partition. I have a windows 2003 server C:\ D:\ Two partitions on 1 disk I cannot do file restore. root@pve-art2:/# mount /dev/loop0p2 /mnt/test mount: /mnt/test: wrong fs type, bad option, bad superblock on /dev/loop0p2, missing codepage or...

Bah, I am getting this too: (device loop0p2): ntfs_read_inode_mount(): Failed to lookup $MFT/$DATA attribute extent. $MFT is corrupt. Run chkdsk. [4434021.036282] ntfs: (device loop0p2): ntfs_read_inode_mount(): Failed. Marking inode as bad. [4434021.036572] ntfs: (device loop0p2)...

How much does server have? Did u try processor type change?

If proxmox is crashing its using too much memory. Reduce the memory perhaps. Also, try setting Processor type to x86-64-v2-AES on the windows 11 virtual machine.