**** BEGIN LOGGING AT Sat Jul 09 23:59:56 2005
Jul 10 20:05:37 <jbowler-away> I turboed two NSLU2 by the R64->R81 move (giving the 3 bits the value 100).  Seems to work fine (266.24MHz)
Jul 10 21:04:14 <jacques> hi jbowler-away what did you say about losing one of your slugs?
Jul 10 21:12:15 <dyoung> I was halfway wondering if it slithered away....
Jul 10 21:26:36 <jbowler-away> jacques: it was the Maxtor 250 GByte (1-Touch-2), the slug was fine...
Jul 10 21:27:32 <jacques> jbowler-away, ah, sorry :-(
Jul 10 21:29:21 <jbowler-away> Somehow the Maxtor seemed to get a significant number of inodes in a very bad state - apparently I/O errors on the disk.
Jul 10 21:29:42 <dyoung> what is it with nslu2-linux devs and dead disks last week.
Jul 10 21:29:51 <dyoung> Everyone had one.
Jul 10 21:30:16 <jbowler-away> That happened a couple of weeks ago I think - last week I got hit by an 8 hour power cut, so I had to shut down the slug...
Jul 10 21:30:33 <jbowler-away> So I said, "what an excellent time to run fsck"
Jul 10 21:30:35 <jbowler-away> Duh.
Jul 10 21:30:40 <dyoung> heh.
Jul 10 21:30:48 <dyoung> Murphy can Bite Me.
Jul 10 21:31:08 <jbowler-away> I personally think the person who wrote e2fsck should be given a big banana
Jul 10 21:31:13 <jbowler-away> somewhere painful
Jul 10 21:31:42 <jbowler-away> I had do dead-mans-handle the program with a red sharpie marker and a stapler.
Jul 10 21:32:02 <dyoung> hehe
Jul 10 21:32:18 <dyoung> fsck and I have a sordid history too.
Jul 10 21:32:22 <jacques> jbowler-away, did you lose data?
Jul 10 21:32:31 <jbowler-away> Yes.
Jul 10 21:32:51 <jbowler-away> But it's about a 200GByte partition and only a very small amount was lost...
Jul 10 21:33:17 <jacques> I have had good experience with a program that's like dd but handles errors gracefully - I recovered data from one of my 250GB Maxtors that way
Jul 10 21:33:25 <jacques> ah ok
Jul 10 21:33:33 <jbowler-away> I don't care about that - the problem was that after fsck had got to the 'I will die on signal 11 after fixing two errors' state I used tar to read the readable parts....
Jul 10 21:33:58 <jbowler-away> So I have a tar archive which contains a 200GByte file, a 600GByte file and an 800GByte file.
Jul 10 21:34:09 <jbowler-away> (along with the files I want)
Jul 10 21:34:44 <jbowler-away> It took me about a day to read the data off it - because I have to --exclude those files or it fills the disk...
Jul 10 21:35:19 <jbowler-away> Oh, then I did an emerge --sync on gentoo, got a new X11 and spent half a day getting the font server working...
Jul 10 21:36:21 <dyoung> jacques, what program was that?
Jul 10 21:40:42 <jacques> let me refind it
Jul 10 21:42:13 <jacques> I think it was this, but the name doesn't sound right: http://safecopy.sourceforge.net/
Jul 10 21:42:47 <dyoung> cool, I'll bookmark that.
Jul 10 21:43:05 <jacques> ah it was this (same principle) http://www.garloff.de/kurt/linux/ddrescue/
Jul 10 21:44:31 <jacques> jbowler-away, uh-oh, I was wondering if there was going to be fallout from that gentoo x11 update
Jul 10 21:44:37 <dyoung> Ah.... Yeah, I did that with some old optical disks before.  dd with conv=noerror or something like that.
Jul 10 21:45:45 <jbowler-away> jacques: my xfs executable 'disappeared' on upgrade, that was the only problem apart from dealing with ~40 config files.
Jul 10 21:46:35 <jacques> jbowler-away, it seems to default to -font-server now
Jul 10 21:46:45 <jbowler-away> To get xfs back I had to add 'font-server' to my USE flags - but I don't know that was the right fix - the upgrade messages scrolled off the screen while I wasn't looking.
Jul 10 21:46:59 <jacques> it sounds right to me
Jul 10 21:47:55 <jacques> ugh, new portage now
**** BEGIN LOGGING AT Sun Jul 10 23:36:06 2005
**** BEGIN LOGGING AT Sun Jul 10 23:49:56 2005
**** ENDING LOGGING AT Sun Jul 10 23:59:57 2005