[ubuntu] Test If Your Laptop Drive Is Going To Die Prematurely - Please Read All Laptop Users

[nicedude]

MODELS OF LAPTOPS THIS IS CONFIRMED TO BE AFFECTING - PLEASE IF AFFECTED POST HERE SO THIS THREAD STAYS BUMPED UP FOR PEOPLE TO SEE - LIST IS NOT COMPLETE SO PLEASE TEST YOUR EQUIPMENT

ACER 5520-5716 - Reported by me
THINKPAD T6 - Reported by reacocard
VAIO VGN-N21E - Reported by playroll
ASUS F3JA - Reported by boppp
Acer Aspire 7520-5839 - Reported by Anduu
HP dv6000 - Reported by ASULutzy
Gateway M-1617 - Reported by johnl
Lenovo thinkpad R61i - Reported by miga
acer model 5920-ZD1 - Reported by beyboo
Hitachi HTS541616J9AT00 - reported by halfmanhalfbug
HP 530 - Reported by Arthur Archnix
Lenove T60p - Reported by Crackh34d
Toshiba Satellite A135-S2246 - Reported by volkswagner
Dell Inspiron 640M/E1405 - Reported by RRFarFar
Toshiba Satellite ProL10 - Reported by webabun
HP nx6125 - Reported by valloric
dell xps1210 - Reported by RRFarFar
Toshiba Satellite A75 S211 - Reported by wdecker
Dell Vostro 1000 - Reported by epitaph
Dell Vostro 1500 - Reported by goldenboy
HP dv6424 - Reported by linuxuser187
HP Pavillion dv9804 - Reported by epitaph
Compaq F572US - Reported by exharrison
Acer Aspire 5570-4315 - Reported by pharnet
HP 6710B - Reported by joshoekstra
Acer Aspire 7520-5A2G12Mi - Reported by Minardi
Gateway M-6846 - Reported by Recruit0
Dell Inspiron 6400 - Reported by Lapino
HP DV6810us - Reported by packman1234
Packardbell EASYNOTE_MX67-O-070 - Reported by Kestol
HP Pavilion dv2058ea - Reported by crisswyatt
Sony Vaio VGN-FZ180E - Reported by G@BO
Asus U6s - Reported by kuyote
Toshiba Satellite A105-S4254 - Reported by darco
Dell Latitude D520 - Reported by llevering
Dell Vostro 1200 - Reported by Super Jamie
HP NX7400 - Reported by Geniusj
Qosmio F40 - Reported by marcon00
Dell Inspiron 1720 - Reported by Cantodea
Zepto Znote 6615WD - Reported by Rokuta
HP nx6325 - Reported by Andycas
Toshiba Portege 4010 - Reported by iamvlad
HP dv 9000 dv9058ea - Reported by qbashi
Dell Inspiron 1520 - Reported by LeoSolaris
Toshiba A135 S2386 - Reported by dirtblack
acer travelmate 4603 WLCi - Reported by ditdot
Znote 3215W - Reported by laoshi
Compaq v5207NR - Reported by strick242
lenovo y510 - Reported by tlcrepairs

