Re: "LUN appears to be stuck writing LBA=10h, retry in 0ms" kills my DVD+R...

[Alessandro Suardi <alessandro.suardi@oracle.com>]

Andy Polyakov wrote:
> >  a cheap Samsung TS-H552 (DL, +R/RW, -R/RW, ...). This one usually
> >  works but has already killed three DVD+Rs with the message in $subj;
> >  full messages (the one I was able to paste from my console, likely
> >  missing a few lines due to scrollback and copy-paste issues) follow.
> >
> > <this is the output of dvd+rw-mediainfo>
> >
> > INQUIRY:                [TSSTcorp][CD/DVDW TS-H552B][TS03]
> > GET [CURRENT] CONFIGURATION:
> >  Mounted Media:         1Bh, DVD+R
> > READ DVD STRUCTURE[#0h]:
> >  Media Book Type:       A1h, DVD+R book [revision 1]
> >  Media ID:              RITEK/R02
> > <OK, now burn it...>
> >
> > [root@donkey tmpburn]# growisofs -Z /dev/hdc=file.dvd
> > Executing 'builtin_dd if=file.dvd of=/dev/hdc obs=32k seek=0'
> > /dev/hdc: "Current Write Speed" is 4.1x1385KBps.
> >          0/4519313408 ( 0.0%) @0x, remaining ??:??
> >          0/4519313408 ( 0.0%) @0x, remaining ??:??
> >          0/4519313408 ( 0.0%) @0x, remaining ??:??
> > :-? the LUN appears to be stuck writing LBA=10h, retry in 0ms
> > :-[ WRITE@LBA=80000010h failed with SK=2h/ASC=04h/ACQ=08h]: Resource
> > temporarily unavailable
> > :-( write failed: Resource temporarily unavailable
>
>
> It should have managed the failure... I'm sorry about delay, it's 
> probably inappropriate to ask if kernel has logged anything by the time 
> failure occured... What growisofs version is it? What is 
> dvd+rw-mediainfo output for coaster?

No problem about the delay - it's holiday season :)

I have kernel logs back to Dec 15, and there's nothing
 in them. growisofs is latest for FC3, that is

 dvd+rw-tools-5.21.4.10.8-2.i386.rpm

Unfortunately I threw the coaster away already... but
 I'll be trying again in the next days (I'll be away
 for a couple of days to friends in Rome, then will
 give this another try) - so in the unfortunate event
 that I get another coaster I'll also update with the
 relevant dvd+rw-mediainfo...

> > It happened to me the other day with a DVD+RW, and sure enough
> >  a new attempt at burning the same media right after an identical
> >  failure worked just fine.
>
>
> Huh? Is it possible that there is some kind of auto-mounter is running?
>  In case you wonder how is worked before. If the only thing that changed 
> was unit and unit only. Compliant unit should be able to manage 
> auto-mounter when recording DVD+R or +RW media, but not all 
> units/firmware can actually do that.

FC3 adds in fstab entries for CD/DVD drives with a syntax
 I don't know but that quite clearly hints to automounting:

#/dev/hdd                /media/cdrecorder       auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0
#/dev/hdc                /media/cdrecorder1      auto    pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0

I commented those entries out however well before attempting
 DVD burning, and the ones I use currently are

/dev/cdrom          /cdrom           udf,iso9660 noauto,owner,noatime,ro 0 0
/dev/dvd            /dvd             udf,iso9660 noauto,owner,noatime,ro 0 0

Not sure whether this is enough to rule automounting out...

Last tidbit of info - when I replaced the LG DVD-RW unit
 I also removed the LG CD-RW unit I had, so now I only
 have the Samsung DVD-RW drive.

> > Question: is there any option I can specify to growisofs to make
> >  it try for a longer period of time before giving up ?
>
>
> Something else is crazy... I have to ponder over it... A.

Thanks - I'll be back in the game on the 7th. Ciao,

--alessandro

 "And every dream, every, is just a dream after all"

    (Heather Nova, "Paper Cup")