/usr/bin/mkisofs: Value too large for defined data type. File /home/pms/projects/paraguay/disc1.iso is too large - ignoringTotal translation table size: 0 Total rockridge attributes bytes: 169 Total directory bytes: 0 Path table size(bytes): 10 /dev/hdc: engaging DVD-R DAO upon user request... *:-[ PERFORM OPC failed with SK=5h/ASC=2Ch/ACQ=00h]: Input/output error*
5/2C/00 stands for "COMMAND SEQUENCE ERROR"... I've never seen PERFORM OPC fail with "COMMAND SEQUENCE ERROR"... And I can hardly imagine what command sequence rule it violates... At least I would normally expect some previous command, such as SET STREAMING, to fail with "insane input" error code, then to defer error to PERFORM OPC like above...
More relevant question is what to do. First of all it appears to me that you fall victim to wrong expectations. If disc1.iso as actual DVD image which you intended to burn, then you shouldn't have seen any messages from mkisofs. It looks as if you used 'growisofs -Z /dev/dvd disc1.iso' instead of 'growisofs -Z /dev/dvd=disc1.iso'. Note that in first case it creates essentially empty file system image [disc1.iso is too large - ignoring], very short one, which *might* as well cause the "command sequence error" if unit firmware implies some minimum size on reserved track.
Secondly "command sequence error" might indicate that unit found internal optimized profile for media in question [where is dvd+rw-mediainfo output???] and OPC request is therefore superfluous. Try to modify growisofs_mmc.cpp by commenting out "exit(FATAL_START(errno));" line, the one immediately following "sperror ("PERFORM OPC",err);" one. Another option is to skip OPC altogether. Given the growing amount of OPC related problems, it makes sense to implement skipping OPC as option... A.