DRIVES CONFIRMED BY MEMBERS TO BE AFFECTED
TOSHIBA MK2035GSS HARD DISK - Reported by linuxuser187
Hitachi HTS541612J9SA00 HARD DISK - Reported by epitaph
Western Digital WD3200BEVT-60ZCT0 - Reported by linuxuser187
TOSHIBA MK8037GSX - Reported by exharrison
Hitachi HTS54161 - Reported by pharnet
TOSHIBA MK2546GSX - Reported by joshoekstra
Hitachi HTS541612J9SA00 - Reported by Minardi
WDC WD3200BEVT-22ZCT0 - Reported by Recruit0
TOSHIBA MK2035GS - Reported by G@BO
Seagate ST9160821AS - Reported by kuyote
Toshiba 1234GXS - Reported by llevering
Samsung HM121HC ( 2.5" Hard disk ) - Reported by dmcn
Fujitsu MHY2250BH - Reported by Super Jamie
TOSHIBA MK8034GSX - Reported by Geniusj
Hitachi HTS542512K9SA00 - Reported by marcon00
SAMSUNG HM120JI - Reported by marcon00
Seagate ST9250827AS - Reported by Cantodea
Hitachi HTS721080G9SA00 - Reported by Rokuta
Samsung HM250JI - Reported by Andycas
ST94813A - Reported by Fenris_rising
Hitachi HTS542525K9SA00 - Reported by tlcrepairs
Hitachi-Travelstar 250GB 0A55566 - Reported by strick242
Seagate ST9808210A - Reported by ditdot

THE FOLLOWING LISTS OF AFFECTED SYSTEMS FROM OTHER SOURCES WERE COMPILED AND GIVEN TO ME BY REACOCARD FOR MEMBERS INFO - SO CLICK HIS STAR AS HE DESERVES YOUR THANKS

LIST OF DRIVES THIS IS BEEN REPORTED TO AFFECT
Fujitsu MHW2120BH
Hitachi C4K60 (HTC426060G9AT00)
Hitachi HTS541010G9SA00
Hitachi HTS541060G9AT00
Hitachi HTS541040G9AT00
Hitachi HTS541210H9SA00
Hitachi HTS721010G9SA00
Hitachi HTS541616J9SA00
Hitachi HTS541080G9SA00
Samsung MP0804H 80GB
Samsung HM12HII
Seagate Momentus 7200.1
Seagate ST910021AS
Seagate ST9160821AS
Seagate ST92811A
Toshiba MK1234GSX
Toshiba MK1032GSX
Toshiba MK3006GAL
Toshiba MK2035GSS
Western Digital WD1200VE
Western Digital WD800BEVS

COMPUTERS POTENTIALLY AFFECTED BY THIS BUG
Acer Aspire 1662wlm
Acer Aspire 1642 WLMi
Asus G1S-A1
Dell Inspiron 6400
Dell Latitude C640
Dell Insipron 9400
Dell Latitude C-840
Dell Latitude D830
Dell XPS M1210
Fujitsu P7230
HP compaq nw9440
HP Compaq nx6325
HP Pavilion dv6500
HP Pavilion dv6602
Thinkpad T61
Thinkpad T60
Thinkpad R52
Thinkpad R50e
Thinkpad T43
Thinkpad T42
Thinkpad T23
Thinkpad Z61
Thinkpad T60p
Toshiba P205
Toshiba M55

Thanks Reacocard for the lists & Thanks to Kestol for questioning the activity in first place.

Several links to offsite information about this bug as the one I got from a member and had posted before was dead.

Launchpad
https://bugs.launchpad.net/ubuntu/+s...ort/+bug/59695

Ubuntu brainstorm
http://brainstorm.ubuntu.com/idea/288/

Overclocking Wiki
http://www.overclockingwiki.org/foru...ead.php?t=1645

So everyone if you are interested in this bug the above links work and can possibly inform you better as to methods other than mine to fix this.


PLEASE POST IN THIS THREAD ANYONE WHO CONFIRMS THEIR LAPTOP IS SUFFERING FROM THIS WITH YOUR MODEL# SO I CAN POST IT HERE FOR OTHERS TO SEE

1. MORE INFO ON THIS PROBLEM IN GENERAL - THIS PROBLEM IS PRESENT IN MANY LINUX DISTROS NOT JUST UBUNTU BUT IT ONLY AFFECTS CERTAIN DRIVES

The problem occurs when APM ( power management ) is constantly parking and unparking your HDD due to aggressive power management and is a hardware firmware flaw present in certain brands & models of drives. If the problem exists for you it will increase your HDD cycle count rapidly and as for my drive it is rated for 600,000 cycles for its lifetime and I would have hit that in 8 months of constant use so please read and tell your friends using any OS to check it out on their laptops as well. I am just trying to save someone having their device bricked by this. I don't get any pay or even glory for my time to warn you so I am doing this out of the goodness of my heart to save you grief down the road. Someone else ( Kestol ) mentioned below asked the question about this abnormality and at first I thought he was wrong ( Sorry Kestol ) then I found that my laptop suffered from it so I made this thread to WARN YOU to test yours as well.

First thanks to Kestol for figuring out this was taking place. I believe through my research of this situation that this warrants enough concern that you should install the simple tool below and test your laptop since if this problem does what it looks like it can, this bug could cause your HDD to prematurely fail. If you don't believe me then I can at least say I warned you and my conscience is clear, plus I won't have to pay for your hardware when it goes poof. But for people who are affected & would rather protect themselves than risk damage, I have made a simple script to fix this problem. First I would recommend to anyone with a laptop to use the software in step 2 to test if your system is actually affected by this problem or not, if not then you don't need this script and you are fine ( Don't use the script if you are not affected ). If so however then I suggest you follow my instructions and implement this fix to stop the disk cycles from growing quickly and possibly killing your hard drive. I can confirm that this is present in Hardy 8.04 so the newest OS does not mean you are not affected, although this is not a Ubuntu flaw but a general OS one ( Google it and see for yourself that it can affect Linux & Windows ) MY DRIVE WAS DOING 120 CYCLES AN HOUR MEANING I WOULD EXCEED THE MANUFACTURERS RATED LIFE EXPECTANCY IN LESS THAN ONE YEAR

