-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Description
Operating system
Debian GNU/Linux 12 (bookworm) x86_64
Description
Hi! I hope everyone is doing well.
Although I'm still unsure if this is the best place, I'm coming to share a problem I experienced at the end of September.
I use this PC as a server so it's on 24/7, before going to sleep I turned off the container then when I woke up I realized something was wrong (I have Unbound and PiHole running but they were failing) so I entered the system and it was basically unusable, I could only move the mouse and not much else.
Thinking the Nvme died since it's relatively new, I physically restarted the PC and the system entered the BIOS because it didn't identify any boot disk, I tried a few things, but what ended up working was completely disconnecting the PC from the power outlet, discharging it, and reconnecting it, there it already detected the Nvme and I could use the system again.
As I'm very new to Debian and linux in general, with AI suggestions (sorry lol) and the commands I found on the internet to identify the problem but I didn't find anything in the logs that indicated what the error was (at least as far as I remember).
But if it sounds like anything to you, basically I experienced the problem of Windows Update that killed SSDs but... in Debian? :P
Now, the reason I'm writing here is that, I don't have Windows on this system (apart from that occasion when I used this container), the Nvme has been working without failures to date after the incident and shows good health (photos attached below) and the only difference is that I haven't used this container again.
Maybe I'm not understanding something but if I really had the Windows problem just by running it in a VM, I feel it shouldn't be possible for it to be transferred to my host system...
I add more information about my system, although at the time I was on Debian 12 and I recently updated to Debian 13. I would like to do more tests regarding the container but I'm afraid of tempting fate and ending up without my Nvme and all the problems that entails…
Docker compose
services:
windows:
container_name: windows
image: dockurr/windows
cap_add:
- NET_ADMIN
ports:
#- "192.168.1.3:6077:8006/tcp"
- "192.168.1.3:3389:3389/tcp"
- "192.168.1.3:3389:3389/udp"
volumes:
- './config/windows:/storage'
- './config/share:/data'
devices:
- "/dev/kvm"
- "/dev/net/tun"
networks:
AuroraNetwork:
ipv4_address: 192.168.3.99
env_file: windows.env
dns: 192.168.3.3
restart: unless-stopped
stop_grace_period: 5m
networks:
AuroraNetwork:
external: trueDocker log
N/AScreenshots (optional)
