Subj : Hard Drive configuration
To   : Bogomips
From : Boraxman
Date : Tue May 13 2025 08:04 am

-=> Bogomips wrote to All <=-

Bo> @MSGID: <[email protected]>
Bo> In and attempt to have a dual boot laptop


Bo> Ive been trying to get get the slackware install to recognize the D:
Bo> drive on install.

Bo> After trying every scenerio online. I still come up short.

Bo> I was thinking of changing the physical location of the drive?

Bo> Out of the box (2018) it was setup in RAID config.

Bo> The BIOS shows the two drives as
Bo> First HDD none
Bo> Second HDD none
Bo> Third HDD IntelSSDlkji (180.G)
Bo> fourth HDD sd2000louol (2000.3G)

Bo> Was wondering if I could move the D: drive to the first or seconds
Bo> spot?

Bo> And any other actions I  would need to take?

Try using a Linux Live CD like systemrescuecd.  Boot it, see if that detects
it.
Also look at the output of "dmesg", see if that reports any errors, and the
output of the command 'lsblk'.

I'm not too familiar with Slackware installer, but if there is a way to get to
a command line interface WITHIN the installer to run commands, you could do
this within the Slackware installer.  Often with Linux installers you can get
access to a shell.

dmesg will show you all the kernel messages.  If you look through it, it will
mention everything the kernel has detected in terms of hardware.  It will
indicate if its found the other hard drive or not, and should detect any RAID
set up.

lsblk is another command which simply lists block devices.

It is a little unusual for Linux not to see the drive, I've never really come
across that before.

It's also important to understand that Linux does NOT do drive letters, it does
devices.  C: and D: are windows constructs for PARTITIONS.  First partition C:,
Second D: and so on.  D: could actually be on the SAME disk as C:

Also, if you have a second hard-drive, but it is NOT partitioned for Windows,
it
won't come up as D: at all.

If you could let us know what 'lsblk' reports, that would help.

A drive will appear to be something like
/dev/sdd
with each partition
/dev/sdd1
/dev/sdd2
etc

The fact that the BIOS is finding it means that Linux SHOULD see it as well.
Lets see what Linux actually reports first, and verify this isn't simply a case
of it actually seeing it and you not recognising that it found it.

--- MultiMail/Linux v0.49
� Synchronet � MS & RD BBs - bbs.mozysswamp.org