Disk is not detected in Fedora 43 Live USB (No AHCI mode option)

My issue is pretty self explanatory: I can’t see my disk anywhere in my live USB, while it does show in Windows, this means I can’t install Fedora.

The default installer shows no disks available, and the KDE Partition manager shows my USB and zram0 for some reason?

I tried looking around and most solutions involved changing the disk mode to AHCI, but I couldn’t see any option for it in my bios.

I have a Honor laptop from around 2022 although I’m not sure about the exact model. I tried updating my bios, but the official guide mentioned either using the device manager app through the driver update tab which marked all drivers as up to date.

I should probably also mention that the bios itself or Windows sometimes don’t detect the SSD, especially after restarting. Shutting down also doesn’t seem to work properly, as the screen stays black but I can tell my laptop is still on since the fans keep running. I need to force it to shut down by holding the power button. If I turn it on immediately after, I get a Failed to boot or No boot device found error, and the bios shows no disks. I can usually fix this by turning off the computer again, waiting for a minute and two and then turning it on again (sort of like a power cycle except I have to force my computer to shut down). After that, the disk does get recognized by the bios and I can boot into Windows.

Booting into the USB also causes the disk to be “unloaded” (I’m not really sure how to call this), as Windows does show in the boot menu (but in the issue I mentioned before it doesn’t and I just see no boot options).

Also I didn’t use this computer for 3 years as it wasn’t charging since the charging port broke. We did repair it once, but it stopped working about a week later, I got lended a computer and stopped using this laptop until a few days ago when I got it repaired. This laptop never gave me any issues like this until now.

I had also installed Linux on it previously, I had 4 operating systems installed: Zorin, Kali, Fedora, and Windows (Don’t ask, I don’t know what I was thinking back then). Oddly enough, in grub the only boot options were Zorin and Kali, and Fedora wasn’t visible. I tried reading my fedora files on zorin but they didn’t show in the file explorer, and in Windows using this linux reader did allow me to see my files in Zorin and Kali, but not in Fedora, where it got stuck reading until 96% and then froze. Kali also couldn’t boot and showed an error.

Anyways I thought that they might be causing issues so I got a few files that I wanted to back up, and then deleted their partitions, with Fedora first, thinking they might’ve gotten corrupted somehow and that was causing the issue. I also removed the grub instances from all 4 and stayed only with Windows. This still unfortunately didn’t fix the issue though, I couldn’t install Fedora and was also stuck with Windows now. I wanted to delete my whole disk and reinstall Windows, so I tried making a Windows installer USB and didn’t meet the Windows 11 upgrade requirements?? (I was inside Windows 11). I decided to just settle for a reset, it took a bit of babysitting since I had to force my computer to turn off, then wait, then turn it back on each time it had to restart but then it was done.

That leads you up until now, where I still have the disk issues, and Fedora doesn’t detect my disk. I’m a bit lost on what to do now so I need help. I have safe boot off, and I also didn’t see any option to change the disk mode to AHCI which seems to fix the issue for most people.

Someone mentioned that sometimes it’s only the installer that doesn’t detect the disk, but this is not the case for me, because running sudo fdisk -l prints this:

GPT PMBR size mismatch (6378599 != 60538880) will be corrected by write.
Disk /dev/sda: 28.87 GiB, 30995907072 bytes, 60538881 sectors
Disk model: DataTraveler 3.0
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: 09D661A4-D7D4-4D99-8EC7-B91E3365D7F0

Device       Start     End Sectors Size Type
/dev/sda1       64 6317095 6317032   3G Microsoft basic data
/dev/sda2  6317096 6378535   61440  30M EFI System


Disk /dev/loop0: 2.71 GiB, 2908037120 bytes, 5679760 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/zram0: 7.49 GiB, 8040480768 bytes, 1963008 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And inxi -Dzxx prints this:

