Vertex 450 (128GB) - Disk I/O error

M

MrReplay

n00b
Joined
Mar 24, 2012
Messages
41
When I switched my PC on yesterday I got an error - I can't remember the exact error - after I few tries I decided to reinstalling Windows 7, the disk was showing as unallocated space & I tried installing but got some other kind of error (maybe I/O)

After some Googling on my phone I got a command prompt off the install CD & tried:

diskpart
select disk
clean all

This threw an I/O error. I subsequently tried just clean which executed ok but it still wouldn't let me reinstall the OS. After this I booted into an Ubuntu live CD to try formatting it there but sudo fdisk -l but this wouldn't even display the disk?

Is there anything else I can try here or am I wasting my time?
 
How about booting a linux live cd and using hdparm to secure erase it? I'm guessing you don't have anything on it you need....?
 
Robstar is spot on with it.

Try to secure erase the drive first. Before (and perhaps after, if it completes successfully), you might want to check the SMART attributes for signs of wear.
 
So I rebooted into an Ubuntu live cd; I noticed the disk is showing up in the BIOS screen but when I look in GParted it's not listed?
 
If you do not see it in fdisk -l then it probably does not even have a device node. Maybe check your dmesg for any mention of problems with sda ...
 
Lost-Benji said:
Linux fan-boys unite ehhh....
If you can't clear it with DISKPART then it might be time to check your commands but more to it, check the disk for errors and faults starting with your BIOS and hardware config.

http://technet.microsoft.com/en-us/library/cc766465(v=ws.10).aspx
Click to expand...

What do you mean check my commands?

What should I be checking in BIOS / hardware config? Note that one day it was working, the next day I couldn't reinstall the OS - no BIOS settings were changed in between that time. I should also say that I tried resetting the BIOS defaults, which made no difference...
 
Note that one day it was working, the next day I couldn't reinstall the OS
Click to expand...

This is typical of SSD failure. I suspect you hit some type of controller failure or a firmware bug (and nothing at all to do with the NAND).
 
MrReplay said:
Could you be more specific to what commands I should use?
Click to expand...

When you did fdisk -l did you see a missing device node? I mean did you have /dev/sda, /dev/sdb /dev/sdc ... or did you have one device missing from the middle? If you had a missing device node grep that from your dmesg

For example if /dev/sdb was missing from your fdisk -l

dmesg | grep sdb

would show you just the kernel messages for /dev/sdb
 
Here's the output:

ubuntu@ubuntu:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 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 identifier: 0x0a155de8

Device Boot Start End Blocks Id System
/dev/sda1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sde: 160.0 GB, 160000000000 bytes
255 heads, 63 sectors/track, 19452 cylinders, total 312500000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008b5b1

Device Boot Start End Blocks Id System
/dev/sde1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sde2 206848 312496127 156144640 7 HPFS/NTFS/exFAT
Click to expand...

sda is a 2TB data disk
sde is a 160GB disk I've used to reinstall Win7 on
the SSD isn't showing?
 
Is there more than sda and sde when you execute the following:

Code: 
ls -al /dev/sd?


Does this show anything other than sda and sde

Code: 
dmesg | grep Attached

Here is an example from my home pc:

Code: 
jmd0 work # dmesg | grep Attached
[    1.285419] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[    1.287568] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.771842] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.825793] sd 1:0:0:0: [sdb] Attached SCSI disk
[    2.246637] sd 2:0:0:0: Attached scsi generic sg2 type 0
[    2.266422] sd 2:0:0:0: [sdc] Attached SCSI disk
[    2.483685] sd 6:0:0:0: Attached scsi generic sg3 type 0
[    2.563292] sd 6:0:0:0: [sdd] Attached SCSI disk
[    2.599633] sd 7:0:0:0: Attached scsi generic sg4 type 0
[    2.634590] sd 7:0:0:0: [sde] Attached SCSI disk
[    2.720195] sd 3:0:0:0: Attached scsi generic sg5 type 0
[    2.754593] sd 3:0:0:0: [sdf] Attached SCSI disk
[    3.193226] sd 4:0:0:0: Attached scsi generic sg6 type 0
[    3.226541] sd 4:0:0:0: [sdg] Attached SCSI disk
[    3.666237] sd 5:0:0:0: Attached scsi generic sg7 type 0
[    3.702600] sd 5:0:0:0: [sdh] Attached SCSI disk
[    4.049306] sd 9:0:0:0: Attached scsi generic sg8 type 0
[    4.085084] sd 9:0:0:0: [sdi] Attached SCSI disk
 
Code: 
ubuntu@ubuntu:~$ ls -al /dev/sd?

brw-rw---- 1 root disk 8,  0 Feb 20 20:49 /dev/sda
brw-rw---- 1 root disk 8, 16 Feb 20 20:49 /dev/sdb
brw-rw---- 1 root disk 8, 64 Feb 20 20:49 /dev/sde

I don't get an output for dmesg | grep Attached
 
Are you booting from a USB stick? sdb shows up there.

Code: 
hdparm -I /dev/sdb

smartctl --all /dev/sdb
 
Code: 
ubuntu@ubuntu:~$ sudo hdparm -I /dev/sdb

