You are not logged in.

#1 2021-11-22 18:29:19

jairot
Member
Registered: 2021-09-06
Posts: 7

[SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

I got two drives on my system, an SSD for the OS and programs and a HDD for long-term storage. Both drives are recognized by the BIOS, but I can't find the HDD to mount onto my system. Both Drives are permanently connected (Laptop). I'm quite sure it is not hardware error, since I recently got the Laptop back from the manufacturer after they fixed the Hardware issues it had.

The output of fdisk -l reads:

Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: KBG40ZNV256G KIOXIA
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: 28A52FBC-5EBD-4A0E-B1D5-38511B9E71D7

Device           Start       End   Sectors  Size Type
/dev/nvme0n1p1    2048   1050623   1048576  512M EFI System
/dev/nvme0n1p2 1050624 500118158 499067535  238G Linux filesystem

The information regarding the drive I'm trying to mount is as follows (according to the BIOS):

Port: 0.1
Model Number: WDC WD10SPZX-60Z10T1
Size: 931.5GB
Status: Non-RAID
Controller Type: AHCI
Controller Interface: SATA

I've tried rescanning SATA ports by using some commands like

[user@Laptop ~]$ sudo echo "---" > /sys/class/scsi_host/host0/scan
> bash: /sys/class/scsi_host/host0/scan: Permission denied

[user@Laptop  ~]$ sudo echo "0 0 0" >/sys/class/scdi_host/host0/scan
> bash: /sys/class/scdi_host/host0/scan: No such file or directory

Any help or pointers would be appreciated :)

Last edited by jairot (2021-11-23 15:21:21)

Offline

#2 2021-11-22 20:29:31

roccobaroccoSC
Member
Registered: 2021-10-04
Posts: 16

Re: [SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

Can you try the command

lsblk

? Also, take a look into your

dmesg

output. Search for a text like this:

sudo dmesg | grep sda
[    3.306408] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    3.306411] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    3.306419] sd 0:0:0:0: [sda] Write Protect is off
[    3.306420] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.306431] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.584522]  sda: sda1
[    3.584952] sd 0:0:0:0: [sda] Attached SCSI disk

Also, search your /dev directory for sd* files.
Maybe your HDD is not formatted yet. In this case you would need to create a partition table (GPT is recommended). You can format the drive with the command

cfdisk /dev/sda

This would destroy all data on the device, of course!

Also, take a look at this thread: https://unix.stackexchange.com/question … the-system
It describes more ways to analyze your devices.

I assume your HDD is SATA. SATA drives should be detected automatically by Arch, you don't need an extra driver to load or whatever.

Last edited by roccobaroccoSC (2021-11-22 20:32:08)

Offline

#3 2021-11-22 20:44:35

seth
Member
Registered: 2012-09-03
Posts: 49,986

Re: [SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

[user@Laptop ~]$ sudo echo "---" > /sys/class/scsi_host/host0/scan
> bash: /sys/class/scsi_host/host0/scan: Permission denied
echo "---"  | sudo tee /sys/class/scsi_host/host0/scan

But please provide lsblk and dmesg as mentioned by roccobaroccoSC
If that doesn't lead anywhere, you could try to access the drive via IDE insntead of ahci (the bios likely has a setting for that)

Online

#4 2021-11-22 22:39:38

jairot
Member
Registered: 2021-09-06
Posts: 7

Re: [SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

Ok, lets do this

So the output for lsblk is

lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:0    0 238.5G  0 disk
|-nvme0n1p1 259:1    0   512M  0 part
`-nvme0n1p2 259:2    0   238G  0 part /

Going further

 sudo dmesg | grep sda

gives me no output.

I am unable to find any sd* files on /dev/:

ls /dev/
acpi_thermal_rel  drm_dp_aux0  kvm             nvidia-uvm        random    tty1   tty22  tty35  tty48  tty60   ttyS15  ttyS28   urandom  vcsa3   vga_arbiter
autofs            drm_dp_aux1  lightnvm        nvidia-uvm-tools  rfkill    tty10  tty23  tty36  tty49  tty61   ttyS16  ttyS29   userio   vcsa4   vhci
block             fb0          log             nvidia0           rtc       tty11  tty24  tty37  tty5   tty62   ttyS17  ttyS3    v4l      vcsa5   vhost-net
btrfs-control     fd           loop-control    nvidiactl         rtc0      tty12  tty25  tty38  tty50  tty63   ttyS18  ttyS30   vcs      vcsa6   vhost-vsock
bus               full         mapper          nvme0             shm       tty13  tty26  tty39  tty51  tty7    ttyS19  ttyS31   vcs1     vcsa63  video0
char              fuse         media0          nvme0n1           snapshot  tty14  tty27  tty4   tty52  tty8    ttyS2   ttyS4    vcs2     vcsu    video1
console           gpiochip0    mei0            nvme0n1p1         snd       tty15  tty28  tty40  tty53  tty9    ttyS20  ttyS5    vcs3     vcsu1   watchdog
core              hidraw0      mem             nvme0n1p2         stderr    tty16  tty29  tty41  tty54  ttyS0   ttyS21  ttyS6    vcs4     vcsu2   watchdog0
cpu               hidraw1      mqueue          nvram             stdin     tty17  tty3   tty42  tty55  ttyS1   ttyS22  ttyS7    vcs5     vcsu3   zero
cpu_dma_latency   hpet         mtd0            port              stdout    tty18  tty30  tty43  tty56  ttyS10  ttyS23  ttyS8    vcs6     vcsu4
cuse              hugepages    mtd0ro          ppp               tpm0      tty19  tty31  tty44  tty57  ttyS11  ttyS24  ttyS9    vcs63    vcsu5
disk              hwrng        net             psaux             tpmrm0    tty2   tty32  tty45  tty58  ttyS12  ttyS25  udmabuf  vcsa     vcsu6
dma_heap          input        null            ptmx              tty       tty20  tty33  tty46  tty59  ttyS13  ttyS26  uhid     vcsa1    vcsu63
dri               kmsg         nvidia-modeset  pts               tty0      tty21  tty34  tty47  tty6   ttyS14  ttyS27  uinput   vcsa2    vfio

Even after snooping around in

/dev/disk/

and the other directories/files as suggested in the link provided by roccobaroccoSC, I only found stuff pertaining to de SSD.

The corrected command given by Seth gives me:

echo "---"  | sudo tee /sys/class/scsi_host/host0/scan
[sudo] password for jairot:
---
tee: /sys/class/scsi_host/host0/scan: Invalid argument

And now for the fun part, the output of

sudo dmesg

https://dpaste.com/E3LRF92SU

As it regards the UEFI Firmware settings there is no option in the menu of the BIOS to chance the Controller Type from AHCI to IDE

Offline

#5 2021-11-23 07:38:00

seth
Member
Registered: 2012-09-03
Posts: 49,986

Re: [SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

tee: /sys/class/scsi_host/host0/scan: Invalid argument

"- - -" - those need to be 3 glyphs separated by blanks (sorry, missed that when copypasting your command)

However:

[    0.460137] ahci 10000:e0:17.0: version 3.0
[    0.460146] ahci 10000:e0:17.0: can't derive routing for PCI INT A
[    0.460147] ahci 10000:e0:17.0: PCI INT A: no GSI
[    0.460216] ahci 10000:e0:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[    0.460217] ahci 10000:e0:17.0: flags: 64bit ncq sntf pm clo only pio slum part deso sadm sds
…
[    0.460556] pcieport 10000:e0:1c.4: can't derive routing for PCI INT A
[    0.460557] pcieport 10000:e0:1c.4: PCI INT A: no GSI
[    0.460626] pcieport 10000:e0:1c.4: PME: Signaling with IRQ 144
[    0.460671] pcieport 10000:e0:1c.4: AER: enabled with IRQ 144
[    0.460706] pcieport 10000:e0:1c.4: DPC: enabled with IRQ 144
[    0.460707] pcieport 10000:e0:1c.4: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[    0.460829] nvme nvme0: pci function 10000:e1:00.0
[    0.460838] vmd 0000:00:0e.0: Bound to PCI domain 10000
[    0.460856] pcieport 10000:e0:1c.4: can't derive routing for PCI INT A

leads to

[    0.460523] ata2: SATA max UDMA/133 abar m2048@0x52102000 port 0x52102180 irq 143
[    0.789467] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    5.825938] ata2.00: qc timeout (cmd 0xec)
[    5.827027] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.159922] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   16.545937] ata2.00: qc timeout (cmd 0xec)
[   16.547028] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   16.547043] ata2: limiting SATA link speed to 3.0 Gbps
[   16.879856] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[   47.265929] ata2.00: qc timeout (cmd 0xec)
[   47.267015] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   47.599870] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 3296.062803] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 3301.080110] ata2.00: qc timeout (cmd 0xec)
[ 3301.081316] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 3301.413872] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 3311.560030] ata2.00: qc timeout (cmd 0xec)
[ 3311.561245] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 3311.561257] ata2: limiting SATA link speed to 1.5 Gbps
[ 3311.893715] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 3342.279809] ata2.00: qc timeout (cmd 0xec)
[ 3342.280998] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 3342.613853] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 5887.116820] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 5892.123951] ata2.00: qc timeout (cmd 0xec)
[ 5892.125045] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 5892.455874] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 5902.923720] ata2.00: qc timeout (cmd 0xec)
[ 5902.924810] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 5903.265887] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 5933.643672] ata2.00: qc timeout (cmd 0xec)
[ 5933.644759] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 5933.977417] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 7519.132989] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 7524.160214] ata2.00: qc timeout (cmd 0xec)
[ 7524.161394] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 7524.494021] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 7534.810021] ata2.00: qc timeout (cmd 0xec)
[ 7534.811105] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 7535.142969] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 7565.529948] ata2.00: qc timeout (cmd 0xec)
[ 7565.531138] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 7565.863853] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[13266.054616] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[13271.111653] ata2.00: qc timeout (cmd 0xec)
[13271.112741] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[13271.444770] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[13281.671678] ata2.00: qc timeout (cmd 0xec)
[13281.672768] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[13282.003041] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[13312.391470] ata2.00: qc timeout (cmd 0xec)
[13312.392555] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[13312.725510] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

I'm quite sure it is not hardware error, since I recently got the Laptop back from the manufacturer after they fixed the Hardware issues it had.

Did the drive work *before*?

menu of the BIOS to chance the Controller Type from AHCI to IDE

These can come at all sorts of weird names (legacy, raid mode, …)

Lastly: did you try the main kernel instead of the lts one?

Online

#6 2021-11-23 15:18:58

jairot
Member
Registered: 2021-09-06
Posts: 7

Re: [SOLVED] Cannot mount Hard Drive although it is recognized by the BIOS

The hard drive did work beforehand, the drive I sent the unit to repair for was the SSD.

Anyway I tried the non-lts Kernel and that seems to have solved the Hard Drive issue, but broke my KDE install, I switched to xfce4 which seems to work fine so far, I'll look into that issue later.

Thanks for all your support guys! :)

Offline

Board footer

Powered by FluxBB