Skip to contentSkip to conversation

strange xcdroast bug solved

DISCUSSION Rei Shinozuka 5 participants 10 messages Apr 7, 2004 – Apr 11, 2004 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

----- Forwarded message from Rei Shinozuka <[email protected]> -----

Subject: strange xcdroast bug solved
From: Rei Shinozuka <[email protected]>
Date: Wed, 7 Apr 2004 12:35:28 -0400
To: Thomas Niederreiter <[email protected]>

thanks, you da man. i built my own version of cdrtools and it no longer reports errors!!

-rei

Quoted 42 lines · Thomas Niederreiter

On Wed, Apr 07, 2004 at 05:29:11AM +0200, Rei Shinozuka wrote:

Hello Rei,

Quoted 10 lines

i have been using 98alpha13 for years on my thinkpad, and recently went to a desktop with alpha14 and i also built alpha15.

Linux tuxedo 2.4.22-1.2115.nptl #1 Wed Oct 29 15:31:21 EST 2003 i686 athlon i386 GNU/Linux

Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003 Jorg Schilling

the problem appears that xcdroast always reports errors when burning CDs, even though the logs do not show any evidence of trouble.

The alpha14 had exactly such a problem - due a little typo in my code the cdrecord error code was not evaluated correctly and some folks always got "Error writing tracks". This is fixed in alpha15, so I dont know whats happening.

I only note that you dont seem to use an official version of the cdrtools:

cdrecord: Warning: using inofficial libscg transport code version (schily - Red Hat-scsi-linux-sg.c-1.75-RH '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling').

Please compile cdrecord from the original sources and try again. I can just guess it reports an illegal value.

Create full debug output (FAQ) and then its much easier to see..

Regards,

Thomas

___ ___

 /   |   \  ___________   | REAL   : Thomas Niederreiter: Munich, Germany
/    ~    \/  _ \_  __ \  | EMAIL  : [email protected]
\    Y    (  <_> )  | \/  | WEB    : www.xcdroast.org
 \___|_  / \____/|__|     | 

\/ All I want is a warm bed and a kind word and unlimited power
-- Ashleigh Brilliant

Signature · 15 lines
Rei Shinozuka [email protected]
Ridgewood, New Jersey


----- End forwarded message -----

-- 
Rei Shinozuka [email protected]
Ridgewood, New Jersey

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#1 lore raw

Retrieving deleted files

We had a user leave our company recently, and he deleted a folder on the server that wasn't backing up. I know on Windows that, when you delete an item, you can use often use Norton Systemworks or Utilities to retrieve that file, as it doesn't securely delete.

What can I use on Linux to retrieve a deleted object?

Thanks,
Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#2 lore raw

Re: Retrieving deleted files

Quoted 6 lines · Eve Atley

We had a user leave our company recently, and he deleted a folder on the server that wasn't backing up. I know on Windows that, when you delete an item, you can use often use Norton Systemworks or Utilities to retrieve that file, as it doesn't securely delete.

What can I use on Linux to retrieve a deleted object?

This question is actually a bit dependent on what filesystem the Linux host uses. For ext2, a couple of possibilities are (these are the Debian package names; your distro may differ a bit) "e2undel" and "recover".

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#3 lore raw

RE: Retrieving deleted files

This question is actually a bit dependent on what filesystem the Linux host uses. For ext2, a couple of possibilities are (these are the Debian package names; your distro may differ a bit) "e2undel" and "recover".

That answer is probably ext3fs - I'm running Linux Redhat 9, latest kernel.

I did try recover, but could not get it to run; it says command not found.
I have tried to install recover and gtkrecover.

- Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#4 lore raw

RE: Retrieving deleted files

Quoted 10 lines · Eve Atley

This question is actually a bit dependent on what filesystem the Linux host uses. For ext2, a couple of possibilities are (these are the Debian package names; your distro may differ a bit) "e2undel" and "recover".

That answer is probably ext3fs - I'm running Linux Redhat 9,
latest kernel.

I did try recover, but could not get it to run; it says command
not found.
I have tried to install recover and gtkrecover.

