FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 08-09-2012, 05:46 PM
Keith McKenzie
 
Default BD-RE mount problem

On 9 August 2012 18:28, Gary Dale <garydale@rogers.com> wrote:
> On 09/08/12 01:19 PM, Keith McKenzie wrote:
>>
>> On 9 August 2012 17:43, Gary Dale<garydale@rogers.com> wrote:
>>>
>>>
>>> Already tried that. dd complains:
>>> dd: opening `/dev/sr0': Read-only file system
>>>
>> It sounds like it is mounted; try unmounting it,& then try dd again.
>>
> root@transponder:/home/garydale# umount /dev/sr0
> umount: /dev/sr0: not mounted
> root@transponder:/home/garydale# dd of=/dev/sr0 bs=2048 count=1024
> dd: opening `/dev/sr0': Read-only file system
>
>
> Also,
>
> root@transponder:/home/garydale# mkfs -t ext2 /dev/sr0
> mke2fs 1.42.4 (12-Jun-2012)
> /dev/sr0 is entire device, not just one partition!
> Proceed anyway? (y,n) y
> /dev/sr0: Read-only file system while setting up superblock
>
.....& it isn't mounted under /dev/cdrom or /dev/dvd ?



--
Sent from FOSS (Free Open Source Software)
Debian GNU/Linux


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAL36VGnwbN_PRNfHaFBpXXFXj921ztxeoOrMK_3P5zdVhF=rT g@mail.gmail.com
 
Old 08-09-2012, 06:39 PM
"Thomas Schmitt"
 
Default BD-RE mount problem

Hi,

> I also tried using K3B to burn as udf.
> mkisofs print size result: 0 (0 bytes)

This looks like a different problem.
A size prediction of 0 is hardly to explain by any state of
the target medium. How large should the result have been ?


What do you get from

xorriso -outdev /dev/sr0 -blank as_needed
-md5 on -add /usr/local/bin --

(You may use any other existing directory. I have chosen /usr/local/bin
because it is normally not too large for a quick test.)

If this fails, then you can get very verbous message output
by prepending -report_about and -scsi_log commands and by
catching the messages in file /tmp/xorriso.log

xorriso -report_about all -scsi_log on
-outdev /dev/sr0 -blank as_needed
-md5 on -add /usr/local/bin --
2>&1 | tee -i /tmp/xorriso.log

That file xorriso.log would be of interest then, of course.


Have a nice day

Thomas


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 379612444358986481@scdbackup.webframe.org">http://lists.debian.org/379612444358986481@scdbackup.webframe.org
 
Old 08-09-2012, 06:53 PM
Gary Dale
 
Default BD-RE mount problem

On 09/08/12 01:46 PM, Keith McKenzie wrote:

On 9 August 2012 18:28, Gary Dale<garydale@rogers.com> wrote:

On 09/08/12 01:19 PM, Keith McKenzie wrote:

On 9 August 2012 17:43, Gary Dale<garydale@rogers.com> wrote:


Already tried that. dd complains:
dd: opening `/dev/sr0': Read-only file system


It sounds like it is mounted; try unmounting it,& then try dd again.


root@transponder:/home/garydale# umount /dev/sr0
umount: /dev/sr0: not mounted
root@transponder:/home/garydale# dd of=/dev/sr0 bs=2048 count=1024
dd: opening `/dev/sr0': Read-only file system


Also,

root@transponder:/home/garydale# mkfs -t ext2 /dev/sr0
mke2fs 1.42.4 (12-Jun-2012)
/dev/sr0 is entire device, not just one partition!
Proceed anyway? (y,n) y
/dev/sr0: Read-only file system while setting up superblock


.....& it isn't mounted under /dev/cdrom or /dev/dvd ?

No. The umount /dev/sr0 should handle that anyway, but I don't have the
other devices on my system. I think it's been pretty much /dev/sr? for
optical media for a couple of years now.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 50240719.20609@rogers.com">http://lists.debian.org/50240719.20609@rogers.com
 
Old 08-09-2012, 07:02 PM
Gary Dale
 
Default BD-RE mount problem

On 09/08/12 01:45 PM, Thomas Schmitt wrote:

Hi,


Yes, I have read-write permissions.

Something does not work properly.
Are any related messages to see in the output of dmesg ?
Nothing in dmesg | tail or syslog just now when I tried a dvd+rw-format
-force=full.






I tried xorriso to fix the disc as well but it also fails.

What did you try and what did it report when it failed ?
(We could get a log of SCSI commands from xorriso by
command -scsi_log on .)

xorriso just reports "failure". Here's the output with -scsi_log on:

root@transponder:/home/garydale# xorriso -scsi_log on -dev /dev/sr0
-format "full"

xorriso 1.2.2 : RockRidge filesystem manipulator, libburnia project.


TEST UNIT READY
00 00 00 00 00 00
4 ms

INQUIRY
12 00 00 00 24 00
From drive: 36b
05 80 05 32 5b 00 00 00 50 49 4f 4e 45 45 52 20 42 44 2d 52
57 20 20 20 42 44 52 2d 32 30 37 44 31 2e 31 30
8 ms

MODE SENSE
5a 00 2a 00 00 00 00 00 1e 00
From drive: 30b
00 2a 00 00 00 00 00 00 2a 22 3f 17 f1 63 2b 23 af 96 01 00
0f a0 af 96 00 00 23 1e 23 1e
8 ms

MODE SENSE
5a 00 2a 00 00 00 00 00 2c 00
From drive: 44b
00 2a 00 00 00 00 00 00 2a 22 3f 17 f1 63 2b 23 af 96 01 00
0f a0 af 96 00 00 23 1e 23 1e 00 01 00 00 00 00 23 1e 00 01
00 00 23 1e
4 ms

GET CONFIGURATION
46 00 00 00 00 00 00 00 08 00
From drive: 8b
00 00 01 ac 00 00 00 43
8 ms

GET CONFIGURATION
46 00 00 00 00 00 00 01 b0 00
From drive: 432b
00 00 01 ac 00 00 00 43 00 00 03 44 00 43 01 00 00 42 00 00
00 41 00 00 00 40 00 00 00 2b 00 00 00 1a 00 00 00 1b 00 00
00 16 00 00 00 15 00 00 00 13 00 00 00 14 00 00 00 11 00 00
00 02 01 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00
00 01 0b 08 00 00 00 07 01 00 00 00 00 02 07 04 02 00 00 00
00 03 07 04 39 00 00 00 00 04 09 04 02 00 00 00 00 10 01 08
00 00 08 00 00 20 01 00 00 1d 00 00 00 1e 08 04 03 00 00 00
00 1f 08 04 00 00 01 00 00 20 05 0c 00 b4 73 ff 00 00 08 00
00 20 01 00 00 21 0c 08 3f 01 07 01 00 00 00 00 00 23 09 08
08 00 00 00 00 00 00 00 00 24 05 04 80 00 00 00 00 26 00 00
00 2a 08 04 01 00 00 00 00 2b 00 04 01 00 00 00 00 2c 00 04
03 00 00 00 00 2d 08 04 46 00 3f 01 00 2e 04 04 6f 00 08 00
00 2f 08 04 4e 00 00 00 00 33 00 08 00 00 00 01 10 00 00 00
00 37 00 04 00 0f 00 00 00 38 00 04 00 00 00 00 00 3b 00 04
01 00 00 00 00 40 09 1c 01 00 00 00 00 06 00 00 00 00 00 00
00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 41 05 14
01 00 00 00 00 04 00 00 00 00 00 00 00 02 00 00 00 00 00 00
01 00 03 00 01 03 00 04 07 00 00 01 01 04 04 04 00 00 00 00
01 05 07 04 01 00 00 00 01 06 00 04 00 00 00 01 01 07 15 04
3f 00 00 00 01 08 03 0c 4b 4b 44 4c 30 30 30 30 32 30 57 4c
01 0a 00 0c 46 44 43 00 53 44 43 00 54 4f 43 00 01 0b 00 04
00 00 00 01 01 0d 09 04 13 01 01 01
8 ms

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 00 03 00
From drive: 8b
00 00 00 14 00 00 00 00
4 ms

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 b4 73 ff 00 00 23 1e
00 00 23 1e
4 ms

