Intel SSD 520 - problem after resume from sleep mode

[idata]

Hi,

i upgrade Asus ntb UL30VT with Intel SSD 520 120GB.

After try to "hibernate-ram" ntb going succesfully to hibernation, but when i try resume,

system resume ok, but disk is gone away from system.

Filesystem is not availible and write SIGBUS errors (in /var/log/messages i have lot's of messages that you cant write to system etc).

In previous same system i have OCZ Octane S2 SSD without problem, i only copy system to new disk.

I use Gentoo linux, I try severals kernel (vanila, gentoo-sources, tuxonince, reinstaling and reconfigure hibernate-scripts, try disable AHCI access. etc..)

I found that exists lots'of users that have similar (or same) problem on other operatin systems, for example:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930561 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930561

http://www.sevenforums.com/hardware-devices/129647-hdd-disappears-resume-sleep.html http://www.sevenforums.com/hardware-devices/129647-hdd-disappears-resume-sleep.html

you can search more with google (intel ssd "resume from sleep" problem)

I have actual firmware.

It seems that is problem of harddrive, I think right now then returned as a claim.

Have anyone solution on similar problem?

Thanks Zdenek

# smartctl -i /dev/sda

smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.0.26-tuxoniceasusUL30] (local build)Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===

Model Family: Intel 520 Series SSDsDevice Model: INTEL SSDSC2CW120A3Serial Number: CVCV2--CENSORED---

LU WWN Device Id: 5 001517 bb27fb0e0

Firmware Version: 400iUser Capacity: 120 034 123 776 bytes [120 GB]Sector Size: 512 bytes logical/physical

BIOS Information

Vendor: American Megatrends Inc. Version: 210 Manufacturer: ASUSTeK Computer Inc. Product Name: UL30VT

# emerge --info

Portage 2.1.10.49 (default/linux/amd64/10.0/desktop/kde, gcc-4.5.3, glibc-2.14.1-r2, 3.0.26-tuxoniceasusUL30 x86_64)=================================================================System uname: Linux-3.0.26-tuxoniceasusUL30-x86_64-Genuine_Intel-R-_CPU_U7300_@_1.30GHz-with-gentoo-2.1

# hdparm -t /dev/sda

/dev/sda:

Timing buffered disk reads: 730 MB in 3.00 seconds = 243.18 MB/sec

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

5 Reallocated_Sector_Ct 0x0032 100 100 000 Old_age Always - 0 9 Power_On_Hours_and_Msec 0x0032 000 000 000 Old_age Always - 894830h+14m+44.020s 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 71170 Available_Reservd_Space 0x0033 100 100 010 Pre-fail Always - 0171 Program_Fail_Count 0x0032 100 100 000 Old_age Always - 0172 Erase_Fail_Count 0x0032 100 100 000 Old_age Always - 0174 Unexpect_Power_Loss_Ct 0x0032 100 100 000 Old_age Always - 62184 End-to-End_Error 0x0033 100 100 090 Pre-fail Always - 0187 Uncorrectable_Error_Cnt 0x000f 100 100 050 Pre-fail Always - 3057045192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 62225 Host_Writes_32MiB 0x0032 100 100 000 Old_age Always - 4785226 Workld_Media_Wear_Indic 0x0032 100 100 000 Old_age Always - 65535227 Workld_Host_Reads_Perc 0x0032 100 100 000 Old_age Always - 20228 Workload_Minutes 0x0032 100 100 000 Old_age Always - 65535232 Available_Reservd_Space 0x0033 100 100 010 Pre-fail Always - 0233 Media_Wearout_Indicator 0x0032 100 100 000 Old_age Always - 0241 Host_Writes_32MiB 0x0032 100 100 000 Old_age Always - 4785242 Host_Reads_32MiB 0x0032 100 100 000 Old_age Always - 1259249 NAND_Writes_1GiB 0x0013 100 100 000 Pre-fail Always - 95h

# hdparm -i /dev/sda

/dev/sda:

Model=INTEL SSDSC2CW120A3, FwRev=400i, SerialNo=CVCV2--------------

Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7

* signifies the current active mode

# mountrootfs on / type rootfs (rw)/dev/root on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,commit=6000,barrier=1,stripe=128,data=ordered,discard)

[UHans]

Rhyando wrote:

Hello all,

i want to share my HP elitebook 8460p with SSD 320 series problems.

[...]

Anybody know how to fix SSD 320 series harddrive without secure erase it ?

Look, I feel your pain. Having lost data due to a drive failure is not fun.

But copy/pasting your exact same question into 7 different threads is not increasing your chance of getting constructive feedback. On the contrary. It is considered spamming. And it is especially off topic for this thread, as it revolves around the 520 series, not the 320.

With that said, I have not heard of a confirmed working solution for your issue other than secure erasing it (and thereby definitively deleting all data). This guy ( http://communities.intel.com represents a company that claims to be able to recover data from a 8MB'ed drive for an undisclosed amount of money (probably not cheap).

Please continue the 320 discussion here:

[idata]

i'm sorry about the post that i wrote. I miss to read the 520 series in the topic above.. Because i think a lot of people already experienced this issue. I hope intel will heard this and make a solution as soon as possible. By the way, thank you for your suggestion. I will take a look of those website that you gave.

[idata]

POTENTIAL SOLUTION!

I had exactly the same problem on my elitebook 8440p

TL;DR; Only got round it by turning OFF the ATA drive lock. Sleep/resume then works fine. this does of course negate most of the security on the drive, making the whole thing bloody pointless. Whether it's a problem with this drives firmware, or the HP implementation of DriveLock, who knows. I do know that when my manager comes back and asks about how my trial of the drive went I can honestly say 'we can't buy this model for our staff". So come on Intel, I've given you a clue, get your finger out and investigate.

Long version:

BIOS is latest version.

Tried a fresh Win7 install with the bios in RAID MODE instead instead, no dice.

Tried turning off all the power saving on the drive (i.e. Drive power down = never), no dice

Last thing I will try in the future, is perhaps if I use the master password rather than the user password (for drivelock) it might bypass whatever bug is causing the problem (though I doubt it).