Re: k3b iso-image write stops after writing iso, solved
Srdjan Todorovic <[email protected]> Fri, 28 Aug 2009 17:50:28 +0100 (BST)
| Newsgroups | gmane.comp.kde.k3b |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Fri, 28 Aug 2009, Julien Michielsen wrote: > > I'm glad you got it working. I've not had much success with the verify > > aspect of k3b - the last few times I tried to verify a disk, it always > > said it failed - so for about a year now I've resorted to creating an > > md5sum file of the disk contents, then after burning, I mount the disk > > and verify each individual file with md5sum -c option. > > That's much work. And, do you know the correct md5sums of all files? 1) Create directory that will contain your disk contents 2) copy files as you wish, in correct hierarchy using du to make sure you are below the size limit of the disk. 3) md5sum * > ../mydisk.md5 (or md5deep -r -l * > ../mydisk.md5 if the dir contains subdirectories) 4) burn disk 5) mount, cd to mounted disk path, md5sum -c /path/to/md5sumfile.md5 So the sums of all the files are taken before writing the disk, and so you have these for reference. I know - it's not a GUI solution so not everyone will like it - but that's how I do it. It's not a huge amount of work. And this way if there are problems, you get a report telling you which *file* was bad, rather than K3b saying "ooops! disk is bad" (but I'm not sure if K3b nowadays will report which files failed). Regards, Srdjan ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july