MODE SENSE
5a 00 01 00 00 00 00 00 0c 00
From drive: 12b
00 12 00 00 00 00 00 00 01 0a 00 03
4 ms

PREVENT/ALLOW MEDIA REMOVAL
1e 00 00 00 00 00
4 ms

START/STOP UNIT
1b 00 00 00 03 00
8 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms

PREVENT/ALLOW MEDIA REMOVAL
1e 00 00 00 01 00
4 ms

START/STOP UNIT
1b 01 00 00 01 00
4 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms

START/STOP UNIT
1b 00 00 00 01 00
8 ms

INQUIRY
12 00 00 00 24 00
From drive: 36b
05 80 05 32 5b 00 00 00 50 49 4f 4e 45 45 52 20 42 44 2d 52
57 20 20 20 42 44 52 2d 32 30 37 44 31 2e 31 30
4 ms

MODE SENSE
5a 00 2a 00 00 00 00 00 1e 00
From drive: 30b
00 2a 00 00 00 00 00 00 2a 22 3f 17 f1 63 2b 23 af 96 01 00
0f a0 af 96 00 00 23 1e 23 1e
8 ms

MODE SENSE
5a 00 2a 00 00 00 00 00 2c 00
From drive: 44b
00 2a 00 00 00 00 00 00 2a 22 3f 17 f1 63 2b 23 af 96 01 00
0f a0 af 96 00 00 23 1e 23 1e 00 01 00 00 00 00 23 1e 00 01
00 00 23 1e
8 ms

GET CONFIGURATION
46 00 00 00 00 00 00 00 08 00
From drive: 8b
00 00 01 ac 00 00 00 43
8 ms

GET CONFIGURATION
46 00 00 00 00 00 00 01 b0 00
From drive: 432b
00 00 01 ac 00 00 00 43 00 00 03 44 00 43 01 00 00 42 00 00
00 41 00 00 00 40 00 00 00 2b 00 00 00 1a 00 00 00 1b 00 00
00 16 00 00 00 15 00 00 00 13 00 00 00 14 00 00 00 11 00 00
00 02 01 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00
00 01 0b 08 00 00 00 07 01 00 00 00 00 02 07 04 02 00 00 00
00 03 07 04 39 00 00 00 00 04 09 04 02 00 00 00 00 10 01 08
00 00 08 00 00 20 01 00 00 1d 00 00 00 1e 08 04 03 00 00 00
00 1f 08 04 00 00 01 00 00 20 05 0c 00 b4 73 ff 00 00 08 00
00 20 01 00 00 21 0c 08 3f 01 07 01 00 00 00 00 00 23 09 08
08 00 00 00 00 00 00 00 00 24 05 04 80 00 00 00 00 26 00 00
00 2a 08 04 01 00 00 00 00 2b 00 04 01 00 00 00 00 2c 00 04
03 00 00 00 00 2d 08 04 46 00 3f 01 00 2e 04 04 6f 00 08 00
00 2f 08 04 4e 00 00 00 00 33 00 08 00 00 00 01 10 00 00 00
00 37 00 04 00 0f 00 00 00 38 00 04 00 00 00 00 00 3b 00 04
01 00 00 00 00 40 09 1c 01 00 00 00 00 06 00 00 00 00 00 00
00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 41 05 14
01 00 00 00 00 04 00 00 00 00 00 00 00 02 00 00 00 00 00 00
01 00 03 00 01 03 00 04 07 00 00 01 01 04 04 04 00 00 00 00
01 05 07 04 01 00 00 00 01 06 00 04 00 00 00 01 01 07 15 04
3f 00 00 00 01 08 03 0c 4b 4b 44 4c 30 30 30 30 32 30 57 4c
01 0a 00 0c 46 44 43 00 53 44 43 00 54 4f 43 00 01 0b 00 04
00 00 00 01 01 0d 09 04 13 01 01 01
8 ms

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 00 03 00
From drive: 8b
00 00 00 14 00 00 00 00
0 ms