When you "tried" to install recover (I assume from an rpm), did the install procedure indicate that it had succeeded or not? If not, what did it say?

What is the "it" that says "command not found"? It is a message from the shell (probably bash) that looks something like this:

        ray@kuryakin:~$ recover
        -bash: recover: command not found

Or does recover itself give you a message indicating that some other command cannot be found? (I'm assuming you tried this from a command line, not from the X frontend gtkrecover ... if not, please do so.)

Where is recover on the system?

Does "which recover" find it?

Does "find / -name recover" find it?

Were you trying to run recover as root or as an ordinary user? Could there be a PATH issue (what happens if you specify the path to the app explicitly)?

I've no actual experience here, but I'd bet that recover will work on ext3 ... in most respects, ext3 can fall back to ext2. And you can check /etc/fstab for the relevant partition to see what filesystem type you are using.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw

RE: Retrieving deleted files

Quoted 21 lines · Eve Atley

Hi Ray,

Quoted 2 lines

When you "tried" to install recover (I assume from an rpm), did the install procedure indicate that it had succeeded or not? If not, what did it say?

Yes, from an RPM. I get no error from the RPM install install; I do get what you indicate below when running recover from the command prompt:

         ray@kuryakin:~$ recover
         -bash: recover: command not found

I can not find recover on the system. "which recover" does not find it; find / -name recover either does nothing, or is taking so long I finally end up quitting the process.

'which recover' gives me the following:
[root@wow-rtr root]# which recover /usr/bin/which: no recover in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sb in:/usr/bin:/usr/X11R6/bin:/root/bin:/usr/local/mysql/bin)

Quoted 5 lines
Quoted 2 lines

Were you trying to run recover as root or as an ordinary user? Could there be a PATH issue (what happens if you specify the path to the app

explicitly)?

I am definitely running as root.

Well, as it turns out, recover doesn't work with ext3 anyway ... at least not according to its entry in the Debian package directory, and the description at the upstream site (http://recover.sourceforge.net/linux/recover/).

This source -- http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html -- says that true undeleting (of the sort that recover does) is not possible with ext3. But a cruder sort of recovery may be possible ... see http://recover.sourceforge.net/unix/ for instruction.

As to the install itself ... either there is a problem with the RPM or it places recover in some truly odd location (Debian installs it in /usr/sbin, BTW, the usual place for this sort of app). I'm cc'ing this back to the list in case someone more used to working with RPM-based distros can help you here.

Sorry I do not have better news for you.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#7 lore raw

RE: Retrieving deleted files

Thanks so much for your help, Ray.

I have tried the instructions at:
http://recover.sourceforge.net/unix/
(one of the first things I did try)
...and I got a whole lot of garbage spit back to my screen; so much so, I had to quit.

I am attempting to do something along these lines:

	grep -a -B10000 -A0 "wowerpresumes" /dev/hdfb

...and since I'm not sure what to put for B and A, I may be doing something wrong here. I don't recall how large the directory was 'before' things were deleted.

- Eve

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#8 lore raw

RE: Retrieving deleted files

Quoted 8 lines · Eve Atley

Thanks so much for your help, Ray.

I have tried the instructions at:
http://recover.sourceforge.net/unix/
(one of the first things I did try)
...and I got a whole lot of garbage spit back to my screen; so much so, I had to quit.

Quoted 7 lines

I am attempting to do something along these lines:

        grep -a -B10000 -A0 "wowerpresumes" /dev/hdfb

...and since I'm not sure what to put for B and A, I may be doing something wrong here. I don't recall how large the directory was 'before' things were deleted.

You do not need to know how large the directory was. This approach, as I read it (I've never actually used it myself), is limited to recovering text files. The trick is that you need to know something about the contents of some line of the file you want to recover. Then, you use grep to examine the raw partition (in this case, /dev/hdfb) as a single file (the -a switch tells grep to pretend the file is text), and it will turn up each instance of what you entered, reporting back the preceding "B" lines of text, the line itself, and "A" lines of following text.

Since you selected a very large value for B and 0 for A, you get a mess to the screen when you try this.

There is no general way to specify "right" values for A and B. You simply have to know something about the structure of the file. And since this approach will (I think) examine the filesystem linearly, a fragmented file will not be recoverable this way. Nor will a directory, which is really just a list of inode entries, which themselves can be scattered anywhere convenient on the filesystem. (And what I read about ext3 says the inode tables will be zero'd on deletion anyway.)

I did a bit more searching and still cannot find any undelete program tailored to ext3. I did find this one for ext2 -- http://www.data-recovery-software.net/Linux_Recovery.shtml -- that MIGHT be worth a look, since its description seems to indicate that it does not depend on the inode table to recover. And this one -- http://www.securiteam.com/tools/6R00T0K06S.html -- is not specific about what filesystems it will work on. The Debian package tct (Coroner's Toolkit) also includes a program called unrm, but I don't know if it is the same one.

Finally, my search turned up a couple of references to www.experts-exchange.com, a site that requires registration. You might want to check its resources.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#9 lore raw

Re: Retrieving deleted files

In reply to Eve Atley
Quoted 8 lines · Eve Atley

Thanks so much for your help, Ray.

I have tried the instructions at:
http://recover.sourceforge.net/unix/
(one of the first things I did try)
...and I got a whole lot of garbage spit back to my screen; so much so, I had to quit.

Quoted 7 lines

I am attempting to do something along these lines:

	grep -a -B10000 -A0 "wowerpresumes" /dev/hdfb

...and since I'm not sure what to put for B and A, I may be doing something wrong here. I don't recall how large the directory was 'before' things were deleted.

What you're doing is using the grep command to find some relatively unique string of data in your file, and then printing the data before, and after, that string.

-A and -B signiy the number of lines after (-A) and before (-B) tthe matched string to print...

The 'string' is actually a grep pattern, to look for, not a fixed string (unless you use fgrep instead of grep).

so, as an example -- if you'r trying to find a deleted /etc/passwd , you might look for the entry for root, with:

grep -A200 -B2 'root:[^:]*:0:0:' /dev/hda3

(presuming that the /etc/ driectory is on /dev/hda3)

note that I'm presuming that you understand grep regular expressions... It looks for 'root:' followed by any number of characterss other than colons ('[^:]*) followed by :0:0: which are the userid and groupid of the root user.

Since, for most incarnations of the /etc/passwd file the
root entry is the first, I'm only printing 2 lines before (just in case), and 200 lines after (presuming I'm expecting the file to be less than 200 lines long.

if you're lucky, you'll only find one copy of the file on your partition.

The upshot is that the ext3 filesystem does a pretty thorough job of deleting any residual metadate when it removes your files. (Unlike dos, which just zeroes the first byte of the name).

Zherefore you're left hunting thru the raw disk, hoping that the file you're looking for hasn't been fragmented into 2 or more pieces (if it has, then you're going to have to do more searching for the second and subsequent pieces).

you basically want to look for a string/pattern that will (hopefully) uniquely identify your file.. You want something that is guaranteed to be in the file, and something unlikely to be found in any other random file.

I guess, if somebody wanted to be really fancy, it might be possible to create a bitmap of allocated blocks on the disk, and only search in the unallocated space for your string

I'll leave that as an exercise for the reader :-).

Signature · 9 lines
Stephen Samuel +1(604)876-0426                [email protected]
		   http://www.bcgreen.com/~samuel/
   Powerful committed communication. Transformation touching
     the jewel within each person and bringing it to light.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#10 lore raw

Re: Retrieving deleted files

In reply to Ray Olszewski
Quoted 7 lines · Ray Olszewski

As to the install itself ... either there is a problem with the RPM or it places recover in some truly odd location (Debian installs it in /usr/sbin, BTW, the usual place for this sort of app). I'm cc'ing this back to the list in case someone more used to working with RPM-based distros can help you here.

Sorry I  do not have better news for you.

AFAIK you cant undelete with ext3.

http://www.linuxmafia.com/faq/Filesystems/ext3-no-undeletion.html

Signature · 15 lines
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
[email protected]
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs