serverfault.com

I have an ST12000NM0127 12TB SATA drive. It's documented as having a "Formatted capacity" of 12000GB (12TB), "Guaranteed sectors" 23437770752 for 512 bytes logical sector, that is 12000138625024 bytes (0xAEA00000000). This precisely matches SFF-8447. However my drive has a 0.01% larger capacity of 12001339219968 bytes (0xAEA478FA000), e.g.: Get-Disk | Select-Object FriendlyName, Size, LogicalSectorSize, PhysicalSectorSize FriendlyName : ST12000NM0127 Size : 12001339219968 LogicalSectorSize : 512 PhysicalSectorSize : 4096 I'm worried that if I buy a 12TB drive from another brand, it will have the capacity mandated b

I have a Windows Server 2022 Active Directory, and a network share on Windows Server 2022. Endpoints are Windows 11, and we are using Bitdefender Endpoint Security. The problem: One user can't save Excel files on a network share. Saving a file results in a nonsensical error message The document has not been saved. Save it as if the problem still exists. The first part I understand the second part makes no sense, but it could mean "save it as a new file". I checked the permissions with Effective Access and everything is green. The problem appears randomly when saving Excel files to a network location. Other users don't have the problem. The user can create new files, save as a new file, but when the problem appears, the newly opened saved as file can no longer be saved. Saving a file may work 5 times in a row or fail the first time. When the error occurs, saving a new file w

'I upgraded a VM from Debian 9 (Stretch) to Debian 12 (Bookworm). sssd.service itself is active, but after reboot I see all the SSSD sockets as failed: systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● sssd-nss.socket loaded failed failed SSSD NSS Service responder socket ● sssd-pam-priv.socket loaded failed failed SSSD PAM Service responder private socket ● sssd-pam.socket loaded failed failed SSSD PAM Service responder socket ● sssd-ssh.socket loaded failed failed SSSD SSH Service responder socket ● sssd-sudo.socket loaded failed failed SSSD Sudo Service responder socket However the main service looks fine: systemctl status sssd.service ● sssd.service - System Security Services Daemon Loaded: loaded (/lib/systemd/system/sssd.service; enabled; preset: enabled) Active: active (running) since Mon 2025-08-25 11:39:14 CEST; 39min ago Main PID: 54436 (sssd) Tasks: 6 (limit: 8662) Memory: 61.6M CPU: 1.323s CGroup

I run a PHP 8.1 Laravel application on an Apache server. The same server also runs a Node.js API (separate subdomain). The site is behind Cloudflare. The issue: The site randomly goes down for 10–20 minutes, then comes back without me doing anything. During downtime, the Laravel site is inaccessible and Node.js APIs return Cloudflare 522 (connection timeout). Sometimes the APIs work when tested directly with Postman, but the Laravel frontend is down. I confirmed this with Uptime Robot monitoring, which shows repeated outages. Laravel logs during downtime: [2025-09-01 04:27:35] production.ERROR: Product Detail Error: cURL error 56: Recv failure: Connection reset by peer for http://ip-api.com/json/52.167.144.238 [2025-09-01 04:28:39] production.ERROR: API Request Error: Server error: POST

Have a question regarding formatting HDD using PSID. I purchased two Western Digital 14 TB SATA HSH721414ALE6M0 hard drives. I want to reformat the drives and use them in my mac (APSF). They were used in a Linux host. The seller says that they are both compatible with btrfs & f2fs, hinting Linux only. I can't just plug&play on Mac. Would it be possible to create a bootable Ubuntu USB stick and boot my pc from it, use sedutil-cli with PSID to erase the drive (sudo sedutil-cli --yesIReallyWantToERASEmyDriveWithPSID XXXXX-XXXXX-XXXXX-XXXXX /dev/sdX)? The letter "E" in HSH721414ALE6M0 stands for Encryption and clues that the drive supports the security commands that allow me to use PSID revert function.

On an Ubuntu 24.04 google compute engine VM, Apache 2.4, the following warning is in the apache logs: [ssl:warn] a.b.c.d.bc.googleusercontent.com:443:0 server certificate does NOT include an ID which matches the server name IP address a.b.c.d is assigned to myserver.example.com, and a.b.c.d.bc.googleusercontent.com is not the server name. I recently set the server name in /etc/hostname; the file was formerly missing. nslookup myserver.example.com both from inside the google compute engine private network and from outside yield a.b.c.d. dig -x a.b.c.d yields a.b.c.d.bc.googleusercontent.com from both inside and outside. None of my certificates are for that server name. Is there a "proper" way to resolve this warning, or just ignore it? Where is the a.b.c.d.bc.googleusercontent.com certificate coming from, and where is it stored on my machine?

I'm having issues removing old tenants from my Entra. Two are old tenants that I no longer need. And another 2 are for linking to other Company's entra. If I click the checkbox next to one of the tenants then delete it asks me to MFA which I cannot. I upgraded to a new phone losing my MFA links for these to authenticate and remove. I tried using my newly created (with the same ID) MFA, but that does not authenticate. And I don't have another method to MFA on those tenants. It should be a lot simpler than this... How can I remove these tenants now that I no longer have the MFA to remove them? Edit: I was able to leave one of the tenants. But I still need MFA to leave the others.

I've got three websites being served from a CentOS 9 Stream instance. All have SSL enabled So, siteone.com sitetwo.com sitethree.com both work fine, on http (port 80) The issue is that https://sitetwo.com and https://sitethree.com display https://siteone.com on https (port 443) I have one public IP address available and use SOPHOS as a firewall <IfModule mod_ssl.c> <VirtualHost *:443> ServerName www.siteone.com DocumentRoot /var/www/siteone/html ServerAlias siteone.com ErrorLog /var/www/siteone/error.log CustomLog /var/www/siteone/requests.log combined SSLEngine on Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/xxxxx/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/xxxxx/privkey.pem </VirtualHost> <IfModule mod_ssl.c> <VirtualHost *:443> ServerName www.sitetwo.com DocumentRoot /var/www/sitetwo/html ServerAlias

I have several SAS hard drives that were previously in a hardware RAID. I reflashed an LSI 9211-8i controller to IT mode following: https://forums.serverbuilds.net/t/guide-updating-your-lsi-sas-controller-with-a-uefi-motherboard/131 which worked. The controller is recognized by the system everywhere. The problem is the SAS disks appear but I cannot access them using System Rescue, Ubuntu Live, or Windows PE. Under System Rescue, I tried lsblk, lsscsi, sg_map, and sg_inq, but am unable to access the disks. I installed OpenSeaChest-Basic under Ubuntu Live, but was unable to access the disks. The same was true under Windows PE with Disk Management and Diskpart. I tested another PCIe slot, another 9211-8i (I have 4, with 24x 10TB SAS hard

I have a user data script that changes the SSH port on an EC2 machine to 9000 to make way for a podman bastion container on port 22. This worked fine for several months, until today when it didn't. No changes to the script prior to this, and the EC2 AMI is Ubuntu LTS, so I am scratching my head as to what could have changed. I have added set -x to the top of the script and a few echos of command outputs, and I can see systemd is listening, but it doesn't connect to ssh. The sleep and extra restarts were added today to see if it was a timing issue. The ListenStream= is the official way to clear an existing port 22 binding. First the relevant bits of script: # --------------------------------------------------------------------------------------------------------------------- # RECONFIGURE HOST SSH TO PORT 9000 # ------------------------------------------------------------------------------------------------------