Re: recovering from "rm -rf"

> that. I could have just resized the filesystem, but it was Reiser4. *sigh* And that is why there are two features in Reiser4 that I am still waiting for before I upgrade: resizing partitions (preferably both shrink and grow) and the repacker (online or otherwise). [And maybe something that wil

Re: recovering from "rm -rf"

michael chang wrote: > On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > >>Rudy Zijlstra wrote: >> >>>David Masover wrote: >>> >>> PFC wrote: >>Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I >>mv'ed all my data (about 100 gigs) from drive A to

Re: recovering from "rm -rf"

On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > Rudy Zijlstra wrote: > > David Masover wrote: > > > >> PFC wrote: > >> > >> > Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I > mv'ed all my data (about 100 gigs) from drive A to drive B. Drive B > then had

Re: recovering from "rm -rf"

Rudy Zijlstra wrote: > David Masover wrote: > >> PFC wrote: >> >> Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I mv'ed all my data (about 100 gigs) from drive A to drive B. Drive B then had its power plug fall out (don't ask me how I managed that), I

Re: recovering from "rm -rf"

Aaron D. Ball wrote: > PFC wrote: > >> You probably fried the electronics... if the heads are still OK, >> you could recover your data by exchanging the PCB from a brand new >> drive, with the fried PCB of the old drive. You need some electronics >> skillz, but a friend of mine did this (it

Re: recovering from "rm -rf"

David Masover wrote: PFC wrote: Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I mv'ed all my data (about 100 gigs) from drive A to drive B. Drive B then had its power plug fall out (don't ask me how I managed that), I plugged it back in (stupid!) -- there was a spark

Re: recovering from "rm -rf"

PFC wrote: > >> Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I >> mv'ed all my data (about 100 gigs) from drive A to drive B. Drive B >> then had its power plug fall out (don't ask me how I managed that), I >> plugged it back in (stupid!) -- there was a spark -- drive B no

Re: recovering from "rm -rf"

I have actually done this a couple of times with modern drives and found it shockingly easy. You buy an identical drive, unscrew the board, and screw the other board in, and it just works. The contacts are little springs that connect correctly as long as the board is screwed on properly

Re: recovering from "rm -rf"

PFC wrote: You probably fried the electronics... if the heads are still OK, you could recover your data by exchanging the PCB from a brand new drive, with the fried PCB of the old drive. You need some electronics skillz, but a friend of mine did this (it was an adventure, as he had to

Re: recovering from "rm -rf"

michael chang wrote: > On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > >>michael chang wrote: >> >>>On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: >>> >>> I've got a Reiser4 partition which I just moved (mv) a bunch of stuff off of, onto another drive. The other drive died imme

Re: recovering from "rm -rf"

Drive A is a 500 gig striped RAID. Drive B is a 200 gig IDE drive. I mv'ed all my data (about 100 gigs) from drive A to drive B. Drive B then had its power plug fall out (don't ask me how I managed that), I plugged it back in (stupid!) -- there was a spark -- drive B now won't spin up, and dr

Re: recovering from "rm -rf"

On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > michael chang wrote: > > On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > > > >>I've got a Reiser4 partition which I just moved (mv) a bunch of stuff > >>off of, onto another drive. The other drive died immediately after. > >> > >>I'm tryi

Re: recovering from "rm -rf"

michael chang wrote: > On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > >>I've got a Reiser4 partition which I just moved (mv) a bunch of stuff >>off of, onto another drive. The other drive died immediately after. >> >>I'm trying to repair the other drive, and to find any backups, but is >>t

Re: recovering from "rm -rf"

On 8/5/05, David Masover <[EMAIL PROTECTED]> wrote: > I've got a Reiser4 partition which I just moved (mv) a bunch of stuff > off of, onto another drive. The other drive died immediately after. > > I'm trying to repair the other drive, and to find any backups, but is > there a reasonable chance t

recovering from "rm -rf"

I've got a Reiser4 partition which I just moved (mv) a bunch of stuff off of, onto another drive. The other drive died immediately after. I'm trying to repair the other drive, and to find any backups, but is there a reasonable chance to recover from the good drive? Maybe force fsck.reiser4 to re

Re: Reiser4progs-1.0.4-1 issues with gcc-4.0.1

Hello Stef van der Made wrote: Dear Sir / Madam, I'm having an issue when compiling reiser4progs-1.0.4-1 using gcc-4.0.1. The compiler spits out the following error but I'm afraid that I'm not famaliar with C code or compilers. I hope you can fix this issue. gcc -DHAVE_CONFIG_H -I. -I. -I

Reiser4progs-1.0.4-1 issues with gcc-4.0.1

Dear Sir / Madam, I'm having an issue when compiling reiser4progs-1.0.4-1 using gcc-4.0.1. The compiler spits out the following error but I'm afraid that I'm not famaliar with C code or compilers. I hope you can fix this issue. gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include -D_RE