Drives:
  Local Storage: total: 28.87 GiB used: 0 KiB (0.0%)
  ID-1: /dev/sda vendor: Kingston model: DataTraveler 3.0 size: 28.87 GiB
    type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>

I know that my issue is really specific but I don’t really know where to ask and you know more than I do so this feels like a good place to get help in. Also I know that my post is really disorganized, I’m sorry about that. I just don’t really know what order to put this information in, I might reorganize it later. Anyways if you need more information please let me know and I’ll be sure to send it.

TLDR:

  • I left my computer unused for a while, repaired its charging port, then the SSD started failing
  • The ssd stops being detected after a shutdown or restart and I need to power cycle my laptop for it to get recognized
  • While sometimes it does get recognized by Windows and the bios, it never gets detected by the Fedora Live USB no matter what (and booting into the Fedora USB seems to unload it)
  • I made the Fedora USB twice (once it worked with two other computers and I made it with rufus, the second I made it with the official Fedora Media Writer), and it didn’t work any time
  • I don’t have an option to change my disk mode to AHCI, or any other mode at all
  • Secure boot is off

As you’re undoubtedly aware that DataTraveller 3.0 USB disk is your Live USB drive.

Is you SSD detect in the BIOS at all, Assuming it is, can you take a screenshot of the BIOS displaying the drive being detected and any information you can get it to display about that SSD.

Also, post the entire output of inxi -Fzxx so we can see everything in your tin, just as you have posted it here - as pre-formatted text. That’ll tell us about your kit, the decives, the drivers, what’s detected, the BIOS age and so on - all of which can be used to help piece together the root cause.

When you boot into the Live USB,
what is the output of

lsblk

It depends: If I just turned off my computer, then no, it won’t show up, and in the disk section the bios shows that it’s missing. If I force my computer to turn off, and then wait about one minute then it does show up. I can’t take a picture right now but I might be able to later today.

System:
  Kernel: 6.17.1-300.fc43.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
  Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Fedora Linux 43 (KDE Plasma Desktop Edition)
Machine:
  Type: Laptop System: HUAWEI product: NBLB-WAX9N v: M1070
    serial: <superuser required>
  Mobo: HUAWEI model: NBLB-WAX9N-PCB-B2 v: M1070
    serial: <superuser required> part-nu: C331 Firmware: UEFI vendor: HUAWEI
    v: 1.45 date: 01/17/2023
Battery:
  ID-1: BAT1 charge: 40.4 Wh (77%) condition: 52.4/55.2 Wh (94.9%) volts: 8
    min: 7.64 model: Sunwoda-H HB4692Z9ECW-22T serial: <filter> charging:
    status: discharging control: start: 40% end: 70% cycles: 247
