Black screen after swapping gpu and disconnecting and reconnecting ssd's

After swapping my GPU from a GTX 1060 to an RTX 3060 and unplugging then re-plugging my 2 ssd’s I am unable to access manjaro. when trying to boot it just takes me to a black screen with a white underscore on top. So I thought it was the gpu so I swapped the GTX 1060 back, but the issue stayed.
The nvme has manjaro on it. While the 2 ssd have windows on it, only one works (crucial works, but the kingston one does not it was a failed attemp at a windows installation I think). I can still boot on windows with the RTX 3060. Also previously I had another RTX 3060, but with 3 fans this is one is 2 fans (for a future small build) and it worked fine.

Right now I booted from a live USB. I tried to reinstall grub with these 2 commands I mounted my nvme, -p /mnt/boot/efi and my sdc1 or windows ssd.

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --no-nvram
grub-mkconfig -o /boot/grub/grub.cfg

but it didn’t work. The output

sudo: unable to allocate pty: No space left on device
Installing for x86_64-efi platform.
Installation finished. No error reported.
sudo: unable to allocate pty: No space left on device

lsblk -f

NAME        FSTYPE   FSVER            LABEL            UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                                          0   100% /run/miso/sfs/livefs
loop1       squashfs 4.0                                                                          0   100% /run/miso/sfs/mhwdfs
loop2       squashfs 4.0                                                                          0   100% /run/miso/sfs/desktopfs
loop3       squashfs 4.0                                                                          0   100% /run/miso/sfs/rootfs
sda                                                                                                        
└─sda1      ntfs                                       0A1836E558CB39BF                                    
sdb                                                                                                        
├─sdb1      exfat    1.0              Ventoy           CE72-295B                                           
│ └─ventoy  iso9660  Joliet Extension MANJARO_KDE_2421 2024-12-16-11-21-39-00                     0   100% /run/miso/bootmnt
└─sdb2      vfat     FAT16            VTOYEFI          223C-F3F8                                           
sdc                                                                                                        
├─sdc1      vfat     FAT32                             0002-DBC1                              69.3M    28% /mnt/boot/efi
│                                                                                                          /mnt/boot/efi
│                                                                                                          /mnt/boot/efi
│                                                                                                          /mnt/boot/efi
│                                                                                                          /mnt/boot/efi
├─sdc2                                                                                                     
├─sdc3      ntfs                                       820A0B7A0A0B6A8D                                    
└─sdc4      ntfs                                       7838A51338A4D204                                    
nvme0n1                                                                                                    
└─nvme0n1p2 ext4     1.0                               8e0e212d-3399-41b6-9b0f-83f4032ed28f    352G    56% /mnt
                                                                                                           /mnt
                                                                                                           /mnt
                                                                                                           /mnt
                                                                                                           /mnt

inxi -Fazy

inxi -Fazy                                                                                                          ✔ 
System:
  Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_KDE_2421 quiet systemd.show_status=1
    splash driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: B550M Steel Legend
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: L3.46 date: 08/20/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech G304 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1740 min/max: 550/4663 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1740 2: 1740 3: 1740
    4: 1740 5: 1740 6: 1740 7: 1740 8: 1740 9: 1740 10: 1740 11: 1740 12: 1740
    13: 1740 14: 1740 15: 1740 16: 1740 bogomips: 108643
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ZOTAC driver: nvidia
    v: 550.135 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current
    (as of 2024-09; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 06:00.0
    chip-ID: 10de:1c03 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: N/A failed: nvidia gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: Unknown-1 mapped: DP-0 res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") modes: 1024x768
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.135
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
    memory: 5.86 GiB
  API: Vulkan v: 1.4.303 layers: 1 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1060 6GB driver: N/A device-ID: 10de:1c03 surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA GP106 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 06:00.1 chip-ID: 10de:10f1 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 08:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.12.4-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:8 chip-ID: 8087:0032
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Drives:
  Local Storage: total: 2.31 TiB used: 517.3 GiB (21.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B4QFXO7 temp: 39.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37480G
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0102 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: SanDisk model: USB 3.2Gen1
    size: 57.3 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.2
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-4: /dev/sdc maj-min: 8:32 vendor: Crucial model: CT1000BX500SSD1
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 061 scheme: GPT
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 34.2 C mobo: 33.5 C gpu: nvidia temp: 37 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 40%
Info:
  Memory: total: 20 GiB available: 19.46 GiB used: 6.17 GiB (31.7%)
  Processes: 333 Power: uptime: 1h 13m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 7.74 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1242 libs: 323 tools: pamac pm: flatpak pkgs: 0
    Compilers: N/A Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.36

fdisk -l

Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: KINGSTON SA400S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4987D8A8-A794-1B43-9111-0BD26A15FD7F

Device     Start       End   Sectors   Size Type
/dev/sda1   2048 937701375 937699328 447.1G Microsoft basic data


Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 980 1TB                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: 3B14A996-5D4E-4734-81AF-A0F0E1595CDA

Device         Start        End    Sectors   Size Type
/dev/nvme0n1p2  2048 1953523711 1953521664 931.5G Linux filesystem


Disk /dev/sdb: 57.3 GiB, 61524148224 bytes, 120164352 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x704e76c9

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *         2048 120098815 120096768 57.3G  7 HPFS/NTFS/exFAT
/dev/sdb2       120098816 120164351     65536   32M ef EFI (FAT-12/16/32)


Disk /dev/mapper/ventoy: 4.03 GiB, 4327022592 bytes, 8451216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device                   Boot   Start     End Sectors Size Id Type
/dev/mapper/ventoy-part1 *         64 8443023 8442960   4G  0 Empty
/dev/mapper/ventoy-part2      8443024 8451215    8192   4M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 90.12 MiB, 94494720 bytes, 184560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 1.13 GiB, 1213464576 bytes, 2370048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.84 GiB, 1972195328 bytes, 3851944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 858.86 MiB, 900575232 bytes, 1758936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000BX500SSD1 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3D8CE3E2-DD50-47C3-A34F-10B85B0421C9

Device          Start        End    Sectors   Size Type
/dev/sdc1        2048     206847     204800   100M EFI System
/dev/sdc2      206848     239615      32768    16M Microsoft reserved
/dev/sdc3      239616 1952002047 1951762432 930.7G Microsoft basic data
/dev/sdc4  1952002048 1953521663    1519616   742M Windows recovery environment

Better perform it exactly as described here:

Why did you unplug and replug your ssd’s when you changed your graphic card? Does not make much sense to me without further explanation.

Windoze usage can compromise affected partitions (“dirty bit”), maybe it was not properly shutdown? Did you unset all Fast startup options in Windoze properly?

In what modes (BIOS / UEFI) did you install all your OS’? Your drives sda and nvme0n1 seem to carry only one partition, so this looks like BIOS install on nvme0n1. In this case your grub-install command was wrong. On the other hand, Windoze on sdc looks to be installed in UEFI mode. On one computer these two install modes should not be mixed.

2 Likes

I have a little project going and i wanted to redesign the ssd shroud because it is too big. That’s why I unplugged it at first. I did that at the same time I swapped my GPU because I was already working on my pc.

To be honest I don’t recall in what modes they were installed. You are probably correct but I don’t know.

I will add that it isn’t the first time that I unplugged and re plugged my ssd’s this issue is new to me.

I think take your time to sort out what your plans are. You need to decide on what partition or disk you would like to keep what system. If one is broken I would dump it after backing up still valuable data. If you want to start both, Manjaro and Windoze via grub’s boot menu they need to be installed in the same mode. This only can be achieved by a re-installation of one of the systems if indeed they differ.

Yeah you are probably right but it’s weird that grub worked a day ago and not anymore. But right now even if i unplug the windows ssd it will still not boot.

We don’t know all the details involved in your specific case, does not matter much anyhow. It could be that you still can boot Manjaro from your firmware in legacy mode. Or you have the ESP linking to the single partition on nvme0n1 placed in sdc, who knows. There are many weird possibilites unfortunately working for a while.

Here is a good tutorial how to do it right:

it’s in UEFI not legacy.
I will also say that my windows drive is sdc the sda drive is a failed drive it should have nothing on it.
They are all gpt.

Why you have no ESP on nvme0n1 then if you believe it’s installed in UEFI mode? Where is it? Technically it’s possible to place it on another disk but this is then an out-of-spec installation, prone to fail.

Its on the sdc

In this case you could create an ESP on nvme0n1, chroot via the wiki entry and restore the boot loader. It’s important to mount the newly created ESP in this process. Ideally, all the other disks are unmounted.

oke I will try it. Do the links you provided have the steps needed?

Here is a description how to create the ESP (it’s simply a FAT32 formatted partition with a size of 300 MiB or larger and flagged “boot”).

When you are in manjaro-chroot environment (based on a LIVE ISO boot) only make sure that the newly created ESP is mounted to make sure it’s really used:

mount /dev/nvme0n1pXY /boot/efi

where /dev/nvme0n1pXY needs to be replaced by the exact device name of your newly created ESP.

Then restore the boot-loader still within chroot environment.

Then you need to select the new ESP in your firmware to make sure it’s used in the boot process. Reboot.


At the end you can create the Windoze entry in the grub boot menu by re-enabling os-prober in the file /etc/default/grub (followed by command sudo update-grub).


:warning: I would recommend you to study the process first, I’m not going to list here all the detail commands. :warning:

Thanks for your help!

1 Like

Additionally, you might discover useful takeaways from:

First time I’ve seen this. Did you boot into Windows with the other storage disconnected? Cables/connectors securely seated?

Does sudo parted -l show any more partiitions? Or a grahical partition manager such as KDE Partition Manager or GParted?

It’s also possible the drive is now faulty, maybe zapped with static? Easily done.

ETA: Very poor connection here, page didn’t reload until after posting.