Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

  1. #11
    Join Date
    Jun 2007
    Location
    ~$
    Beans
    62
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Hi Johnross,

    Tried my approach? No drives but the OCZ and install using pen drive?

    Let me know.

    Greetz,

    J@n
    Main desktop: Mint 12-AMD Phenom II X4 975-16GB- 60 GB OCZ Vertex 2 SSD + 2 TB + 1,5 TB (DIY)
    Storage: Synology CS-406-4x500 GB, DS-211-2x2TB
    Ubuntu user 33387

  2. #12

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    J@n,

    Yes, I've tried installing from CD and I've also tried installing from usb flash drive with other drives connected and with all other drives disconnected. Results are always the same.

    OCZ tech support suggested doing a secure erase to reset the drive but their firmware tool doesn't work on Windows XP and I don't have Vista/7 so I'm stuck on that approach.

    This morning I tried doing a usb pen drive install of the latest natty build. It appears natty has the same issues as the others and it couldn't find the OCZ ssd.

    I've done a lot of googling and I think the problem lies in a murky nexus of buggy bios firmware, ssd firmware and linux drivers. I'm guessing that no one really knows what the problem really is and even if they do I kind of doubt that it will get fixed any time soon.

    At this point, I've wasted far more time trying to get this to work than the faster drive would have ever saved me on my applications so I've decided to give up on it and just go back to using my HHD for now. I may try a different make of SSD at a later date. Frustrating to say the least!

    Thanks again for responding!

  3. #13
    Join Date
    Jun 2007
    Location
    ~$
    Beans
    62
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Hi Johnross,

    I had the same frustrating experience with my first board (Asus M2N series). I too concluded the combination was causing the problems. So I bought the new board expecting install was going to be a breeze. Unfortunately it was quite difficult to get it working as you have read.

    I found on the OCZ forum a tool/method to secure erase the disk. Haven't used it myself but you could investigate. Have a look here: http://www.ocztechnologyforum.com/fo...d-Click-Method

    Greetz,

    J@n
    Main desktop: Mint 12-AMD Phenom II X4 975-16GB- 60 GB OCZ Vertex 2 SSD + 2 TB + 1,5 TB (DIY)
    Storage: Synology CS-406-4x500 GB, DS-211-2x2TB
    Ubuntu user 33387

  4. #14

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Thanks for the link! I'll give it a try and let you know if I have any success.

  5. #15

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Looks like partedmagic secure erase internal mode couldn't detect the ocz drive. It found my maxtor hdd just fine though. Oh well...

  6. #16
    Join Date
    Feb 2008
    Beans
    50

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Quote Originally Posted by J@n View Post
    I created a bootable USB disk (pen drive) with UnetBootIn and tried again. This time I got a complete and succesfull install. Reconnected the other drives and now all is working perfectly.
    Thanks again, J@n. I finally got around to giving this a shot, but unfortunately I still get the same result. Any other thoughts, anyone?

  7. #17
    Join Date
    Feb 2008
    Beans
    50

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    bump.

  8. #18

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    Over the weekend I put the ocz in an external usb adapter. I booted parted magic on a usb stick and was able to detect and wipe the ocz with secure erase. I was then able to install Maverick 64 bit from usb stick without any problems. The ocz booted and ran fine in the usb adapter. Unfortunately when I connected the drive to the SATA adapter on the Asus motherboard it froze with drive errors on boot. That was enough for me and I returned the drive to the seller for a refund.

    I'm done with ocz for now but would appreciate it if someone would e-mail me if you ever figure out the root cause of this issue. Thanks!

    John

  9. #19
    Join Date
    Jun 2011
    Beans
    4

    Corsair Force 3 SSD unrecognized by Ubuntu - faulty drive?

    Same problem for me with a 120GB Corsair Force 3 Series SSD.

    I tried a new Linux install from CD onto the drive, trying both Ubuntu 11.10 and Debian Testing.. but both failed at the same point..

    Syslog reveals:

    Code:
    Oct 25 17:42:20 kernel: [    1.447477] libata version 3.00 loaded.
    Oct 25 17:42:20 kernel: [    1.455693] pata_sis 0000:00:02.5: version 0.5.2
    
    Oct 25 17:42:20 kernel: [    1.480712] pata_sis 0000:00:02.5: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    Oct 25 17:42:20 kernel: [    1.493927] scsi0 : pata_sis
    Oct 25 17:42:20 kernel: [    1.505575] scsi1 : pata_sis
    Oct 25 17:42:20 kernel: [    1.516947] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x1080 irq 14
    Oct 25 17:42:20 kernel: [    1.528328] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1088 irq 15
    
    Oct 25 17:42:20 kernel: [    1.744260] ata1.00: ATAPI: TSSTcorp CDDVDW TS-L632H, TMC0, max UDMA/33
    Oct 25 17:42:20 kernel: [    1.788233] ata1.00: configured for UDMA/33
    Oct 25 17:42:20 kernel: [    1.800281] Refined TSC clocksource calibration: 1999.975 MHz.
    Oct 25 17:42:20 kernel: [    1.812522] Switching to clocksource tsc
    Oct 25 17:42:20 kernel: [    1.825711] scsi 0:0:0:0: CD-ROM            TSSTcorp CDDVDW TS-L632H  TMC0 PQ: 0 ANSI: 5
    Oct 25 17:42:20 kernel: [    1.838030] ata2: port disabled. ignoring.
    
    Oct 25 17:42:20 kernel: [    1.880495] sata_sis 0000:00:05.0: version 1.0
    Oct 25 17:42:20 kernel: [    1.880534] sata_sis 0000:00:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Oct 25 17:42:20 kernel: [    1.880540] sata_sis 0000:00:05.0: Detected SiS 1183/966/966L/968/680 controller in PATA mode
    Oct 25 17:42:20 kernel: [    1.947251] scsi2 : sata_sis
    Oct 25 17:42:20 kernel: [    1.947388] scsi3 : sata_sis
    Oct 25 17:42:20 kernel: [    1.947932] ata3: PATA max UDMA/133 cmd 0x10c8 ctl 0x10bc bmdma 0x10a0 irq 17
    Oct 25 17:42:20 kernel: [    1.947935] ata4: PATA max UDMA/133 cmd 0x10c0 ctl 0x10b8 bmdma 0x10a8 irq 17
    
    Oct 25 17:42:20 kernel: [    7.480035] ata3.00: qc timeout (cmd 0x27)
    Oct 25 17:42:20 kernel: [    7.493502] ata3.00: failed to read native max address (err_mask=0x4)
    Oct 25 17:42:20 kernel: [    7.507191] ata3.00: HPA support seems broken, skipping HPA handling
    Oct 25 17:42:20 kernel: [    7.708215] ata3.00: ATA-8: Corsair Force 3 SSD, 1.3, max UDMA/133
    Oct 25 17:42:20 kernel: [    7.721907] ata3.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Oct 25 17:42:20 kernel: [    7.756209] ata3.00: configured for UDMA/133
    Oct 25 17:42:20 kernel: [    7.770092] scsi 2:0:0:0: Direct-Access     ATA      Corsair Force 3  1.3  PQ: 0 ANSI: 5
    Oct 25 17:42:20 kernel: [    7.955617] sr 0:0:0:0: Attached scsi generic sg0 type 5
    Oct 25 17:42:20 kernel: [    7.976509] scsi 2:0:0:0: Attached scsi generic sg1 type 0
    Oct 25 17:42:20 kernel: [    7.991283] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
    Oct 25 17:42:20 kernel: [    8.007956] sd 2:0:0:0: [sda] Write Protect is off
    Oct 25 17:42:20 kernel: [    8.021802] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Oct 25 17:42:20 kernel: [    8.022424] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Oct 25 17:42:20 kernel: [    8.051637]  sda: sda1 sda2 < sda5 >
    Oct 25 17:42:20 kernel: [    8.066370] sd 2:0:0:0: [sda] Attached SCSI disk
    
    Oct 25 17:42:20 kernel: [   38.848028] ata3: lost interrupt (Status 0x58)
    Oct 25 17:42:20 kernel: [   38.863129] ata3: drained 512 bytes to clear DRQ.
    Oct 25 17:42:20 kernel: [   38.863138] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Oct 25 17:42:20 kernel: [   38.877849] ata3.00: failed command: IDENTIFY DEVICE
    Oct 25 17:42:20 kernel: [   38.892153] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
    Oct 25 17:42:20 kernel: [   38.892155]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Oct 25 17:42:20 kernel: [   38.920958] ata3.00: status: { DRDY }
    Oct 25 17:42:20 kernel: [   38.920986] ata3: soft resetting link
    Oct 25 17:42:20 kernel: [   39.212209] ata3.00: configured for UDMA/133
    Oct 25 17:42:20 kernel: [   39.226301] ata3: EH complete
    
    Oct 25 17:43:26 kernel: [  104.928061] ata3: lost interrupt (Status 0x58)
    Oct 25 17:43:26 kernel: [  104.928430] ata3: drained 512 bytes to clear DRQ.
    Oct 25 17:43:26 kernel: [  104.928438] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Oct 25 17:43:26 kernel: [  104.928442] ata3.00: failed command: IDENTIFY DEVICE
    Oct 25 17:43:26 kernel: [  104.928448] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
    Oct 25 17:43:26 kernel: [  104.928449]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Oct 25 17:43:26 kernel: [  104.928452] ata3.00: status: { DRDY }
    Oct 25 17:43:26 kernel: [  104.928477] ata3: soft resetting link
    Oct 25 17:43:26 kernel: [  105.124210] ata3.00: configured for UDMA/133
    Oct 25 17:43:26 kernel: [  105.124229] ata3: EH complete
    
    Oct 25 17:45:07 kernel: [  205.920025] ata3: lost interrupt (Status 0x58)
    Oct 25 17:45:07 kernel: [  205.920394] ata3: drained 512 bytes to clear DRQ.
    Oct 25 17:45:07 kernel: [  205.920402] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Oct 25 17:45:07 kernel: [  205.920406] ata3.00: failed command: IDENTIFY DEVICE
    Oct 25 17:45:07 kernel: [  205.920412] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
    Oct 25 17:45:07 kernel: [  205.920414]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Oct 25 17:45:07 kernel: [  205.920417] ata3.00: status: { DRDY }
    Oct 25 17:45:07 kernel: [  205.920442] ata3: soft resetting link
    Oct 25 17:45:07 kernel: [  206.180210] ata3.00: configured for UDMA/133
    Oct 25 17:45:07 kernel: [  206.180230] ata3: EH complete
    
    Oct 25 17:47:16 kernel: [  334.880026] ata3: lost interrupt (Status 0x58)
    Oct 25 17:47:16 kernel: [  334.880395] ata3: drained 512 bytes to clear DRQ.
    Oct 25 17:47:16 kernel: [  334.880405] ata3.00: limiting speed to UDMA/100:PIO4
    Oct 25 17:47:16 kernel: [  334.880409] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Oct 25 17:47:16 kernel: [  334.880413] ata3.00: failed command: IDENTIFY DEVICE
    Oct 25 17:47:16 kernel: [  334.880419] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
    Oct 25 17:47:16 kernel: [  334.880420]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Oct 25 17:47:16 kernel: [  334.880423] ata3.00: status: { DRDY }
    Oct 25 17:47:16 kernel: [  334.880449] ata3: soft resetting link
    Oct 25 17:47:16 kernel: [  335.116210] ata3.00: configured for UDMA/100
    Oct 25 17:47:16 kernel: [  335.116229] ata3: EH complete
    
    Oct 25 17:48:18 kernel: [  396.896022] ata3: lost interrupt (Status 0x50)
    Oct 25 17:48:18 kernel: [  396.896040] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    Oct 25 17:48:18 kernel: [  396.896044] ata3.00: failed command: FLUSH CACHE
    Oct 25 17:48:18 kernel: [  396.896049] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
    Oct 25 17:48:18 kernel: [  396.896051]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Oct 25 17:48:18 kernel: [  396.896054] ata3.00: status: { DRDY }
    Oct 25 17:48:18 kernel: [  396.896079] ata3: soft resetting link
    Oct 25 17:48:18 kernel: [  397.164210] ata3.00: configured for UDMA/100
    Oct 25 17:48:18 kernel: [  397.164214] ata3.00: retrying FLUSH 0xe7 Emask 0x4
    Oct 25 17:48:33 kernel: [  412.164027] ata3.00: qc timeout (cmd 0xe7)
    Oct 25 17:48:33 kernel: [  412.164032] ata3.00: FLUSH failed Emask 0x4
    Oct 25 17:48:33 kernel: [  412.164054] ata3: soft resetting link
    Oct 25 17:48:33 kernel: [  412.400209] ata3.00: configured for UDMA/100
    Oct 25 17:48:33 kernel: [  412.400213] ata3.00: retrying FLUSH 0xe7 Emask 0x4
    Oct 25 17:48:48 kernel: [  427.400031] ata3.00: qc timeout (cmd 0xe7)
    Oct 25 17:48:48 kernel: [  427.400037] ata3.00: FLUSH failed Emask 0x4
    Oct 25 17:48:48 kernel: [  427.400042] ata3.00: limiting speed to UDMA/100:PIO3
    Oct 25 17:48:48 kernel: [  427.400068] ata3: soft resetting link
    Oct 25 17:48:49 kernel: [  427.596210] ata3.00: configured for UDMA/100
    Oct 25 17:48:49 kernel: [  427.596213] ata3.00: retrying FLUSH 0xe7 Emask 0x4
    Oct 25 17:49:19 kernel: [  457.596031] ata3.00: qc timeout (cmd 0xe7)
    Oct 25 17:49:19 kernel: [  457.596037] ata3.00: FLUSH failed Emask 0x4
    Oct 25 17:49:19 kernel: [  457.596040] ata3.00: disabled
    Oct 25 17:49:19 kernel: [  457.596056] ata3.00: device reported invalid CHS sector 0
    Oct 25 17:49:19 kernel: [  457.596082] ata3: soft resetting link
    Oct 25 17:49:19 ata_id[4852]: HDIO_GET_IDENTITY failed for '/dev/sda': No message of desired type
    Oct 25 17:49:19 kernel: [  457.752059] ata3: EH complete
    Oct 25 17:49:19 kernel: [  457.752300] sd 2:0:0:0: [sda] READ CAPACITY(16) failed
    Oct 25 17:49:19 kernel: [  457.752303] sd 2:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    Oct 25 17:49:19 kernel: [  457.752308] sd 2:0:0:0: [sda] Sense not available.
    Oct 25 17:49:19 kernel: [  457.752342] sd 2:0:0:0: [sda] READ CAPACITY failed
    Oct 25 17:49:19 kernel: [  457.752344] sd 2:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    Oct 25 17:49:19 kernel: [  457.752348] sd 2:0:0:0: [sda] Sense not available.
    Oct 25 17:49:19 kernel: [  457.752407] sd 2:0:0:0: [sda] Asking for cache data failed
    Oct 25 17:49:19 kernel: [  457.752409] sd 2:0:0:0: [sda] Assuming drive cache: write through
    Oct 25 17:49:19 kernel: [  457.752417] sda: detected capacity change from 120034123776 to 0

  10. #20
    Join Date
    Sep 2012
    Beans
    6

    Re: OCZ Vertex 2 SSD unrecognized by Ubuntu - faulty drive?

    I have not Ubuntu, but I have OCZ Vertex 2 Sata II and the same problem. I have an old PC with intel d865perl but the same results.

    Same dmesg, HDD maxtor (the same of someone in this 3ad), same smartctl --all /dev/sdb results. I have try all my live cd (madriva, pardus, mageia) and gparted without luck.

    Windows XP install fine and works fine. Pardus 2011.2 dama dama find ocz ssd and i can write on it but not to partition it. With an old mandriva live i can to partition it, i'll try some suggestion in this 3ad but I'm not optimistic.

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •