Step 1.) Upgrade to Debian 11 first The process to go to Debian 12 is not as smooth as 11, when trying to upgrade from Debian 10. In fact, it doesn't work directly, so you'll first need to follow this guide to update to Debian 11, reboot and come back here if successful. Step 2.) Update sources.list Update your /etc/apt/sources.list like this: deb http://........

If you are installing ta-lib for Python and get this error then you can normally solve it by manually getting the ta-lib source files and compiling. tar -zxvf ta-lib-0.4.0-src.tar.gz cd ta-lib;./configure;make;make install Collecting ta-lib Downloading https://files.pythonhosted.org/packages/39/6f/6acaee2eac6afb2cc6a2adcb294080577f9983fbd2726395b9047c4e13ec/TA-Lib-0.4.26.tar.gz (272kB) &nbs........

Debian based OS's have a similar issue as the behavior in RHEL/CentOS dhclient, which is that if you have an interface that relies on DHCP, if the first attempt fails, it will quit and stop. This is a problem especially if you are using your Linux as a router or something else mission critical, but where the internet for some reason may have been down or the DHCP server it gets a lease from broken. The expected behavior you would hope is that when things are back online that the........

Most newer distros inexplicably cause your NIC to have what Icall "random" non-standard name conventions because of systemd. This is a big problem for many people and especially those running servers. Imagine that you have a static IPconfigured for ens33 but then the hard disk is moved to a newer system, the NIC could be anything from ens33 to enp0s1, meaning that manual intervention is required to go and update the NIC config file (eg. /etc/network/interfa........

If you can print other PDFs but not a particular one it is very likely that the PDF size is A4 (the longer, skinnier Asian paper size) instead of the North American letter size ( 8.5" x 11"). This breaks printing in most cases. Or it may print if you find a program that ignores the size issue. Here is an example of an A4 being rejected by a printer in Ubuntu Linux via CUPS Cannot print PDF CUPS Samsung C460: Processin........

sudo pip3 install python-docx [sudo] password for : Downloading/unpacking python-docx Downloading python-docx-0.8.10.tar.gz (5.5MB): 5.5MB downloaded Running setup.py (path:/tmp/pip_build_root/python-docx/setup.py) egg_info for package python-docx no previously-included directories found matching 'docs/.build' warning: no previously-included files matching '.DS_Store' foun........

This is a VIA made VL805 USB 3.0 Chipset with 4-ports and MOLEX powered. First of all this unit was cheap at about only 9 USD with fast shipping. My biggest concern was if this was a quality unit and would it really give you full USB 3.0 speeds (some people reported with similar cards that for some weird r........

In short the two drives in the array were /dev/sdd and /dev/sde. The kernel sees they were unplugged and have gone down as you can see below. mdadm caught the first one being unplugged /dev/sde and disabled the missing drive. However when the final drive that was part of the array is unplugged it didn't notice at all. Instead it complains about an IO error later for drives that the kernel knows do not exist anymore. [45817.162728] ata4: exception........

Remove the failed partition /dev/sde1 mdadm --manage /dev/md99 -r /dev/sde1 mdadm: hot removed /dev/sde1 from /dev/md99 Now add another drive back to replace it: # mdadm --manage /dev/md99 -a /dev/sdf1 mdadm: added /dev/sdf1 A "cat /proc/mdstat" should show it resyncing if all is well.........

[3805108.257042] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257052] sd 0:0:0:0: [sda] Write Protect is off [3805108.257054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3805108.257066] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3805108.257083] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257090] sd 0:0:0:0: [sda] Write Protect is off........

Dell CS24-NV7 Unusually the Virtualization was enabled when I got this server but all the NICs were diabled in the BIOS including PXE boot! Advanced -> Advanced Chipset Control PCI Slot 1 Option ROM: Enabled Onboard LAN1 Control: Enabled LAN1 Option ROM Scan: Enabled (you need it for PXE boot) Onboard LAN2 Control: Enabled LAN2 Option ROM Scan: Enabled *you will need to reboot and........

./configure ./configure: cannot locate gcc 3.x. please install it or specify with --qemu-cc yum -y install gcc make ./configure ./configure: cannot locate gcc 3.x. please install it or specify with --qemu-cc yum -y install compat-gcc-* ./configure Error: Could not find alsa Make sure to have the alsa libs and headers installed. yum -y install alsa-lib-devel ./configure........

Have you ever unplugged the wrong drive and then had to rebuild the entire array? It may not be a big deal in some ways but it does make your system vulnerable until the rebuild is done. Many distros often enable the "bitmap" feature and this basically keeps track of what parts need to be resynced in the case of a temporary removal of a drive from the array, this way it only needs to sync what has changed. To enable bitmap to speed up rebuilds and sync........

[1433128.139339] sd 5:0:1:0: [sde] Unhandled error code [1433128.139343] sd 5:0:1:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [1433128.139348] sd 5:0:1:0: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [1433128.139360] end_request: I/O error, dev sde, sector 0 [1433128.139410] sd 5:0:1:0: [sde] Unhandled error code [1433128.139414] sd 5:0:1:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [1433128.139420] sd 5:0:1........