Automatic deletion of partitions in primary SSD

Hi, I'm using Garuda KDE Dr460nized for a month.

yesterday I updated my system regularly and tried to shutdown but it failed with some errors. I wasn't able to copy the error, so I clicked picture of it (I attached it below). I turned off by long pressing the power button. when rebooting again I pops up NO BOOTABLE DEVICE FOUND. where I found the partitions of primary disk (ssd) was deleted completely. inside bios the ssd found as brand new without any partitions. Everything lost. surprisingly my secondary drive was also deleted completely. I don' t know why. my files and programs was lost. I wasn't able copy the earlier system specs. I am using lenovo legion 5i. I reinstalled the garuda os again. I need a reliable remedy. down here i pasted my current system specs.

  Kernel: 6.2.2-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=e0515285-b865-4077-a6d9-c5750353ceda
    rw [email protected] quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=66d2e84f-5fdf-42f0-bf64-a14db45a3616 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.2 tk: Qt v: 5.15.8 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: LENOVO product: 82AU v: Lenovo Legion 5 15IMH05 serial: <superuser required>
    Chassis: type: 10 v: Lenovo Legion 5 15IMH05 serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0Q55722 WIN serial: <superuser required> UEFI: LENOVO
    v: EFCN57WW date: 09/05/2022
  ID-1: BAT0 charge: 42.8 Wh (83.9%) condition: 51.0/60.0 Wh (85.0%) volts: 17.2 min: 15.4
    model: SMP L19M4PC0 type: Li-poly serial: <filter> status: charging cycles: 783
  Info: model: Intel Core i5-10300H bits: 64 type: MT MCP arch: Comet Lake gen: core 10 level: v3
    note: check built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 2
    microcode: 0xF4
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2500 min/max: 800/2500 scaling: driver: intel_pstate governor: powersave
    cores: 1: 2500 2: 2500 3: 2500 4: 2500 5: 2500 6: 2500 7: 2500 8: 2500 bogomips: 39999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: NVIDIA TU117M vendor: Lenovo driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm
    non-free: 525.xx+ status: current (as of 2023-02) arch: Turing code: TUxxx process: TSMC 12nm FF
    built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f99
    class-ID: 0300
  Device-2: Syntek Integrated Camera type: USB driver: uvcvideo bus-ID: 1-6:3 chip-ID: 174f:244c
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 compositor: kwin_x11 driver: X:
    loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.43x7.52") s-diag: 391mm (15.39")
  Monitor-1: DP-2 res: 1920x1080 hz: 120 dpi: 142 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.55") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
    direct-render: Yes
  Device-1: Intel Comet Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
  Device-2: NVIDIA vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
  Sound API: ALSA v: k6.2.2-zen2-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.66 running: yes
  Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:06f0 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 08:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp8s0 state: down mac: <filter>
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:6 chip-ID: 8087:0026
    class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
  Local Storage: total: 953.88 GiB used: 18.63 GiB (2.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Silicon Power model: SPCC M.2 PCIe SSD
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: V0523B
0 temp: 58.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: PC SN730 SDBPNTY-512G-1101
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 11130001 temp: 40.9 C scheme: GPT
  ID-1: / raw-size: 467.84 GiB size: 467.84 GiB (100.00%) used: 18.63 GiB (4.0%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:2
  ID-3: /home raw-size: 467.84 GiB size: 467.84 GiB (100.00%) used: 18.63 GiB (4.0%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-4: /var/log raw-size: 467.84 GiB size: 467.84 GiB (100.00%) used: 18.63 GiB (4.0%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:3
  ID-5: /var/tmp raw-size: 467.84 GiB size: 467.84 GiB (100.00%) used: 18.63 GiB (4.0%) fs: btrfs
    dev: /dev/nvme0n1p2 maj-min: 259:3
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    maj-min: 259:4
  ID-2: swap-2 type: zram size: 7.67 GiB used: 2.09 GiB (27.3%) priority: 100 dev: /dev/zram0
  System Temperatures: cpu: 54.0 C pch: 47.0 C mobo: N/A gpu: nvidia temp: 49 C
  Fan Speeds (RPM): N/A
  Processes: 290 Uptime: 4h 32m wakeups: 35812 Memory: 7.67 GiB used: 4.47 GiB (58.2%)
  Init: systemd v: 253 default: graphical tool: systemctl Compilers: gcc: 12.2.1 Packages:
  pm: pacman pkgs: 1325 libs: 351 tools: gnome-software,octopi,paru Client: shell wrapper
  v: 5.1.16-release inxi: 3.3.25
Garuda (2.6.15-1):
  System install date:     2023-03-11
  Last full system update: 2023-03-12 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:            

As I am new user, i am unable to upload pictures. I given my drive link (photo) below.

This would be a bug of the greatest magnitude if Garuda or Arch were responsible for this. However, I find that highly unlikely (although not completely impossible), as this type of serious problem would receive much exposure if it was happening to other Garuda/Arch users.

This sounds more like a virii or malware attack of some sort. Of course a forced shutdown can have serious consequences depending on what type of operation is in progress at the time. Were you running any programs that are used for formatting or partitioning drives at the time? Forcing a shutdown during a system update can result in an unbootable system, but I know of no instances that have resulted in wiping connected drives.

Kernel regressions do occur at times, but I doubt something as serious as your report could slip through kernel testing.

Do you dual boot windows?

It would also be useful to list your drive information and post the output to the forum.

Please post the output of:

blkid -o list 

Welcome to the Garuda forum. :wave:


I agree, it seems very unlikely the data was wiped from the disk. "Wiping" data from a disk actually involves writing to the disk again; you don't truly delete data from a disk, as much as you write on top of the data that's already there. It is not something a computer can do when it is not powered on.

Corrupting a file system or partition table by forcing a shutdown while the drives are mounted is very common. It is exactly the reason they tell you not to do it. It sounds like it is a little late now, but it is often possible to recover a system with a corrupted filesystem.

These are a few examples that just happened to be on the top of a Whoogle search:

Hopefully there won't be a "next time", but if there is I would not be so quick to reinstall.


I shut it down after the update completed successfully. and I am using one primary OS - Garuda linux, not dual booting. If it is virii or malware, could you please suggest some free antivirus software for linux to wipe it out.

output for <blkid -o list>:

device fs_type label mount point UUID

/dev/nvme0n1p2 btrfs (not mounted) e0515285-b865-4077-a6d9-c5750353ceda
/dev/nvme0n1p3 [SWAP]
/dev/nvme0n1p1 /boot/efi
/dev/nvme1n1 (not mounted)
/dev/zram0 [SWAP]

I have never encountered any virii using Linux with that type of destructive capability. Windows virii are different story, that was why I enquired if you were using Windows.

If you have already overwritten your prior installation there will be little use in running a virus scan as it should no longer be present (if there was one in the first place). If you feel the need to run a Linux based AV you can install the free ClamAV utility. It tends to identify a lot of false positives IMO. I mostly used it in the past for scanning my Windows installations/drives for virii. Linux is still pretty safe from malware threats as long as you follow safe computing practices. There is generally little need to worry about Linux becoming infected the way Windows frequently does.

As @BluishHumility already stated this was probably a case of corruption of your file system caused by a forced power down. I have never had this misfortune, although I have suffered drive damage from a power outage in the past. If your partition tables were corrupted rendering your drives unreadable there is free Linux software (testdisk) to help with that. Unfortunately, having overwritten your drives, it's a little late for recovery efforts now.


yes. I have already installed clamav, which way would more appropriate-scanning the home or root directory?. The similar problem occurred when I was using (windows 10) 2 months ago. I replaced my old nvme ssd with new sp silicon ssd. More than a month there was no such conflicts. I believed the problem is with old ssd ,the same were told by the customer care lenovo legion. Again it happened with some new errors. so i intrigue to root cause.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.