-----------------------------------------------------------------------------------------------
This problem is only present due to the existence of the three following factors:
* Hardware is set (default or otherwise) to aggressive power management, causing heads to park. (default behavior of many drives and often the only user available type of power management)
* Disk is touched often, causing heads to unpark. (default behavior of many distributions)
* Drives are spec'd to a limited number of these cycles. (600,000 is the most common, although some may be spec'd higher or lower).

Reasonable Limits / Criteria for a fix:
* There should be fewer than ~15 load cycles per hour, except during heavy usage while on battery.
* This provides a life expectancy of over four years, which is reasonable for a hard disk.
--------------------------------------------------------------------------------------------------------------
The above acceptable statements were taken from other web sources ( Launchpad bug report ) on this problem so I am only doing the best I can to offer advise and support since I hadn't seen anything about this here. If you do the test then multiply the figure you get by 4 ( If you waited 15 minutes ) and that will give you an hourly increase count from there it is up to you if the numbers of hours of operation until your drive will reach its rated lifespan for this activity is acceptable or not as your the one who will have to replace your drive if it dies.

I did some calculations and made these tables so everyone could easily see what their result means to them.

If you have your laptop on 8 hours per day
15 cycles per hour - how long till 600,000 barrier 13.5 yrs
25 cycles per hour - how long till 600,000 barrier 8.1 yrs
50 cycles per hour - how long till 600,000 barrier 3.9 yrs
75 cycles per hour - how long till 600,000 barrier 2.7 yrs
120 cycles per hour - how long till 600,000 barrier 1.6 yrs
200 cycles per hour - how long till 600,000 barrier 1.1 yrs

If you use it 12 hours per day
15 cycles per hour - how long till 600,000 barrier 9.0 yrs
25 cycles per hour - how long till 600,000 barrier 5.4 yrs
50 cycles per hour - how long till 600,000 barrier 2.6 yrs
75 cycles per hour - how long till 600,000 barrier 1.8 yrs
120 cycles per hour - how long till 600,000 barrier 1.1 yrs
200 cycles per hour - how long till 600,000 barrier 8.0 months

If you leave it on almost 24/7
15 cycles per hour - how long till 600,000 barrier 4.5 yrs
25 cycles per hour - how long till 600,000 barrier 2.7 yrs
50 cycles per hour - how long till 600,000 barrier 1.3 yrs
75 cycles per hour - how long till 600,000 barrier 10.9 months
120 cycles per hour - how long till 600,000 barrier 6.8 months
200 cycles per hour - how long till 600,000 barrier 4.0 months

More than 200 cycles per hour and you better fix it as that would be worse than mine was.
Math in these tables isn't perfect as I rounded and multiplied some figure to do it quickly, but its darn close.
--------------------------------------------------------------------------------------------------------------
everyone should be thankful for HalPomeranz & ethanay for the tips on how to test drive heat levels below in this guide. I have tested mine and my drive is showing 42C under high load with my fix in place so as for me all is well and I hope it will be for all of you as well. My only wish is to help this community and I hope this thread furthers that goal
--------------------------------------------------------------------------------------------------------------

