http://bugzilla.novell.com/show_bug.cgi?id=564304 http://bugzilla.novell.com/show_bug.cgi?id=564304#c7 Tejun Heo <teheo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |carlos.e.r@opensuse.org --- Comment #7 from Tejun Heo <teheo@novell.com> 2009-12-17 00:38:36 UTC ---
Could growisofs fail and wodim suceed?
Sure, it can. As I wrote before, while burning / ripping, the kernel and driver just play a messenger role between the application and the drive. If your drive is peculiar and unhappy with certain command sequence, different apps can definitely make or break it. Another possibility is that your previous blank media was just faulty but you tested it more than once, right?
A funny thing: the just burned session is not mountable right after burning:
This too is expected. Many drives need reload after burning to recognize the burned media. One of the reasons why so many burning apps eject the drive after burning is complete. So, I think you'll need to retry with growisofs and find out whether different burning programs indeed make difference? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.