GET PERFORMANCE
ac 00 00 00 00 00 00 00 00 01 03 00
From drive: 24b
00 00 00 14 00 00 00 00 00 00 00 00 00 b4 73 ff 00 00 23 1e
00 00 23 1e
8 ms

MODE SENSE
5a 00 01 00 00 00 00 00 0c 00
From drive: 12b
00 12 00 00 00 00 00 00 01 0a 00 03
4 ms

MODE SENSE
5a 00 05 00 00 00 00 00 0a 00
From drive: 10b
00 3a 00 00 00 00 00 00 05 32
4 ms

GET CONFIGURATION
46 00 00 00 00 00 00 00 08 00
From drive: 8b
00 00 01 ac 00 00 00 43
12 ms

GET CONFIGURATION
46 00 00 00 00 00 00 01 b0 00
From drive: 432b
00 00 01 ac 00 00 00 43 00 00 03 44 00 43 01 00 00 42 00 00
00 41 00 00 00 40 00 00 00 2b 00 00 00 1a 00 00 00 1b 00 00
00 16 00 00 00 15 00 00 00 13 00 00 00 14 00 00 00 11 00 00
00 02 01 00 00 10 00 00 00 0a 00 00 00 09 00 00 00 08 00 00
00 01 0b 08 00 00 00 07 01 00 00 00 00 02 07 04 02 00 00 00
00 03 07 04 39 00 00 00 00 04 09 04 02 00 00 00 00 10 01 08
00 00 08 00 00 20 01 00 00 1d 00 00 00 1e 08 04 03 00 00 00
00 1f 08 04 00 00 01 00 00 20 05 0c 00 b4 73 ff 00 00 08 00
00 20 01 00 00 21 0c 08 3f 01 07 01 00 00 00 00 00 23 09 08
08 00 00 00 00 00 00 00 00 24 05 04 80 00 00 00 00 26 00 00
00 2a 08 04 01 00 00 00 00 2b 00 04 01 00 00 00 00 2c 00 04
03 00 00 00 00 2d 08 04 46 00 3f 01 00 2e 04 04 6f 00 08 00
00 2f 08 04 4e 00 00 00 00 33 00 08 00 00 00 01 10 00 00 00
00 37 00 04 00 0f 00 00 00 38 00 04 00 00 00 00 00 3b 00 04
01 00 00 00 00 40 09 1c 01 00 00 00 00 06 00 00 00 00 00 00
00 02 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 41 05 14
01 00 00 00 00 04 00 00 00 00 00 00 00 02 00 00 00 00 00 00
01 00 03 00 01 03 00 04 07 00 00 01 01 04 04 04 00 00 00 00
01 05 07 04 01 00 00 00 01 06 00 04 00 00 00 01 01 07 15 04
3f 00 00 00 01 08 03 0c 4b 4b 44 4c 30 30 30 30 32 30 57 4c
01 0a 00 0c 46 44 43 00 53 44 43 00 54 4f 43 00 01 0b 00 04
00 00 00 01 01 0d 09 04 13 01 01 01
8 ms

READ DISC INFORMATION
51 00 00 00 00 00 00 00 22 00
From drive: 34b
00 20 1e 01 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
4 ms

READ CAPACITY
25 00 00 00 00 00 00 00 00 00
From drive: 8b
00 b4 73 ff 00 00 08 00
4 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 04 00
From drive: 4b
00 00 00 30
8 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 34 00
From drive: 52b
00 00 00 30 00 b4 74 00 02 00 30 00 00 b4 74 00 00 00 30 00
00 b4 74 00 c0 00 30 00 00 b0 74 00 c0 00 50 00 00 b8 74 00
c0 00 10 00 00 ba 74 00 c4 00 08 00
4 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 04 00
From drive: 4b
00 00 00 30
4 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 34 00
From drive: 52b
00 00 00 30 00 b4 74 00 02 00 30 00 00 b4 74 00 00 00 30 00
00 b4 74 00 c0 00 30 00 00 b0 74 00 c0 00 50 00 00 b8 74 00
c0 00 10 00 00 ba 74 00 c4 00 08 00
4 ms

