A couple of things I ran into. You need to make sure that you switch to BIOS to UEFI or it won't recognize that there is anything to boot to.

And you have to choose something other than VIRTIO for the controller. Because it's likely that there aren't VIRTIO drivers installed you have to use something else.

You can't install drivers to a device you don't have so...

You can add a 2nd hard drive to the mix as VIRTIO to get Windows to ask for drivers, then you can shut down, trash the 2nd HD and make your main disk use the VIRTIO controller. Obviously use the VIRTIO drivers for the other unknown devices that pop up and you are good to go.

Ok, it looks like I just need to import it and adjust it in Windows and then in proxmox when I am done.

It looks like it's easy to change: https://www.thegeekdiary.com/how-to-enable-the-automatic-extension-for-a-thin-lvm-volume/

But, if it auto extends, what tells it that there is a hard limit? The side of the drive you set up when making the VM?

It can't auto extend to infinity.

root@spwj-phy:/mnt/usbdest# qm importdisk 100 vm-100-Apps.qcow2 local-lvm
importing disk 'vm-100-Apps.qcow2' to VM 100 ...
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "vm-100-disk-0" created.
WARNING: Sum of all thin volume sizes (1.95 TiB) exceeds the size of thin pool pve/data and the size of whole volume group (1.63 TiB).
transferred: 0 bytes remaining: 2147483648000 bytes total: 2147483648000 bytes progression: 0.00 %

Googling what to do now...

On most proxmox installs it sets the local storage at 100 GB. This seems to be the filesystem and any ISO's. Most of our installs only use about 8 GB for this (I know I can remove the ISO's after install)

Obviously some is used for swap and then it essentially uses the rest for local-lvm.

I'm trying to figure out what I need to change in order to have it use less space for the local storage.

For the most part I 'think' I understand the information in 2.3.1 of the admin manual: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#installation_installer

The hdsize is the max amount you want to use at all
Swap size is usually 4 to 8 GB
Maxroot - I think this corresponds to the local storage that in most of our deployments is using 100 GB. Setting this at something low like 20 GB should be sufficient and even maybe overkill... (I think)
Min Free - default is 16 GB (I don't know if I should set it as something different)
Max VZ - This is the one I am really confused on. Does this correspond to the local-vlm that it normally creates?

I am a bit over my head as @scottalanmiller often helps with our Proxmox deployments but he's out of pocket.

@Pete-S said in Ubuntu DDE Spanish Characters:

Change your keyboard settings to the English US international. You'll get some additional AltGr+key combinations for Spanish and other languages.

Thanks!

I'm looking for a way to type Spanish tildes / accents, etc. in Ubuntu DDE. In Ubuntu Gnome there is a Gnome Tweak tool, but I am not finding anything like for DDE.

@marcinozga said in Power in Qatar:

I checked few power supplies in office pcs, every single one accepts 100-240VAC 50-60Hz input. So they will work anywhere. I haven't seen one in years that would be limited to 110 or 230 (or others) only.

Nice, thanks!

https://forums.lenovo.com/t5/Displays-Options-and-Accessories/Using-AC-Adapter-Internationally/m-p/149222?page=1#149224

Looks like Lenovo is the same. I don't know why I was making it so difficult.

I suppose server would be the same then?

We have a client in Qatar. I believe they are on 240 V / 50 Hz.

I recall back in the day that computer power supplies used to have the 120/240 (or was it 220) switch on them.

The new power supplies I think are auto sensing.

Is it really just a cable that is the difference? In other words if I move to Qatar and take my PC with me, do I just need a new cable?

@dbeato said in Known issue with Unifi Access points and 4.3.24.11355 FW:

New Firmware released supposedly to address this
https://community.ui.com/releases/UAP-Firmware-4-3-28/a02af414-6665-4c57-ac03-6e4dac8317e1

Improvements

• [UAP] Add support for adoption of UniFi SmartPower Strip (Early Access).
  *[UAP] Improve DHCP compatibility, especially when using third-party or non-UniFi DHCP Servers.
  Bugfixes
  *[UAP-G2] Fix intermittent broadcast and multicast packet drop on gen2 APs, introduced in 4.3.24. This impacted users with non-UniFi DHCP servers which use broadcast for DHCP, along with IoT devices that rely on multicast for discovery.

It looks like tons of complaints with that release as well.

@jameswatt said in Known issue with Unifi Access points and 4.3.24.11355 FW:

@CCWTech did it end up being unrelated?

I think so. Everything seems to be stable on the RC version. We have switched clients to the RC and they are not having issues any longer.

@jameswatt said in Known issue with Unifi Access points and 4.3.24.11355 FW:

@CCWTech said in Known issue with Unifi Access points and 4.3.24.11355 FW:

This is supposed to fix the issue: https://community.ui.com/releases/UAP-Firmware-4-3-26-11358/e05cd041-ea54-460c-85f4-7f3fd97261e8?page=8

I just installed this today. Thanks.

I had previously rolled back the firmware, but that didn't permanently fix the issue. It was still happening.

Hoping that this new firmware fixes it.

I had an issue last night but not sure if it was related. I'm on the RC firmware.

Welcome @ErnieT75

@Dashrender said in HPE Smart Array P408i-a SR Gen10 Error 1716:

@CCWTech said in HPE Smart Array P408i-a SR Gen10 Error 1716:

Are they SSD or Spinners? If they are spinners this is a great time to get away from RAID5.

LOL - you mean it's a great time to get away from spinners

I know there are still cases for spinners. We can only hope this system is ancient since it's running RAID 5 on spinners, so we should be able to assume the drives are tiny - easily replaced by two SSDs in RAID 1.

That as well! But at the very least no RAID 5 if you are re-using drives. But all my new server builds are SSD for sure.

Are they SSD or Spinners? If they are spinners this is a great time to get away from RAID5.

This is supposed to fix the issue: https://community.ui.com/releases/UAP-Firmware-4-3-26-11358/e05cd041-ea54-460c-85f4-7f3fd97261e8?page=8

@jclambert I just can't believe Ubiquiti hasn't fixed things yet and the FW is still available as the current version.

Microsoft has acknowledged the Windows 10 bug that is causing PCs to crash when running the Check Disk tool, and it has rushed out a fix, underlining just how serious this problem is. In its list of known issues for Windows 10 updates KB4592438 and KB4586853, the company explains how users can fix their PC if they fail to start up after crashing:

The device should automatically start up into the Recovery Console after failing to start up a few times.
Select Advanced options.
Select Command Prompt from the list of actions.
Once Command Prompt opens, type: chkdsk /f
Allow chkdsk to complete the scan, this can take a little while. Once it has completed, type: exit
The device should now start up as expected. If it restarts into Recovery Console, select Exit and continue to Windows 10.
This should allow your PC to start normally. The company is also rolling out a fix for the error, which should reach users of Windows 10 in the next 24 hours, and as it's an automatic update, you won't need to do anything to apply the fix.

https://www.techradar.com/news/new-windows-10-bug-appears-to-break-one-of-its-most-important-tools