CPU:
  Info: quad core model: Intel Core i5-10210U bits: 64 type: MT MCP
    arch: Comet/Whiskey Lake note: check rev: C cache: L1: 256 KiB L2: 1024 KiB
    L3: 6 MiB
  Speed (MHz): avg: 900 min/max: 400/4200 cores: 1: 900 2: 900 3: 900 4: 900
    5: 900 6: 900 7: 900 8: 900 bogomips: 33599
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel CometLake-U GT2 [UHD Graphics] vendor: QUANTA driver: i915
    v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: DP-1,HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:9b41
  Device-2: IMC Networks HD Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-6:2 chip-ID: 13d3:5476
  Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
    driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x1404 res: 1920x1080 hz: 60
    dpi: 158 diag: 354mm (13.9")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
    drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.4 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
    device-ID: 8086:9b41 display-ID: :0.0
  API: Vulkan v: 1.4.321 surfaces: N/A device: 0 type: integrated-gpu
    driver: mesa intel device-ID: 8086:9b41 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS vendor: QUANTA driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:02c8
  API: ALSA v: k6.17.1-300.fc43.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel Comet Lake PCH-LP CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:02f0
  IF: wlp0s20f3 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-10:3
    chip-ID: 8087:0aaa
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
    lmp-v: 10
Drives:
  Local Storage: total: 28.87 GiB used: 0 KiB (0.0%)
  ID-1: /dev/sda vendor: Kingston model: DataTraveler 3.0 size: 28.87 GiB
    type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 1.5 GiB used: 541.8 MiB (35.3%) fs: overlay source: ERR-102
Swap:
  ID-1: swap-1 type: zram size: 7.49 GiB used: 699.4 MiB (9.1%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 42.0 C pch: 38.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.49 GiB used: 3.66 GiB (48.8%)
  Processes: 316 Power: uptime: 6m wakeups: 0 Init: systemd v: 258
    default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: N/A Shell: Bash
    v: 5.3.0 running-in: konsole inxi: 3.3.40
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0  2.7G  1 loop /run/rootfsbase
sda      8:0    1 28.9G  0 disk 
├─sda1   8:1    1    3G  0 part /run/initramfs/live
└─sda2   8:2    1   30M  0 part 
zram0  251:0    0  7.5G  0 disk [SWAP]

None of these is my disk

1 Like

You are certainly correct! Your disc is not showing up :slight_smile:

This shows that we are not dealing with a Fedora problem as such, but a Huawei hardware/firmware problem.

Are there any RAID settings in your BIOS?

If the SSD sat unpowered for 3 years, then data corruption is likely, though I’m not sure that it would lead to this state where the drive isn’t reliably detected.

1 Like

I would try openingup the laptop and reseating the SSD.
And if you can, test the drive in an external enclosure, and also test another SSD in the laptop.

While I doubt this will fix the problem (as Windoze shows the drive) it is still worth doing.

1 Like

I think it might still be related though, the Fedora partition that I had earlier seemed to be corrupted, and honestly I don’t know where else to ask and this just felt like a good place for it.

No, there are none. In fact it (the bios) is really minimal, it has almost no options. You can find a few pictures of how what looks like on Google

I don’t have the screws to open it though, and I don’t have anywhere else to test the ssd in / another ssd to test. I also don’t really thinking this is a physical problem as in how the ssd is mounted as I can not move my computer at all but have the disk not work / work depending on what I described earlier

You are very welcome to ask here.
You have given a good description of the problem, and give good feedback.
I would recommend trying to follow the instructions the team give, even if they don’t completely make sense. (Go get a screwdriver) The Lord (and computers) works in mysterious ways.

1 Like

As noted this seems either hardware or software from the laptop mgfr/bios

If you cannot update the bios and it does not give you access to the drive config then the remaining thing you may be able to do is remove and reseat the drive.

Sometimes contacts may become oxidized and cause intermittent connections. Sometimes the ssd devices fail. Either of those may cause symptoms similar to what you are seeing.

It would be only logical to rule out the connection issue in order to narrow down the things to look at.

More than once I have been hit in the face when I find a fault that I had previously dismissed as not possible.

2 Likes

Especially if your environment gets hot and humid. Due to the number of computers in today’s autos, auto supply stores sell “contact enhancer”. I would carefully remove all internal connectors, check for corrosion (usually green scum), clean and then apply contact enhancer.

1 Like

I’ll check if I can get a screwdriver that fits my laptop and open it then, thanks for the advice. Until then, there’s not much else that I can do, right?

inxi finds this tin to be a Huawei WAX9N, which apparently is more than capable of running Linux, and thus whatever limited options are in the BIOS, it should be possible to get it chooching.

Given that it’s flaky at best, sometimes vanishes for no reason, doesn’t appear if the machine is rebooted, sometimes needs a forced shutdown and so on… I’d not trust this SSD as far as I could throw it. If it’s this temperamental, I’d not trust with it with any data storage and I’d even be somewhat suspicious of any backups of my data I took from it.

Either way you need to get into the case to clean and reseat it or remove it and replace it with something which is a little more stable.

2 Likes