Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Here's the scenario, I'm backing up some files into a DVD using an automated script. The script just takes the database entries as well as the files associated with them, and transfers them into the DVD. As I'm backing up, I'm pulling up the recording.log to make sure that it's backing up. It goes through and makes a file list of all the files on the directory, then procceeds with burning the files. When it gets to about 32-34 percent the program closes the DVD. To my knowledge the script doesn't have anything keeping the dvd from backing up only 32-34% of the data.
and you expect some1 to know whats wrong without telling us the distro, your your hardware, the software, or even posting the script, or error messages ?
Greetings p8ntcraze, and welcome to LQ. I attempted to view the log file that you linked to, but unfortunately the operation timed out. I'd like to suggest that it would be better if you could post the contents in a post here, that way folks will be able to see the exact messages, and also, assuming that log file may be deleted someday, posting it here will make it permanent, and will allow any future visitors to be able to see that information.
I'd also like to reiterate the points that qwijibow raised. The more information and the more context a post can provide, the easier it is for others to respond. As you know, you can optionally choose to specify your distro(s) on your profile, and similarly a lot of folks include their system specs as part of their sig line, which can save having to retype the same info in multiple posts. -- J.W.
i once had a similar prob. the dvd recorder stoped at ~ 20/30%. it turned out that the driver (i use kernel 2.6 and dev=ATA) didn't work with dma switched on. it worked well when setting hdparm -d0 /dev/hdd (=my dvd+rw).
$link = mysql_connect ($options->opts["db_host"], $options->opts["db_user"], $options->opts["db_passwd"])
or die ("Could not connect");
mysql_select_db("recording");
// If the disc has been closed, everything is fine
if(!preg_match("/error/i",$dvdrecord_cmdl) && preg_match("/closing disc/",$dvdrecord_cmdl)) {
$query = "INSERT INTO backup (`backupsize`,`media`,`volumename`) VALUES ('$total','DVDR/RW','Grid Disk $disknr')";
mysql_query($query)
or die ("Query failed with message: ".mysql_error());
$id_backup = mysql_insert_id();
$query = "UPDATE files SET loc='DVDR/RW:Grid Disk $disknr',id_backup='$id_backup' ";
$query .= "WHERE id IN (" . implode(',',$idfiles) . ")";
mysql_query($query)
or die ("Query failed with message: ".mysql_error());
// Everything was written successfully
$query = "SELECT filename FROM files WHERE id_backup='$id_backup'";
$result = mysql_query($query)
or die ("Query failed with message: ".mysql_error());
while($row = mysql_fetch_array($result))
@unlink($row["filename"]);
}
@unlink($db_file);
@unlink($list_file);
?>
The recording log is waaay too big for me to post here, so i'll take out parts of it:
Executing 'mkisofs -r -v -V Grid Disk 3 -graft-points -path-list /tmp/files.list | builtin_dd of=/dev/cdrom obs=32k seek=0'
mkisofs 2.0 (i686-pc-linux-gnu)
Using CHRIS000.;1 for /CHRISTINE,20040429144536040,, (CHRISTINE,20040429144434361,,)
Using CHRIS001.;1 for /CHRISTINE,20040429144434361,, (CHRISTINE,20040429144346252,,)
Using CHRIS002.;1 for /CHRISTINE,20040429144346252,, (CHRISTINE,20040429144247368,,)
Using LINDA000.;1 for /LINDA,20040429144455282,, (LINDA,20040429144116658,,)
Using CHRIS003.;1 for /CHRISTINE,20040429144247368,, (CHRISTINE,20040429144030471,,)
Using CHRIS004.;1 for /CHRISTINE,20040429144030471,, (CHRISTINE,20040429143841895,,)
Using JIM_2000.;1 for /JIM,20040429144523513,, (JIM,20040429143813685,,)
Using CHRIS005.;1 for /CHRISTINE,20040429143841895,, (CHRISTINE,20040429143813103,,)
Using CHRIS006.;1 for /CHRISTINE,20040429143813103,, (CHRISTINE,20040429143744502,,)
Using CHRIS007.;1 for /CHRISTINE,20040429143744502,, (CHRISTINE,20040429143717934,,)
Using CHRIS008.;1 for /CHRISTINE,20040429143717934,, (CHRISTINE,20040429143608654,,)
Using JIM_2001.;1 for /JIM,20040429143813685,, (JIM,20040429143441199,,)
Using BONNI000.;1 for /BONNIE,20040429144427519,, (BONNIE,20040429143058045,,)
Using LINDA001.;1 for /LINDA,20040429144116658,, (LINDA,20040429142956630,,)
Using CHRIS009.;1 for /CHRISTINE,20040429143608654,, (CHRISTINE,20040429142952493,,)
Using CHRIS00A.;1 for /CHRISTINE,20040429142952493,, (CHRISTINE,20040429142901971,,)
For some reason i can't connect via ssh to the remote system that's having this problem. I'm expecting another RAID card to come in, in a couple of days, once i make the identical system, I'll post up what I can about the system.
Disk /dev/sda: 61.0 GB, 61000000000 bytes
255 heads, 63 sectors/track, 7416 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 7359 59006745 83 Linux
/dev/sda3 7360 7416 457852+ 82 Linux swap
[root@localhost root]#
There is a problem with the 2.6 kernel and burning files that are larger than 2.2 gig. Take a look at this link: http://lists.debian.org/cdwrite/2004/06/msg00083.html. The only option that I have found so far is to burn using ide-scsi drivers; the same way the 2.4 kernels do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.