[solved]new sdd drive not attached

Message

deathraccoon · Post by **deathraccoon** » Thu Oct 01, 2015 10:39 pm

hello.

fdisk -l gives me the foolowing:

Disk /dev/ram0: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 8 MiB, 8388608 bytes, 16384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

what am I doing wrong?

ct85711 · Post by **ct85711** » Fri Oct 02, 2015 6:38 am

fdisk man page wrote: -l, --list
List the partition tables for the specified devices and then exit. If no devices are given, those mentioned in /proc/partitions (if that file exists) are
used.

You got the expected output (minus the actually hard drive after all the ram drives towards the end). The proper thing would have also specified the specific drive too (i.e like /dev/sda).
An example of the full line should have been more of like

Code: Select all

fdlisk -l /dev/sda

Any hard drives you install into your computer, will be listed in your /dev folder starting with sd[a-z] depending on how many drives you have (the numbers after is partitions).

Now if you didn't have a listing for a hard drive, it may indicate that the drive isn't setup (has no partitions yet). (this is a guess, so I may be wrong)

Now if you don't see the drive (the sd[] representing your drive) indicates a more serious issue..
One, your computer isn't seeing the hard drive being connected in general (your bios should report seeing the drive)
Two, your kernel isn't set up properly (try using using a live cd, and see if it sees the drive)
or lastly (very unlikely to be the case) your dev system is messed up...

deathraccoon · Post by **deathraccoon** » Sun Oct 04, 2015 1:48 pm

fsdik doesn't recognize it. nor does parted nor gdisk. the folks at newegg said to return it as it is likely a bad drive. but I don;ty think that is probably the case. I have enabled AHCI in the bios and the kernel supports it. any other suggestions?

ct85711 · Post by **ct85711** » Sun Oct 04, 2015 4:06 pm

ok, lets start with the basics... Does your bios even see the ssd drive? It should be listed with any other drives installed. If your BIOS isn't seeing the drive, you either have a bad hard drive or it's not hooked up (check the cables) it will have 2 cables going to it, a wider one which is power, and a skinny one which will be the data cable going to the motherboard.

After you verified the bios even sees the hard drive; try booting from a live cd and see if that sees the hard drive. If a live cd sees the drive, it most likely means your kernel isn't setup properly...

Now, if the hard drive is connected to an raid controller (i.e. the hard drive data cable is going to an expansion card instead of motherboard), I'm not as familiar on checking if that sees the drive. Though usually those cards will need some additional drives to work properly too.

deathraccoon · Post by **deathraccoon** » Thu Oct 08, 2015 5:16 am

I am embarassed. The drive was not soundly attached. thank you for the replies.