Log in

No account? Create an account
pavelmachek's Journal
[Most Recent Entries] [Calendar View] [Friends View]

Saturday, May 14th, 2005

Time Event
Another day, another failed toshiba harddrive
I had really unlucky thursday, 12th: first horse kicked me, then another horse destroyed its rope, and then I left my keys in the stables. Bad, bad, bad.

So I had to return to stables at friday, 13th. Fortunately keys were there, and I took mare with her foal out. It went okay (which is quite good, considering this was first time foal got out of stables). I thought "hey, lucky friday 13th".. but not so fast.

I kept running one of my notebooks on for few days non-stop as a small "home server". At friday night, I was debugging Billionton bluetooth CF (works now), and server felt strangely slow over ssh. I did not investigate. (Mistake).

Today server started giving I/O errors. BAD. I'm now rsyncing data out of it... getting ~1MB/sec linear throughput thanks to all the successfull and sometimes unsuccessfull resets. Funny thing is that smart *still* thinks disk is healthy.
More fun with disks...
Guess what I got while copying data from broken toshiba 2.5" HDD onto external USB disk?

May 14 20:20:27 amd kernel: kjournald starting. Commit interval 5 seconds
May 14 20:20:27 amd kernel: EXT3 FS on sda1, internal journal
May 14 20:20:27 amd kernel: EXT3-fs: mounted filesystem with ordered data mode.
May 14 20:27:57 amd log1n[3168]: ROOT LOGIN on `tty5'
May 14 20:28:17 amd pam_limits[3253]: wrong limit value 'unlimited'
May 14 20:32:24 amd kernel: SCSI error : <1 0 0 0> return code = 0x8000002
May 14 20:32:24 amd kernel: sda: Current: sense key=0x4
May 14 20:32:24 amd kernel: ASC=0x4b ASCQ=0x0
May 14 20:32:24 amd kernel: end_request: I/O error, dev sda, sector 122597839
May 14 20:59:11 amd -- MARK --

Fun, fun. OTOH toshiba disk started to work better when I opened the window (that decreased temperature in room from ~23C to ~21.5C). Now it is back to normal speeds, and no ill effects can be seen. Or maybe it was because I took disk out to let it cool and generally played with it?

Strange thing is... I can see errors in syslog, but at command line level, no errors are reported. Is kernel doing retries for me?

<< Previous Day 2005/05/14
Next Day >>
My Website   About LiveJournal.com