[SOLVED] New install does not see SSD drive

banshee28 · 2009-02-26 02:49:07

Ok, I have a DFI motherboard which at first did not recognize my new Intel SSD drive I have installed. After updating the BIOS, it now correctly recognizes it. However when I run the 2009.2 cd and try to prepare the drives, it does not show any drives listed?

 /sbin/fdisk -l

does not show any drives either so it looks like arch cant see any installed HD's which makes since, but the motherboard does show the new Intel SSD as a Sata drive right under my DVD player?

Any help?

Edit: I hooked up my old Seagate drive and it shows up fine. Any idea on why this SSD is not playing nice?

Solved: I have come to the conclusion this has nothing to do with the Arch install, but is simply a hardware issue with my motherboard. I installed the SSD drive in my wifes pc, it seen the ssd as a sata drive while booting, it seen it when arch was initializing, it seen it when I did a fdisk, and when i finally tried to install, it was there too!!

So there must be some issue with my old DFI MB. I will work on that or upgrade..Thanks to everyone who helped out...

Last edited by banshee28 (2009-02-28 16:48:07)

ralvez · 2009-02-26 03:07:16

try fdisk /dev/sda0 or /dev/sda1 see if it "takes"

R.

Last edited by ralvez (2009-02-26 03:07:41)

banshee28 · 2009-02-26 03:13:08

ralvez wrote:

try fdisk /dev/sda0 or /dev/sda1 see if it "takes"
R.

tried sda0 and sda1 both "unable to open"

ralvez · 2009-02-26 03:25:35

is that disk "built in" or plugged?

lilsirecho · 2009-02-26 03:33:40

Mebbe

/sbin/sfdisk -l

banshee28 · 2009-02-26 03:40:20

ralvez wrote:

is that disk "built in" or plugged?

its a plugged in sata

banshee28 · 2009-02-26 03:43:50

lilsirecho wrote:

Mebbe

/sbin/sfdisk -l

this returns nothing.

sfdisk /dev/sda0 or sda1 returns a fatal error cannot find /dev/sda0 (sda1) ??

lilsirecho · 2009-02-26 03:54:34

Perhaps the power to the SSD is missing or the sata connector on the motherboard is not making good contact(often happens on my board).

banshee28 · 2009-02-26 03:57:30

lilsirecho wrote:

Perhaps the power to the SSD is missing or the sata connector on the motherboard is not making good contact(often happens on my board).

yea, i made sure its 100% tight both power and the sata connector. Then i used the same cables to my old seagate drive and it worked fine.

I do think its something with the board though since it had trouble trying to locate this drive so many times!!

lilsirecho · 2009-02-26 04:30:06

I had trouble with my throttle device not making contact with the data lines when connected to USB.

I assume the SSD has the same connector as the motherboard and the cable can be reversed end to end to test for performance.

I use a multimeter to verify the presence of power to the device.

Sata cables are known to be flaky.

Throttle devices use 5vdc power from USB connector and are connected to esata cables at the same time since sata ports do not supply power. The connections for throttle are on opposite ends of the device.

I am not familiar with the SSD power setup but assume it is 5vdc as well.

No other suggestions here..................

banshee28 · 2009-02-26 13:11:39

lilsirecho wrote:

I had trouble with my throttle device not making contact with the data lines when connected to USB.
I assume the SSD has the same connector as the motherboard and the cable can be reversed end to end to test for performance.
I use a multimeter to verify the presence of power to the device.
Sata cables are known to be flaky.
Throttle devices use 5vdc power from USB connector and are connected to esata cables at the same time since sata ports do not supply power. The connections for throttle are on opposite ends of the device.
I am not familiar with the SSD power setup but assume it is 5vdc as well.
No other suggestions here..................

Yes, the cable should be able to be reversed as the ssd drives are identical compared to normal sata drives in respect to the cable connections: one sata data connection and one power. I will try some different cables and see if that helps. I did try a new port on the mb which did not work, and when i used the current cables on my older seagate drive it worked fine

Last edited by banshee28 (2009-02-26 13:15:52)