READ(10)
28 00 00 00 00 00 00 00 20 00
220 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 04 00
From drive: 4b
00 00 00 30
4 ms

READ FORMAT CAPACITIES
23 00 00 00 00 00 00 00 34 00
From drive: 52b
00 00 00 30 00 b4 74 00 02 00 30 00 00 b4 74 00 00 00 30 00
00 b4 74 00 c0 00 30 00 00 b0 74 00 c0 00 50 00 00 b8 74 00
c0 00 10 00 00 ba 74 00 c4 00 08 00
4 ms
Drive current: -dev '/dev/sr0'
Media current: BD-RE
Media status : is blank

READ TRACK INFORMATION
52 01 00 00 00 01 00 00 14 00
From drive: 20b
00 26 01 01 00 04 01 00 00 00 00 00 00 00 00 00 00 00 00 00
4 ms
Media summary: 0 sessions, 0 data blocks, 0 data, 22.6g free

START/STOP UNIT
1b 01 00 00 00 00
4 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms
Beginning to format medium.

START/STOP UNIT
1b 01 00 00 01 00
xorriso : UPDATE : Formatting ( 1.0% done in 1 seconds )
1308 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms

START/STOP UNIT
1b 00 00 00 01 00
xorriso : UPDATE : Formatting ( 1.0% done in 2 seconds )
xorriso : UPDATE : Formatting ( 1.0% done in 3 seconds )
1204 ms

FORMAT UNIT
04 11 00 00 00 00
To drive: 12b
00 82 00 08 00 b4 74 00 c2 00 30 00
+++ sense data = 70 00 05 00 00 00 00 0E 00 00 00 00 26 00 00 89 00 08
+++ key=5 asc=26h ascq=00h ( 4 ms)

TEST UNIT READY
00 00 00 00 00 00
8 ms

TEST UNIT READY
00 00 00 00 00 00
8 ms

SYNCHRONIZE CACHE
35 02 00 00 00 00 00 00 00 00
4 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms
xorriso : FAILURE : libburn indicates failure with formatting.
xorriso : NOTE : Gave up -outdev '/dev/sr0'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'

PREVENT/ALLOW MEDIA REMOVAL
1e 00 00 00 00 00
0 ms

START/STOP UNIT
1b 01 00 00 00 00
4 ms

TEST UNIT READY
00 00 00 00 00 00
0 ms






root@transponder:/home/garydale# dvd+rw-format -force=full /dev/sr0
* formatting .:-[ FORMAT UNIT failed with SK=5h/INVALID FIELD IN
PARAMETER LIST]: Input/output error

I've seen mention of this in some of my google searches on the various
messages I've been getting. Can you elaborate on how to change the format
type from the command line?

If you use -force without "=full" then you get sub-type 3.
> From dvd+rw-format.cpp:
if (full&& (formats[i+4+4]>>2)!=0x31)
formats[i+4+4] |= 2;// "Full Certificaton"
else if ((formats[i+4+4]>>2)==0x30)
formats[i+4+4] |= 3;// "Quick Certification"

But i do not see the formatting state of the medium as the cause
of your problems.