2. HERE IS HOW TO TEST IF YOUR DRIVE IS BEING AFFECTED BY THIS SITUATION AND TEST YOUR TEMP AT SAME TIME

INSTALL SMART MONITOR TOOLS - Disk management software, command is following for install.

sudo aptitude install smartmontools

ONCE INSTALLED RUN THIS COMMAND - COPY THE WHOLE LINE AND PASTE IN A TERMINAL AND RUN IT AND IT WILL OUTPUT BOTH A LOADCYCLE COUNT AND TEMPERATURE FOR YOUR DISK
(Thanks to member HalPomeranz for the new command and thanks to member ethany for the original temp check advise and commands that I changed to this )

date; sudo smartctl -a /dev/sda | egrep '(Load_Cycle_Count|Temperature)'

MY OUTPUT AS AN EXAMPLE
193 Load_Cycle_Count 0x0012 083 083 000 Old_age Always - 171239
194 Temperature_Celsius 0x0002 137 137 000 Old_age Always - 40 (Lifetime Min/Max 11/54)

Notice the first line shows my load cycle count ( Look at last number )
And the second shows my temprature for my hard disk. Just write these both down on a piece of paper so we can refer back to them in a minute.

** NOTE
If your laptop disk is addressed as /dev/hda then change the above command to reflect that ( test for this with "sudo fdisk -l" and then look at output )

My sudo fdisk -l output as an example you can see my disk is addressed as sda

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2550 20482843+ 83 Linux
/dev/sda2 2551 3036 3903795 82 Linux swap / Solaris
/dev/sda3 3037 6683 29294527+ 83 Linux
/dev/sda4 6684 19457 102607155 b W95 FAT32

WAIT 15 MINUTES AND RUN THE COMMAND AGAIN

If in 15 minutes the load cycle count number listed in this commands output changes by more than 2-4 then it is probably too much for comfort, Mine with my fix in place has only increased by 8 in 12.5 hours when previous to fix it went up 120 per hour, which for my drive if running 24 hrs a day gave me a life span of about 8 months which is not very acceptable to me

3. IF YOU ARE AFFECTED THEN FOLLOW DIRECTIONS HERE TO USE MY FIX - PLEASE READ FULLY AND CAREFULLY AS INCORRECT IMPLEMENTATION WILL NOT PROTECT YOU

Your hard disk could be called either sda or hda as you should have learned in step 2 so figure out which your drive is called and then download the script that applies to it. Once downloaded to your desktop right click on the script and go to properties -> in the permission tab select to make the file executable ( this must be done with any script you download or make yourself ). Once you have it set as executable and its on your desktop ( I am assuming your desktop is called Desktop as in you have an English install - if not the script will still work but you must copy it to the 4 locations listed in another way) just run each of the four commands below in a terminal window to copy the script to each location it is needed so that it will fix this problem after you reboot.

I have found that a setting of -B 200 works just fine here and my cycle count has gone up 8 in 12.5 hours vs 120 per hour prior to this fix, so I am happy that it is fixed for me. If my script value doesn't work on your machines hard disk ( which so far I can report less than 10 people have said it didn't to me anyway ) then you will need to increase the -B number, the max is 255 which means drive APM OFF if that doesn't work then you will have to try to control the drive APM via your system BIOS or find out who makes the drive and see if they offer any utilities to control the cycling behavior.

Just remember your drive could be addressed as hda or sda - To check look in step 2. Just be sure to download the correct script and run the correct commands. While using the wrong one wont hurt anything it wont help anything either so just make sure you select the correct one and run the correct set of 4 copy commands. You just paste the commands into a terminal window ( Applications -> Accessories -> Terminal ) that saves you form having to type them

---------------------------------------------------------------------------------------------------------------