lilsirecho · 2009-02-26 23:25:32

Looks much like the cd program is at fault....

Dieter@be · 2009-02-27 13:17:40

What does your dmesg say?

banshee28 · 2009-02-27 23:27:44

lilsirecho wrote:

Looks much like the cd program is at fault....

CD program?

banshee28 · 2009-02-27 23:28:40

Dieter@be wrote:

What does your dmesg say?

Will try again now.. I think each time before when i ran it i did not see "intel" or "ssd" anywhere in the output.

banshee28 · 2009-02-28 00:37:58

Just ran dmesg again and found nothing related to the ssd or intel drive. I found the dvd drive listed under scsi, so I filtered for scsi and thats the only device that was there. I swapped out the cable for the dvd drive cable and port on the board and its doing the same thing.

However after several reboots and trying to get into the bios, the bios also occasionally does not see the ssd either! Sounds like a hardware issue, but just want to make sure

Also with some of these ssd's getting "high tech", would i need to setup any kind of raid to see the drives, or should dmesg at least see the physical drive?

Last edited by banshee28 (2009-02-28 00:38:25)

banshee28 · 2009-02-28 16:48:17

Solved: I have come to the conclusion this has nothing to do with the Arch install, but is simply a hardware issue with my motherboard. I installed the SSD drive in my wifes pc, it seen the ssd as a sata drive while booting, it seen it when arch was initializing, it seen it when I did a fdisk, and when i finally tried to install, it was there too!!

So there must be some issue with my old DFI MB. I will work on that or upgrade..Thanks to everyone who helped out...

pedepy · 2009-03-01 05:45:47

that's not 'solved'..

by the by what does your bios have to say about it ?

Last edited by pedepy (2009-03-01 05:46:58)

banshee28 · 2009-03-01 12:17:20

pedepy wrote:

that's not 'solved'..
by the by what does your bios have to say about it ?

lol ... Well i figured it was "solved" since it worked fine in another pc it must be a hardware issue? Now I flashed to another bios and now it does not post at all!!:mad:

So I think it might be a dying MB which I might have to upgrade. The bios showed the SSD "sometimes" when it booted up, and sometimes it did not. Sometimes I would have to reboot for it to see it. The other pc i tested it in worked perfectly the very first time.

Arch Linux

#1 2009-02-26 02:49:07

[SOLVED] New install does not see SSD drive

#2 2009-02-26 03:07:16

Re: [SOLVED] New install does not see SSD drive

#3 2009-02-26 03:13:08

Re: [SOLVED] New install does not see SSD drive

#4 2009-02-26 03:25:35

Re: [SOLVED] New install does not see SSD drive

#5 2009-02-26 03:33:40

Re: [SOLVED] New install does not see SSD drive

#6 2009-02-26 03:40:20

Re: [SOLVED] New install does not see SSD drive

#7 2009-02-26 03:43:50

Re: [SOLVED] New install does not see SSD drive

#8 2009-02-26 03:54:34

Re: [SOLVED] New install does not see SSD drive

#9 2009-02-26 03:57:30

Re: [SOLVED] New install does not see SSD drive

#10 2009-02-26 04:30:06

Re: [SOLVED] New install does not see SSD drive

#11 2009-02-26 13:11:39

Re: [SOLVED] New install does not see SSD drive

#12 2009-02-26 23:25:32

Re: [SOLVED] New install does not see SSD drive

#13 2009-02-27 13:17:40

Re: [SOLVED] New install does not see SSD drive

#14 2009-02-27 23:27:44

Re: [SOLVED] New install does not see SSD drive

#15 2009-02-27 23:28:40

Re: [SOLVED] New install does not see SSD drive

#16 2009-02-28 00:37:58

Re: [SOLVED] New install does not see SSD drive

#17 2009-02-28 16:48:17

Re: [SOLVED] New install does not see SSD drive

#18 2009-03-01 05:45:47

Re: [SOLVED] New install does not see SSD drive

#19 2009-03-01 12:17:20

Re: [SOLVED] New install does not see SSD drive

Board footer