wipper.sh fails, input/output error

[monkman]

monkman@pc:~/Downloads/hdparm-9.28$ sudo /sbin/wiper.sh --commit /dev/sda6

wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord.
Preparing for online TRIM of free space on /dev/sda6 (ext4 mounted read-write at /).

This operation could silently destroy your data.  Are you sure (y/N)? y
Creating temporary file (5926453 KB).. 
Syncing disks.. 
Beginning TRIM operations..

/dev/sda:
trimming 11852912 sectors from 931 ranges
FAILED: Input/output error
Removing temporary file..
Syncing disks.. 
Aborted.

any ideas what goes wrong here? i got the intel x25-v ssd, ubuntu 9.10 64bit, kernel 2.6.32.

thx!

[Footer]

Did you ever get your problem figured out? I"m having the same issues:

footer@kubuntu64:~$ sudo /sbin/wiper.sh /dev/sdc1 --commit

wiper.sh: Linux SATA SSD TRIM utility, version 2.5, by Mark Lord.
Preparing for online TRIM of free space on /dev/sdc1 (ext4 mounted read-write at /).

This operation could silently destroy your data.  Are you sure (y/N)? y
Creating temporary file (24390500 KB).. 
Syncing disks.. 
Beginning TRIM operations..

/dev/sdc:
trimming 27099135 sectors from 512 ranges
succeeded

/dev/sdc:
trimming 18554281 sectors from 512 ranges
FAILED: Input/output error

/dev/sdc:
trimming 1999248 sectors from 512 ranges
FAILED: Input/output error

/dev/sdc:
trimming 893128 sectors from 512 ranges
FAILED: Input/output error

/dev/sdc:
trimming 235208 sectors from 138 ranges
FAILED: Input/output error
Removing temporary file..
Syncing disks.. 
Done.
footer@kubuntu64:~$

It succeeds on the larger sector but fails on the rest. I've run fsck on my 32GB OCZ-Vertext SSD and it comes back clean. It was working fine under Kubuntu 9.04, seems it just started under 10.04. My kernel is 2.6.32-21-generic.

Any thoughts would be appreciated!

[monkman]

i'm afraid not. running windows 7 now and the intel toolbox... for now no linux left here...

[Footer]

Ahh, too bad (or good for you!) depending on how you look at it.

I hope that wasn't the reason you went back to Windows. Re: the subject problem, I ran wiper.sh many times in a row and the last time, I got this:

footer@kubuntu64:~$ sudo /sbin/wiper.sh /dev/sdc1 --commit

wiper.sh: Linux SATA SSD TRIM utility, version 2.5, by Mark Lord.
Preparing for online TRIM of free space on /dev/sdc1 (ext4 mounted read-write at /).

This operation could silently destroy your data.  Are you sure (y/N)? y
Creating temporary file (24390444 KB).. 
Syncing disks.. 
Beginning TRIM operations..

/dev/sdc:
trimming 27099135 sectors from 512 ranges
succeeded

/dev/sdc:
trimming 18554281 sectors from 512 ranges
succeeded

/dev/sdc:
trimming 1999248 sectors from 512 ranges
succeeded

/dev/sdc:
trimming 893128 sectors from 512 ranges
succeeded

/dev/sdc:
trimming 235096 sectors from 138 ranges
FAILED: Input/output error
Removing temporary file..
Syncing disks.. 
Done.
footer@kubuntu64:~$

So I'm not sure what's going on but I'll keep looking. I assume everything works fine in Windows and your SSD gets trimmed automagically?

[monkman]

i'd love to use ubuntu as "mainsystem", need windows though for some certain things but only once a month.

got an asus xonar essence st, which doesn't do what i want under linux... should run, but doesn't. and then there is the thing about resampling in alsa...

in my opinion windows sucks. big time. usability is horrible. wtf do i need antivirus software for? just slows down my system and costs me money...

and the nsa backdoors... just doesn't feel right.

ubuntu felt just right...

[Footer]

Ahh, well, I do hope you get back to Ubuntu soon monkman!

And habtool, thanks for your persistence on this issue. Looking forward to hearing back from the developer. I had no issues while running under 9.10 (I misstated 9.04 in an earlier post) so I'm thinking it might have to do with the newer kernel?

Thanks.

[habtool]

I have contacted Mark Lord, the Trim/hdparm developer, and will post back here if I hear back from him. I sent him a message on the projects source-forge page.

I sent him this:

Hi
On Ubuntu Lucid LTS 10.04
Kernel 2.6.32-22-generic
i686
hdparm-9.28
wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord.

Also a post on ubuntu forums where other are having the problem:
http://ubuntuforums.org/showthread.php?p=9234802

sudo ./wiper.sh --commit /dev/sdc5

wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord.
Preparing for offline TRIM of free space on /dev/sdc5 (ext4 non-mounted).

This operation could silently destroy your data. Are you sure (y/N)? y
Syncing disks..
Beginning TRIM operations..

/dev/sdc:
trimming 32870688 sectors from 5724 ranges
FAILED: Input/output error
Aborted.

[dcstar]

monkman@pc:~/Downloads/hdparm-9.28$ sudo /sbin/wiper.sh --commit /dev/sda6

wiper.sh: Linux SATA SSD TRIM utility, version 2.6, by Mark Lord.
Preparing for online TRIM of free space on /dev/sda6 (ext4 mounted read-write at /).

This operation could silently destroy your data.  Are you sure (y/N)? y
Creating temporary file (5926453 KB).. 
Syncing disks.. 
Beginning TRIM operations..

/dev/sda:
trimming 11852912 sectors from 931 ranges
FAILED: Input/output error
Removing temporary file..
Syncing disks.. 
Aborted.

any ideas what goes wrong here? i got the intel x25-v ssd, ubuntu 9.10 64bit, kernel 2.6.32.

thx!

Just out of interest, when I downloaded the hdparm package I had to compile a new version of it which I then copied to /usr/sbin. Then the wiper.sh command worked on my SSD.

It may be worthwhile for people to compile their own versions rather than using a pre-compiled version that may not be 100% compatible with their setup.

[gibbylinks]

Just out of interest, when I downloaded the hdparm package I had to compile a new version of it which I then copied to /usr/sbin. Then the wiper.sh command worked on my SSD.

It may be worthwhile for people to compile their own versions rather than using a pre-compiled version that may not be 100% compatible with their setup.

Yes I did this today and got it working on my system.

Just a quick query, how often should you run wiper.sh ?

Thanks

[dcstar]

Yes I did this today and got it working on my system.

Just a quick query, how often should you run wiper.sh ?

It depends on how much your SSD slows down due to running out of empty blocks when writing (it will still work, but just slower). If you have a busy system where you do lots of writes, then once a week or more frequently.

Remember that you only need to use wiper.sh with pre 2.6.33 kernels that do not support TRIM. A TRIM kernel with the discard option in the fstab file will automatically do what wiper.sh manually does. 10.10 already uses TRIM kernels, 10.04 LTS is supposed to have one backported (one day.....)