EDIT - Locations I am recommending changed after more research to ensure fix will continue after resume if you previously used my fix then you can safely delete the script from the following 2 locations as they are not needed although if left they should do nothing to harm anything but for clean system sake I give you the following commands that if you paste whole thing in a terminal one at a time they will remove them from the unneeded locations.

These commands are potentially dangerous if altered in any way so please be careful to copy it exactly. The sudo rm command can delete any file on your Ubuntu PC and thereby render it non functional but I have written these so that you will be prompted to confirm any deletion before it occurs ( So just make sure it says the name of my script file before pressing y for yes ) and it is set to be verbose thereby telling you exactly what it is doing. I just ran both of these on my system and it did exactly what I intended. So if copied fully and not modified then these will only delete my script and nothing else and on top of that it will prompt for confirmation before deletion.

sudo rm -i -v /etc/acpi/*load-count-fix.sh
sudo rm -i -v /etc/acpi/suspend.d/*load-count-fix.sh

The only reason I use the wildcard * is so that regardless of whether you have gotten the sda fix or the hda fix it will delete either and as written the command above will delete nothing else but my scripts.
-----------------------------------------------------------------------------------------------------------------

DOWNLOAD SCRIPT "99-sda-load-count-fix.sh" IF YOUR DRIVE IS CALLED SDA BY FDISK AND THEN USE THESE COMMANDS
* make sure to set script as executable before copying or it wont work

sudo cp -f ~/Desktop/99-sda-load-count-fix.sh /etc/acpi/ac.d/
sudo cp -f ~/Desktop/99-sda-load-count-fix.sh /etc/acpi/battery.d/
sudo cp -f ~/Desktop/99-sda-load-count-fix.sh /etc/acpi/start.d
sudo cp -f ~/Desktop/99-sda-load-count-fix.sh /etc/acpi/resume.d

DOWNLOAD SCRIPT "99-hda-load-count-fix.sh" IF YOUR DRIVE IS CALLED HDA BY FDISK AND THEN USE THESE COMMANDS
* make sure to set script as executable before copying or it wont work

sudo cp -f ~/Desktop/99-hda-load-count-fix.sh /etc/acpi/ac.d/
sudo cp -f ~/Desktop/99-hda-load-count-fix.sh /etc/acpi/battery.d/
sudo cp -f ~/Desktop/99-hda-load-count-fix.sh /etc/acpi/start.d
sudo cp -f ~/Desktop/99-hda-load-count-fix.sh /etc/acpi/resume.d

This will stop all the crazy load cycles that could endanger your drives lifespan.

After you use these commands to copy it where it needs to go just REBOOT for the changes to take effect for your system.

4. CONFIRM THAT THE FIX IS WORKING AND THAT TEMP HAS NOT INCREASED TO A DANGEROUS LEVEL

Just repeat the test command from step 2 then wait 15 minutes & run it again then compare the cycle count numbers again. It shouldn't go up at all this time really but 1 or 2 would be ok ( Mine doesn't go up at all ). Also you will have this figure go up by one no matter what each time you turn the PC off and then on as the drive parks when the system is shutdown regardless of APM settings. Also compare your temperature readings now that it is not being spun down all the time.

PLEASE AT THIS POINT GO TO MY THREAD ON THIS SUBJECT AND POST WITH THE FOLLOWING INFORMATION

Model of laptop & hard disk if known.
1 hour cycle count before fix & after
Temperature before fix & after fix

THIS WILL HELP OTHER USERS OUT ALLOT AND IS ALL I ASK OF YOU

I find my temperature is fine but every situation can be different so please check yours to be sure, as the last thing I want to do is solve one problem only to cause you another.

Anything over 50C needs investigating for your equipment
And anything over 60C is critically high for sure and please PM me immediately

This is rare as I have only had one person out of 200 who have used my fix to report this and in the end he didn't need the fix in the first place as he was only getting a 12 cycle increase per hour. That said if you do get excessive heat after applying my fix then PM me and I will work to help you solve it.

From my reading 35c - 50c seem to be safe for most drives but you might investigate your drive model to be sure you are within the acceptable heat range.

---------------------------------------------------------------------------------------------------------

IF YOU HAVE THE PROBLEM AND THIS DOESN'T WORK FOR YOU PLEASE LET ME KNOW BY PRIVATE MESSAGING ME, SO I CAN MAKE SURE I AM PROVIDING THE BEST SOLUTION POSSIBLE

HOW IT WORKS AND TIPS FOR IF IT WONT WORK FOR YOU

This script sets APM for your disk with a hdparm -B 200 value which is sufficient to stop all my extra cycles here anyway and should fix yours as long as you figure out what your disk device is called and get the appropriate script from the 2 below. You can use "man hdparm" without quotes to look at the manual for hdparm command and check out the -B setting for more info about what this is.

Note: Some disks are unresponsive to having their APM changed by the hdparm command, and therefore the workaround doesn't work or at least not with this value. It would be a good idea, in such cases, to disable APM in the BIOS if possible.

If this fix does not work for you ( and you tested that you have the problem ) then you will need to look in your system bios and disable APM ( Power Management - Outside of checking your drive temps the only negetive I see would be reduced laptop battery uptime as spinning the drive always will use more power. I have not however gotten anyones reports back on how much say in a % of time lost per charge this will reduce it by. If you know how long your laptop lasts on battery because you use it in that manner allot then I would be glad to hear how much this fix changed your uptime per charge as since I use mine like a desktop I don't know this myself, Please PM me with a battery uptime report anyone who can look into that.

Please make sure to remember to post your results so others can see them and the post will stay high on the lists so others can see it and be aware of this activity, thanks.

HOPE THIS HELPS YOU OUT EVERYONE - SO BE SAFE TEST YOUR LAPTOP AND USE IF NEEDED TO FIX THIS

[gsiliceo]

What if the cicle count returns nothing?

[nicedude]

If you mean didn't give any output and just went to a new command line, then one of 2 things. Either that you used it with device sda when your disk is addressed with hda ( check with sudo fdisk -l ) or that you didn't use sudo to give it admin power. More than likely your drive is addressed with hda though so the command for you would be the following

sudo smartctl -a /dev/hda | grep Load_Cycle_Count

Instead of

sudo smartctl -a /dev/sda | grep Load_Cycle_Count

Also make sure you installed the smart monitor tools as outlined in my directions.

[gsiliceo]

No, it wasn't that, to tell you the truth my hard disk is a "special" raptor 74 gbs super fast hard disk for coporate usage,
http://www.newegg.com/product/produc...82E16822136033

I have another one, and thankfully the output is ok between 15 min lapse.
I wish i could diagnose the other one, are there any other tools to check SMART? or maybe i have to recompile with special flags.

[nicedude]

I have a 27GB raptor in one of my PC's but I am not by that machine right now so I don't know. As far as I have seen reported this flaw mostly exists with certain laptop drives, mainly Western Digital brand has been claimed by many and I believe it is what is in my laptop ( don't want to reboot to look at bios right now since I am watching tonites episode of LOST on my laptop as I write this ). So you might want to google this linux flaw and see if you can find where it affects desktops as well. I think it is rooted in a laptops aggressive power management schemes due to battery power concerns coupled with flaws in the drive firmware ( Which I found western digital has been made aware and stated they do not support end linux users, now where have i heard that before ) . I don't think there is anything special about using smart monitoring tools on your raptor disk though, did you follow my suggestion to run a sudo fdisk -l and look at your drive table and see how it is addressed? then craft the smartmon command to reflect that address. If you cant figure it out send me the output of sudo fdisk -l ( thats a lower case L not a one even though they look the same on my screen so I will point it out)
and I will customize the command for you and PM it back

I am just trying to save someone a disk failure nightmare since my laptop was cycling 120 times an hour which would put it beyond manufacturers rated life expectancy in 5000 hours of use which I would like to avoid since I tend to keep PC's more than a couple years and am always squeezing life out of old ones

IN MIDDLE OF WRITING THIS I CHECKED SMARTMON PROJECT AT SOUREFORGE AND IT IS SUPPORTED BY VERSION 5.37 - WHICH IS WHAT IS IN THE REPOSITORIES SO YOU SHOULD BE ABLE TO USE SMARTMON TO QUERRY YOUR DISK

So check the fdisk output or PM it to me and you should be able to run smartmon on your raptor just in case so you can sleep at ease.

over 26 hours since I applied my fix to my laptop and my count is up 8 when it would have been up 3000 or so. I can sleep with 8 much more soundly.

Now I must return to lost ep 4x12 to get my fix. PM me back to get further help so I will see it easier ( Just click my name and select send private message )

Good Luck

[balagosa]

i will try that when i get home nicedude.

[gsiliceo]

Oh that is not a problem i know its sda the output

Disco /dev/sda: 74.3 GB, 74355769344 bytes 255 cabezas, 63 sectores/pista, 9039 cilindros Unidades = cilindros de 16065 * 512 = 8225280 bytes Identificador de disco: 0x56b756b7 Disposit. Inicio Comienzo Fin Bloques Id Sistema /dev/sda1 * 1 1912 15358108+ 7 HPFS/NTFS /dev/sda2 1913 4462 20482875 7 HPFS/NTFS /dev/sda3 4463 7012 20482875 af Desconocido /dev/sda4 7013 9039 16281877+ f W95 Ext'd (LBA) /dev/sda5 8800 9039 1927768+ 82 Linux swap / Solaris /dev/sda6 7013 8799 14354014+ 83 Linux Las entradas de la tabla de particiones no están en el orden del disco Disco /dev/sdb: 250.0 GB, 250059350016 bytes 255 cabezas, 63 sectores/pista, 30401 cilindros Unidades = cilindros de 16065 * 512 = 8225280 bytes Identificador de disco: 0x000c1ac5 Disposit. Inicio Comienzo Fin Bloques Id Sistema /dev/sdb1 1 17653 141797691 b W95 FAT32 /dev/sdb2 17654 30401 102398310 83 Linux

Hehe its spanish but you know, i use the sda to hold all my OS's (xp, vista, osx, linux+swap)
I think this is a bug in the SMART monitoring tools, i blame WD, i issued the command without grep

sudo smartctl -a /dev/sda

and i think this is the equivalent value

Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 943

Power cycle count, would that be something different? or is the one i must monitor?

[reacocard]

Does that actually work under pm-utils in hardy? It was my understanding that since pm-utils became default acpi scripts are no longer run on sleep/power events. (I have my own scripts running under pm-utils to fix this issue.)

[nicedude]

To gsiliceo I don't know why smartmon tools arn't even working for you. their homepage for their project is hosted at sourceforge so you might check that out if you ever want to use them. but since Raptor drives are top of the line and not used for laptops then it is probably ok as I can only say this effects my Acer 5520-5716 laptop with Hardy Heron 32bit 8.04 for sure but the guy who first asked about it has it on his laptop as well, so if you own any laptops or manage company laptops running any linux versions I would recommend you check this out on them.

To reacocard

I can't say anything about your hardware but on my laptop with updated 32bit hardy this was happening until I implemented this script fix and I can verify 100% that this is working for me on Hardy as my load cycle count has increased only 171210 to 171218 in 30+ hours of uptime ( I have left it on constantly to check ) while before it was increasing at roughly 120 cycles per hour. I don't blame the Ubuntu makers though as this is apparently a problem with linux in general. I just wanted to save people's laptop from this danger as I realized that if their drive fries in 1 year most people would blame Ubuntu for it and get really mad, I wan't Ubuntu to grow in user base and have a great reputation so that Microsoft can lose a few of their undeserved customers (OR ARE THEY HOSTAGES) .

[reacocard]

Originally Posted by nicedude I can't say anything about your hardware but on my laptop with updated 32bit hardy this was happening until I implemented this script fix and I can verify 100% that this is working for me on Hardy ...

Did you install hardy via upgrade from gutsy or a clean install? If via upgrade it's possible it left acpi in place. I should test this...

EDIT: Ah, think I found why they don't on my box. acpi-support, which is what runs those scripts, isn't installed on my system becasue I installed hardy during the development cycle. However the default clean hardy install now has this package, so it should work fine for most users. Sorry about the confusion.