Recent content by Mikesco3

Thank you uzumo... I just plugged in what you said into ChatGPT and I learned that the > Samsung SMART RAW_VALUE=79 is not 79% wear and that I should be going by the normalized Value... I'll look into changing that... Thank you for sharing that!!

Can you explain this a bit more... ? I'm the one that wrote the script, and I would totally love to improve it if that's the case...

I checked and there is no Samsung Magician tool available for Samsung Evo Drives... I even tried to download the only Linux tool I saw under Samsung Magician software (even though it said it's only available for DC drives) and predictably it didn't detect my Samsung Drive... All of that being...

Hi I just wanted to share this because of the potential of this impacting more people, and there is the small possibility that I might be wrong... I have a 1TB Samsung 870 EVO Sata SSD. Proxmox is reporting the Wearout Value to be 4% However when I go to get he smart values, it is showing 79%...

I was experiencing random weird hangups on proxmox with a Samsung SSD 990 PRO 2TB. Fortunately the 990 Pro was on it's own zfs pool but not storing the OS on it... I'm just posting in case my solution helps anyone... I ended up flashing the Samsung NVME firmware from Linux: Download the...

Hi, I know I'm probably way late to your problem... but I'm also posting this for if someone else has had this issue as well... for me the Solution ended up involving: Boot into Proxmox from a Live install media, then once you are on the screen where it is asking to accept, press ctrl+alt+F1...

Thank you for the reply

Hi Everyone... I've already tried searching a bit on the forum and the Proxmox documentation. I want to ask for some clarification about the "block size" (ashift) value suggested on the Proxmox Web Interface when adding or creating ZFS pools. Lately, the UI has been suggesting a 16k block...

1. On start menu GRUB. Edit grub command line (press e key ) from: initrd=\EFI\proxmox\5.3.18-3-pve\initrd.img-5.3.18-3-pve BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw quiet splash=silent to: initrd=\EFI\proxmox\5.3.18-3-pve\initrd.img-5.3.18-3-pve root=ZFS=rpool/ROOT/pve-1...

What ended up working for me was to run the windows repair script from the christitus tech tool: Run within an elevated powershell irm "https://christitus.com/win" | iex Then go to the tab Config and click System Corruption Scan Let that run for a bit, reboot the VM remove any virtio and...

Nice Job!! Is there a possibility this tool to use syncoid for migrating in the cases where the VMs are using ZFS on both sides of the migration? It is waaaaay faster and it also has the bonus of preserving any zfs dataset snapshots... I apologize in advance if this has been asked a million...

Yes!!! Totally agree... I just have experienced two of my servers go into a degraded state, and thank God for notifications, else I would have been in deep water...

Same here... I have a Windows 10 VM and I'm trying to set a resolution of 1600x900. When I go to set the resolution in the OVMF BIOS I get the same error posted in the picture. I've tried: - Creating a new VM in OVMF Q35 type and moving the windows disk over. and when I created the UEFI...