dd: opening `/dev/sr0': Read-only file system

Something is wrong deep in the kernel or in the hardware.
A BD-RE should be writable at least for the superuser.

But how does this match your report that it fails on another
system too ?
Very riddling.
The failure to format is just on this system, which is the only one I
have locally with a BluRay writer. The other system was just a failure
to mount after formatting. It's at a remote location. I'm waiting for
them to get new discs to try again (I brought the new discs I was trying
back with me to try on my computer). Meanwhile, I seem to be able to
mount their old discs which have already been formatted.




Can you read raw data from the medium ?
dd if=/dev/sr0 bs=2048 count=16 | wc


root@transponder:/home/garydale# dd if=/dev/sr0 bs=2048 count=16 | wc
16+0 records in
16+0 records out
32768 bytes (33 kB) copied, 0.00240657 s, 13.6 MB/s
0 0 32768


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 50240961.2080803@rogers.com">http://lists.debian.org/50240961.2080803@rogers.com
 
Old 08-09-2012, 07:11 PM
Gary Dale
 
Default BD-RE mount problem

On 09/08/12 02:39 PM, Thomas Schmitt wrote:

Hi,


I also tried using K3B to burn as udf.
mkisofs print size result: 0 (0 bytes)

This looks like a different problem.
A size prediction of 0 is hardly to explain by any state of
the target medium. How large should the result have been ?
59M or there about. The problem only shows up when I tell K3B to use
udf, so I believe it is related. K3B and xorriso will burn iso9660.





What do you get from

xorriso -outdev /dev/sr0 -blank as_needed
-md5 on -add /usr/local/bin --

(You may use any other existing directory. I have chosen /usr/local/bin
because it is normally not too large for a quick test.)

root@transponder:/home/garydale# xorriso -outdev /dev/sr0 -blank as_needed
> -md5 on -add /usr/local/bin
xorriso 1.2.2 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr0'
Media current: BD-RE
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 22.6g free
xorriso : NOTE : -blank as_needed: no need for action detected
Added to ISO image: directory '/usr/local/bin'='/usr/local/bin'
xorriso : UPDATE : Writing: 16s 8.3% fifo 0% buf 0%
libburn : NOTE : Write start address is 32 * 2048
xorriso : UPDATE : Writing: 16s 8.3% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 80s 41.7% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.1xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB
xorriso : UPDATE : Writing: 192s 100.0% fifo 0% buf 0%
0.0xB

ISO image produced: 30 sectors
Written to medium : 192 sectors at LBA 32
Writing to '/dev/sr0' completed successfully.


The problem doesn't seem to be affecting iso9660 burns. However, I don't
want iso9660 because it is read only. I need udf because it is a
writable file system.




If this fails, then you can get very verbous message output
by prepending -report_about and -scsi_log commands and by
catching the messages in file /tmp/xorriso.log

xorriso -report_about all -scsi_log on
-outdev /dev/sr0 -blank as_needed
-md5 on -add /usr/local/bin --
2>&1 | tee -i /tmp/xorriso.log

That file xorriso.log would be of interest then, of course.


Have a nice day

Thomas





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 50240B5C.7030605@rogers.com">http://lists.debian.org/50240B5C.7030605@rogers.com
 
Old 08-09-2012, 08:36 PM
"Thomas Schmitt"
 
Default BD-RE mount problem

Hi,

> # xorriso -scsi_log on -dev /dev/sr0 -format "full"
> ...
> xorriso : FAILURE : libburn indicates failure with formatting.

It should have reported the SCSI error (will have to dig for that).

That error came with command FORMAT UNIT

> FORMAT UNIT
> 04 11 00 00 00 00
> To drive: 12b
> 00 82 00 08 00 b4 74 00 c2 00 30 00
> +++ sense data = 70 00 05 00 00 00 00 0E 00 00 00 00 26 00 00 89 00 08
> +++ key=5 asc=26h ascq=00h ( 4 ms)

This would be
5 26 00 INVALID FIELD IN PARAMETER LIST

The drive does not want to format that medium.
At least not with Format Type 0x30, Sub-type 2.
Well, that's what dvd+rw-format tried too.

The refusal to re-format does not necessarily have to be related
to the failure to run mkudffs.


> The failure to format is just on this system, which is the only one I have
> locally with a BluRay writer. The other system was just a failure to mount
> after formatting.

Formatting a BD-RE may or may not erase its data (i.e. the filesystem).
I would consider it normal that a BD-RE cannot be mounted after a
re-format with no successful mkudffs.

So the theory that something in your computer broke down
is not outruled yet.
Did you tamper with udev ? Install new peripherals ?

Why do all block device writers so obstinately scream "read-only" ?


> xorriso -outdev /dev/sr0 -blank as_needed
> -md5 on -add /usr/local/bin
> ...
> Writing to '/dev/sr0' completed successfully.

Ok. It is not the drive to blame. It allowed several SCSI write
commands.

xorriso uses the generic SG_IO driver, which directly performs
SCSI transactions with the drive.

dd, mkudffs, et.al. use the block device driver, which itself would
use the SG_IO driver ... if it was not broken on your machine.


Expert question:

What can make the kernel throw EROFS, probably on write(2) ?
Device file permissions seem not to be the reason.


Gary:

Can you compile and run this C program ?

---------------------------------------------------------------------------
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdio.h>
#include <errno.h>
#include <string.h>

main()
{
int fd, ret;
char buf[2048];

fd = open("/dev/sr0", O_RDWR);
printf("open: fd= %d , errno= %d
", fd, errno);
if(errno)
perror("open");
memset(buf, 0, 2048);
ret = write(fd, buf, 2048);
printf("write: ret= %d , errno= %d
", ret, errno);
if(errno)
perror("write");
close(fd);
}
---------------------------------------------------------------------------

E.g. with code in file open_sr0.c :
cc -g -o open_sr0 open_sr0.c
and then
./open_sr0

With an empty drive i get
open: fd= -1 , errno= 123
open: No medium found
write: ret= -1 , errno= 9
write: Bad file descriptor

I assume that you, with a BD-RE loaded, get errno= 30,
"Read-only file system" at write.


Have a nice day

Thomas


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 14384612447337991541@scdbackup.webframe.org">http://lists.debian.org/14384612447337991541@scdbackup.webframe.org
 
Old 08-09-2012, 09:38 PM
Gary Dale
 
Default BD-RE mount problem

On 09/08/12 04:36 PM, Thomas Schmitt wrote:

Hi,


# xorriso -scsi_log on -dev /dev/sr0 -format "full"
...
xorriso : FAILURE : libburn indicates failure with formatting.

It should have reported the SCSI error (will have to dig for that).

That error came with command FORMAT UNIT


FORMAT UNIT
04 11 00 00 00 00
To drive: 12b
00 82 00 08 00 b4 74 00 c2 00 30 00
+++ sense data = 70 00 05 00 00 00 00 0E 00 00 00 00 26 00 00 89 00 08
+++ key=5 asc=26h ascq=00h ( 4 ms)

This would be
5 26 00 INVALID FIELD IN PARAMETER LIST

The drive does not want to format that medium.
At least not with Format Type 0x30, Sub-type 2.
Well, that's what dvd+rw-format tried too.

The refusal to re-format does not necessarily have to be related
to the failure to run mkudffs.



The failure to format is just on this system, which is the only one I have
locally with a BluRay writer. The other system was just a failure to mount
after formatting.

Formatting a BD-RE may or may not erase its data (i.e. the filesystem).
I would consider it normal that a BD-RE cannot be mounted after a
re-format with no successful mkudffs.

So the theory that something in your computer broke down
is not outruled yet.
Did you tamper with udev ? Install new peripherals ?
No. The last peripheral I installed was the BluRay writer, to replace a
DVD writer.




Why do all block device writers so obstinately scream "read-only" ?



xorriso -outdev /dev/sr0 -blank as_needed
-md5 on -add /usr/local/bin
...
Writing to '/dev/sr0' completed successfully.

Ok. It is not the drive to blame. It allowed several SCSI write
commands.

xorriso uses the generic SG_IO driver, which directly performs
SCSI transactions with the drive.

dd, mkudffs, et.al. use the block device driver, which itself would
use the SG_IO driver ... if it was not broken on your machine.


Expert question:

What can make the kernel throw EROFS, probably on write(2) ?
Device file permissions seem not to be the reason.


Gary:

Can you compile and run this C program ?

---------------------------------------------------------------------------
#include<sys/types.h>
#include<sys/stat.h>
#include<fcntl.h>
#include<stdio.h>
#include<errno.h>
#include<string.h>

main()
{
int fd, ret;
char buf[2048];

fd = open("/dev/sr0", O_RDWR);
printf("open: fd= %d , errno= %d
", fd, errno);
if(errno)
perror("open");
memset(buf, 0, 2048);
ret = write(fd, buf, 2048);
printf("write: ret= %d , errno= %d
", ret, errno);
if(errno)
perror("write");
close(fd);
}
---------------------------------------------------------------------------

E.g. with code in file open_sr0.c :
cc -g -o open_sr0 open_sr0.c
and then
./open_sr0

With an empty drive i get
open: fd= -1 , errno= 123
open: No medium found
write: ret= -1 , errno= 9
write: Bad file descriptor

I assume that you, with a BD-RE loaded, get errno= 30,
"Read-only file system" at write.


garydale@transponder:~$ ./open_sr0
open: fd= -1 , errno= 30
open: Read-only file system
write: ret= -1 , errno= 9
write: Bad file descriptor
garydale@transponder:~$ su
Password:
root@transponder:/home/garydale# ./open_sr0
open: fd= -1 , errno= 30
open: Read-only file system
write: ret= -1 , errno= 9
write: Bad file descriptor


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 50242DD2.6030307@rogers.com">http://lists.debian.org/50242DD2.6030307@rogers.com
 
Old 08-10-2012, 05:50 AM
"Thomas Schmitt"
 
Default BD-RE mount problem

Hi,

> > fd = open("/dev/sr0", O_RDWR);

> root@transponder:/home/garydale# ./open_sr0
> open: fd= -1 , errno= 30
> open: Read-only file system

This is surprising, because xorriso uses
open(..., O_RDWR | O_NDELAY);
when it acquires a drive.
(I would have expected to see the error with write(), which xorriso
does not use.)

Whay happens if you change the test program
- fd = open("/dev/sr0", O_RDWR);
+ fd = open("/dev/sr0", O_RDWR | O_NDELAY);
compile it, and run again as superuser ?


Whatever, a BD-RE device with rw-permission on its device file should
not throw this error.
We need kernel expertise to find out what happens here.

Is anybody at debian-user able to give advise or propose experiments
which shed light on the problem ?


Have a nice day

Thomas


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 23290612469270799061@scdbackup.webframe.org">http://lists.debian.org/23290612469270799061@scdbackup.webframe.org
 
Old 08-10-2012, 08:56 AM
Gary Dale
 
Default BD-RE mount problem

On 10/08/12 01:50 AM, Thomas Schmitt wrote:

Hi,


fd = open("/dev/sr0", O_RDWR);

root@transponder:/home/garydale# ./open_sr0
open: fd= -1 , errno= 30
open: Read-only file system

This is surprising, because xorriso uses
open(..., O_RDWR | O_NDELAY);
when it acquires a drive.
(I would have expected to see the error with write(), which xorriso
does not use.)

Whay happens if you change the test program
- fd = open("/dev/sr0", O_RDWR);
+ fd = open("/dev/sr0", O_RDWR | O_NDELAY);
compile it, and run again as superuser ?


Whatever, a BD-RE device with rw-permission on its device file should
not throw this error.
We need kernel expertise to find out what happens here.

Is anybody at debian-user able to give advise or propose experiments
which shed light on the problem ?


root@transponder:/home/garydale# ./open_sr0
open: fd= 3 , errno= 0
write: ret= 2048 , errno= 0


No one in Debian user has been able to shed any light on the problem.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 5024CCBF.3010507@rogers.com">http://lists.debian.org/5024CCBF.3010507@rogers.com
 
Old 08-10-2012, 09:23 AM
"Thomas Schmitt"
 
Default BD-RE mount problem

Hi,

> > - fd = open("/dev/sr0", O_RDWR);
> > + fd = open("/dev/sr0", O_RDWR | O_NDELAY);

> open: fd= 3 , errno= 0
> write: ret= 2048 , errno= 0

This explains why xorriso or dvd+rw-format can open the drive
device file. (The failure to re-format is a different problem.)


> No one in Debian user has been able to shed any light on the problem.

I am not a kernel hacker, but rather a self-proclaimed expert for
optical drives and ISO 9660.

My best guess is that the kernel believes the medium is read-only
(like BD-ROM) and thus refuses any attempt to use it for writing
via the normal POSIX system interface.

But i do not know how to inquire the kernel's view on the medium.
The drive sees a BD-RE and has no scruples to write data to it.
But the kernel seems to see a problem with writing.


Have a nice day

Thomas


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 24165612497463144592@scdbackup.webframe.org">http://lists.debian.org/24165612497463144592@scdbackup.webframe.org
 

Thread Tools




All times are GMT. The time now is 01:26 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org