/dev/sdb:

ATA device, with non-removable media
	Model Number:       OCZ-VERTEX450                           
	Serial Number:      OCZ-57V17A23R739NJ86
	Firmware Revision:  1.0     
	Transport:          Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
	Supported: 8 7 6 5 
	Likely used: 8
Configuration:
	Logical		max	current
	cylinders	16383	16383
	heads		16	16
	sectors/track	63	63
	--
	CHS current addressable sectors:   16514064
	LBA    user addressable sectors:  250069680
	LBA48  user addressable sectors:  250069680
	Logical  Sector size:                   512 bytes
	Physical Sector size:                   512 bytes
	device size with M = 1024*1024:      122104 MBytes
	device size with M = 1000*1000:      128035 MBytes (128 GB)
	cache/buffer size  = unknown
	Nominal Media Rotation Rate: Solid State Device
Capabilities:
	LBA, IORDY(can be disabled)
	Queue depth: 32
	Standby timer values: spec'd by Standard, no device specific minimum
	R/W multiple sector transfer: Max = 1	Current = 1
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	SMART feature set
	   *	Security Mode feature set
	   *	Power Management feature set
	   *	Write cache
	   *	Look-ahead
	   *	Host Protected Area feature set
	   *	WRITE_BUFFER command
	   *	READ_BUFFER command
	   *	DOWNLOAD_MICROCODE
	    	SET_MAX security extension
	   *	48-bit Address feature set
	   *	Device Configuration Overlay feature set
	   *	Mandatory FLUSH_CACHE
	   *	FLUSH_CACHE_EXT
	   *	SMART self-test
	   *	General Purpose Logging feature set
	   *	64-bit World wide name
	   *	Segmented DOWNLOAD_MICROCODE
	   *	Gen1 signaling speed (1.5Gb/s)
	   *	Gen2 signaling speed (3.0Gb/s)
	   *	Gen3 signaling speed (6.0Gb/s)
	   *	Native Command Queueing (NCQ)
	   *	Host-initiated interface power management
	   *	DMA Setup Auto-Activate optimization
	   *	Software settings preservation
	   *	Data Set Management TRIM supported (limit unknown)
Security: 
	Master password revision code = 30688
		supported
		enabled
		locked
	not	frozen
	not	expired: security count
	not	supported: enhanced erase
	Security level high
Logical Unit WWN Device Identifier: 5e83a97632619308
	NAA		: 5
	IEEE OUI	: e83a97
	Unique ID	: 632619308
Checksum: correct

Code: 
ubuntu@ubuntu:~$ sudo smartctl --all /dev/sdb
smartctl 6.2 2013-04-20 r3812 [x86_64-linux-3.11.0-12-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     OCZ-VERTEX450
Serial Number:    OCZ-57V17A23R739NJ86
LU WWN Device Id: 5 e83a97 632619308
Firmware Version: 1.0
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Feb 21 15:07:41 2014 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x1d) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Abort Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x00)	Error logging NOT supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   0) minutes.
Extended self-test routine
recommended polling time: 	 (   0) minutes.

SMART Attributes Data Structure revision number: 18
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0000   216   216   000    Old_age   Offline      -       63960 (0 23540)
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       2066
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       234
171 Unknown_Attribute       0x0000   000   000   000    Old_age   Offline      -       0
174 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       3318181484
195 Hardware_ECC_Recovered  0x0000   100   100   000    Old_age   Offline      -       3649066674
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       63544 (0 59146)
197 Current_Pending_Sector  0x0000   100   100   000    Old_age   Offline      -       2607393518
208 Unknown_SSD_Attribute   0x0000   100   100   000    Old_age   Offline      -       59
210 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       58
233 Media_Wearout_Indicator 0x0000   097   097   000    Old_age   Offline      -       97
241 Total_LBAs_Written      0x0000   100   100   000    Old_age   Offline      -       1814
242 Total_LBAs_Read         0x0000   100   100   000    Old_age   Offline      -       1516
249 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       110778826833771

Warning! SMART ATA Error Log Structure error: invalid SMART checksum.
SMART Error Log Version: 1
No Errors Logged

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.
SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


Selective Self-tests/Logging not supported
 
I was going to point you to a step by step secure erase procedure using hdparm however the info you posted indicates that the drive its locked. I believe if you don't know the unlock password you can not continue with a secure erase.
 
You need to know the password. I am not sure if there is a default password for your SSD or something else is in play. Hopefully someone else knows. I have only seen drives that were not locked when I tried the secure erase.

BTW: Here are the instructions to secure erase. If you can unlock the drive you can try this (remember to use /dev/sdb instead of /dev/sdx):

http://tinyapps.org/docs/wipe_drives_hdparm.html
 
A bit of Googling shows people with similar problems; writing a support ticket to OCZ now

Thanks for all your help drescherjm :cool:
 
MrReplay said:
Do you have any idea how it got locked?
Click to expand...

Here are some possibilities I can think of at the moment: Could be the BIOS. Could be the firmware on the drive autolocking when it has problems. The drive could be locked with soem default password. Could be a virus set the password.
 
You must log in or register to reply here.
Back
Top