Unable to format dvd
BJ
back and got it solved here on this newsgroup. This is a new problem.
I am trying to run the format command from terminal like I always did in
the past but one of my machines will no longer format. It will on my
second machine just fine. Both machines have the same Ultimate Edition
2.5 with all the latest updates.
This is what I get on the machine that don't work anymore. In Terminal I
typed the dvd format command. This was the output.
bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
:-( unable to open("/dev/dvd"): No such file or directory
bjjl@bjjl-desktop:~$ su
Password:
root@bjjl-desktop:/home/bjjl# dvd+rw-format -force /dev/dvd
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
:-( unable to open("/dev/dvd"): No such file or directory
root@bjjl-desktop:/home/bjjl# dvd+rw-format -force=full /dev/dvd
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
:-( unable to open("/dev/dvd"): No such file or directory
root@bjjl-desktop:/home/bjjl# cdrecord -scanbus
scsibus4:
4,0,0 400) 'HL-DT-ST' 'DVDRRW GSA-4166B' '1.02' Removable CD-ROM
4,1,0 401) *
4,2,0 402) *
4,3,0 403) *
4,4,0 404) *
4,5,0 405) *
4,6,0 406) *
4,7,0 407) *
root@bjjl-desktop:/home/bjjl# dvd+rw-format -force /dev/dvd
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
:-( unable to open("/dev/dvd"): No such file or directory
root@bjjl-desktop:/home/bjjl#
Now if I take the dvd out of that machine and put it in the other
machine. I run the same format command "dvd+rw-format -force /dev/dvd"
It starts formatting the second I hit enter. Thanks for information you
might give me.
Lew Pitcher
> Well I'm back with another problem. I had a Google Chrome problem awhile
> back and got it solved here on this newsgroup. This is a new problem.
>
> I am trying to run the format command from terminal like I always did in
> the past but one of my machines will no longer format. It will on my
> second machine just fine. Both machines have the same Ultimate Edition
> 2.5 with all the latest updates.
> This is what I get on the machine that don't work anymore. In Terminal I
> typed the dvd format command. This was the output.
> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
> * BD/DVD±RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
> :-( unable to open("/dev/dvd"): No such file or directory
Just to be certain, check that, on /this/ machine, you *do* have a /dev/dvd
block-special device entry.
[snipped other errors that claim that /dev/dvd does not exist]
> root@bjjl-desktop:/home/bjjl# cdrecord -scanbus
> scsibus4:
> 4,0,0 400) 'HL-DT-ST' 'DVDRRW GSA-4166B' '1.02' Removable CD-ROM
OK, you have a DVDRW, but is there a /dev/dvd device?
> root@bjjl-desktop:/home/bjjl# dvd+rw-format -force /dev/dvd
> * BD/DVD±RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
> :-( unable to open("/dev/dvd"): No such file or directory
As before, the utility claims that it cant find /dev/dvd. Note that
it /doesnt/ claim that SCSI device 4,0,0 doesn't exist, but claims
that /dev/dvd doesn't exist. Perhaps your system externalizes the DVD
device by some other name.
> Now if I take the dvd out of that machine and put it in the other
> machine. I run the same format command "dvd+rw-format -force /dev/dvd"
> It starts formatting the second I hit enter. Thanks for information you
> might give me.
You need to determine the path name of your DVD burner (it probably
isn't /dev/dvd), and use that pathname in your dvd+rw-format command.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
unruh
> Well I'm back with another problem. I had a Google Chrome problem awhile
> back and got it solved here on this newsgroup. This is a new problem.
>
> I am trying to run the format command from terminal like I always did in
> the past but one of my machines will no longer format. It will on my
> second machine just fine. Both machines have the same Ultimate Edition
> 2.5 with all the latest updates.
> This is what I get on the machine that don't work anymore. In Terminal I
> typed the dvd format command. This was the output.
> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
>:-( unable to open("/dev/dvd"): No such file or directory
It keeps telling you that the file /dev/dvd does not exist. Does it?
ls -l /dev/dvd
If it does, what are the permission on it?
BUt usually it is a link to the actual hard drive device. eg
/dev/dvd->/dev/sdr0
or something.
...
>
> Now if I take the dvd out of that machine and put it in the other
> machine. I run the same format command "dvd+rw-format -force /dev/dvd"
> It starts formatting the second I hit enter. Thanks for information you
> might give me.
On that machine /dev/dvd does exist.
BJ
When I run ls -l /dev/dvd "
When I run ls -l /dev/dvd+rw "
When I run ls -l /dev/dvd1 says >sr0
So the path is /dev/dvd1 then?
BJ
bjjl@bjjl-desktop:~$ dmesg | grep DVD
[ 0.948348] ata5.00: ATAPI: HL-DT-STDVDRRW GSA-4166B, 1.02, max UDMA/66
[ 2.169465] scsi 4:0:0:0: CD-ROM HL-DT-ST DVDRRW GSA-4166B
1.02 PQ: 0 ANSI: 5
bjjl@bjjl-desktop:~$
Lew Pitcher
> Lew Pitcher wrote:
>> On April 28, 2010 18:02, in alt.os.linux.debian, bj...@charter.net wrote:
>>
>>> Well I'm back with another problem. I had a Google Chrome problem awhile
>>> back and got it solved here on this newsgroup. This is a new problem.
>>>
>>> I am trying to run the format command from terminal like I always did in
>>> the past but one of my machines will no longer format. It will on my
>>> second machine just fine. Both machines have the same Ultimate Edition
>>> 2.5 with all the latest updates.
>>> This is what I get on the machine that don't work anymore. In Terminal I
>>> typed the dvd format command. This was the output.
>>> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
>>> * BD/DVD±RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
>>> :-( unable to open("/dev/dvd"): No such file or directory
>>
>> Just to be certain, check that, on /this/ machine, you *do* have a
>> /dev/dvd block-special device entry.
[snip]
>> As before, the utility claims that it cant find /dev/dvd. Note that
>> it /doesnt/ claim that SCSI device 4,0,0 doesn't exist, but claims
>> that /dev/dvd doesn't exist. Perhaps your system externalizes the DVD
>> device by some other name.
>>
>>> Now if I take the dvd out of that machine and put it in the other
>>> machine. I run the same format command "dvd+rw-format -force /dev/dvd"
>>> It starts formatting the second I hit enter. Thanks for information you
>>> might give me.
>>
>> You need to determine the path name of your DVD burner (it probably
>> isn't /dev/dvd), and use that pathname in your dvd+rw-format command.
>>
> When I run ls -l /dev/cdrom says no such file or directory
> When I run ls -l /dev/dvd "
> When I run ls -l /dev/dvd+rw "
> When I run ls -l /dev/dvd1 says >sr0
> So the path is /dev/dvd1 then?
Yup.
Try your format command again, this time specifying /dev/dvd1 instead
of /dev/dvd
dvd+rw-format -force /dev/dvd1
BJ
bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd1:-( mounted media doesn't appear to be DVD±RW, DVD-RAM or Blu-ray
bjjl@bjjl-desktop:~$
The other linux box is doing the same thing now I get the same error
messages. I ran rkhunter on both machines this is the output of both
machines.
Performing filesystem checks
Checking /dev for suspicious file types [ Warning ]
Checking for hidden files and directories [ Warning ]
[Press <ENTER> to continue]
System checks summary
=====================
File properties checks...
Files checked: 133
Suspect files: 0
Rootkit checks...
Rootkits checked : 111
Possible rootkits: 0
Applications checks...
Applications checked: 3
Suspect applications: 3
The system checks took: 1 minute and 46 seconds
All results have been written to the logfile (/var/log/rkhunter.log)
One or more warnings have been found while checking the system.
Please check the log file (/var/log/rkhunter.log)
root@bjjl-desktop:/home/bjjl#
Thanks for your time.
unruh
Sorry, that is irrelevant ( grep -i dvd might have been slightly more
informative) but the question is where does it put the dvd. As you
mentioned it seems to use /dev/dvd1 instead of /dev/dvd, so try using
/dev/dvd1
BJ
bjjl@bjjl-desktop:~$ dmesg | grep -i dvd
[ 0.948348] ata5.00: ATAPI: HL-DT-STDVDRRW GSA-4166B, 1.02, max UDMA/66
[ 2.169465] scsi 4:0:0:0: CD-ROM HL-DT-ST DVDRRW GSA-4166B
1.02 PQ: 0 ANSI: 5
[ 2.174372] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw
xa/form2 cdda tray
bjjl@bjjl-desktop:~$ dvd+rw-format -force=full /dev/dvd1
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
:-( mounted media doesn't appear to be DVD�RW, DVD-RAM or Blu-ray
bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd1
* BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
unruh
So, that tells you that /dev/sr0 is the dvd drive.
and it is a dvd-ram cd/rw device. Since /dev/dvd1 is pointing to sr0
that is the one to use.
> bjjl@bjjl-desktop:~$ dvd+rw-format -force=full /dev/dvd1
> * BD/DVD?RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
>:-( mounted media doesn't appear to be DVD?RW, DVD-RAM or Blu-ray
Well, are you sure that the disk you stuck in there is a dvd-rw disk?
Or it could be a bug in dvd+rw-format. Doesn't cdrecord have a format
option for rw disks?
> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd1
> * BD/DVD?RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
>:-( mounted media doesn't appear to be DVD?RW, DVD-RAM or Blu-ray
BJ
Yes. If I try to put a dvd-rw or dvd+rw that has data already on it both
machines will not see it. I use different media also, Memorex, Verbatim,
Office Depot, etc. Same results. If I put a brand new never been written
to dvd-rw or +rw the little message says "you have just inserted a blank
dvd. Choose what application to launch" If I put one that already has
data that window won't come up. Usually I would put the filled discs in
the drive and use the "dvd+rw-format -force /dev/dvd" command and it
format the disc so it was clean the next time I used it.
The strange thing is these commands use to work fine but now they won't
on either machine. I was thinking there was a Linux update that might
have changed something on both machines. I guess I'll have to try a
fresh install and see if that will make a difference.
Darren Salt
[snip]
> This is what I get on the machine that don't work anymore. In Terminal I
> typed the dvd format command. This was the output.
> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
> * BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
> :-( unable to open("/dev/dvd"): No such file or directory
Elewhere, you say that /dev/dvd1 exists and points to /dev/sr0. This makes me
think "udev", and some change in how the kernel sees the DVD writer.
There's a file, /etc/udev/rules.d/70-persistent-cd.rules, which controls
which symlinks are created. As root, you can edit this (carefully!): comment
out any line which creates "dvd", then replace "dvd1" with "dvd"; once you've
saved the modified file, run
udevadm trigger --sysname-match sr0
Feel free to add --verbose --dry-run to that command if you want to test
without making any actual changes to /dev. (Which would be a good idea,
really; I've not tested this.)
BTW, you probably want to make a copy of the file before you edit it for
comparison/restoration purposes.
[snip]
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL.
It's later than you think.
BJ
> I demand that BJ may or may not have written...
>
> [snip]
>> This is what I get on the machine that don't work anymore. In Terminal I
>> typed the dvd format command. This was the output.
>> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
>> * BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
>> :-( unable to open("/dev/dvd"): No such file or directory
>
> Elewhere, you say that /dev/dvd1 exists and points to /dev/sr0. This makes me
> think "udev", and some change in how the kernel sees the DVD writer.
>
> There's a file, /etc/udev/rules.d/70-persistent-cd.rules, which controls
> which symlinks are created. As root, you can edit this (carefully!): comment
> out any line which creates "dvd", then replace "dvd1" with "dvd"; once you've
> saved the modified file, run
> udevadm trigger --sysname-match sr0
>
> Feel free to add --verbose --dry-run to that command if you want to test
> without making any actual changes to /dev. (Which would be a good idea,
> really; I've not tested this.)
>
> BTW, you probably want to make a copy of the file before you edit it for
> comparison/restoration purposes.
>
> [snip]
Ultimate edition 2.5 It took about 2 hours but now everything works
fine. I can format from the terminal just like before. Some sort of
glitch somewhere. Don't know where. But, like Windoze a fresh install
cures all.
Thanks for all the help guys.
Darren Salt
[snip]
> I solved the problem by installing a fresh Ultimate edition 2.5
s/solved/invoked the sledgehammer-to-nut approach to/ ;-)
[snip]
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE.
I am Neelix of Borg. Your assimilation will boost the Collective's morale.
BJ
> I demand that BJ may or may not have written...
>
> [snip]
>> I solved the problem by installing a fresh Ultimate edition 2.5
>
> s/solved/invoked the sledgehammer-to-nut approach to/ ;-)
>
> [snip]
solution to the problem because it will probably happen again. However,
I don't know if its worth the week I spent trying to solve it when it
takes only 2 hours to do a fresh install.
BJ.
Darren Salt
> Darren Salt wrote:
>> I demand that BJ may or may not have written...
>> [snip]
>>> I solved the problem by installing a fresh Ultimate edition 2.5
>> s/solved/invoked the sledgehammer-to-nut approach to/ ;-)
>> [snip]
> LOL........... that is about right. I would have liked to found a solution
> to the problem because it will probably happen again. However, I don't know
> if its worth the week I spent trying to solve it when it takes only 2 hours
> to do a fresh install.
Well, yes, but if it only takes a few minutes to fix, once you've learned
how... and you don't have to remember how you configured various things last
time. ;-)
(OTOH, familiarity with the installer can be useful in its own right.)
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | back!
| + Burn less waste. Use less packaging. Waste less. USE FEWER RESOURCES.
It /is/ as bad as you think and they /are/ out to get you.
Yo$$1960
> There's a file, /etc/udev/rules.d/70-persistent-cd.rules, which controls
> which symlinks are created. As root, you can edit this (carefully!):
It's better to create a new file with the rules you want in (say)
80-persistent-cd.rules. This file overrides the relevant settings in 70*,
so system/package updates can rewrite 70* without affecting your changes.
It's only important that the number part of the name is higher, but I tend
to use big(ish) gaps so I can add other priorities in between, if
necessary. It rarely is, though.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
It's got nothing to do with the need to impress
Titanic (My Over) Reaction - 999
BJ
> I demand that BJ may or may not have written...
>
> [snip]
>> This is what I get on the machine that don't work anymore. In Terminal I
>> typed the dvd format command. This was the output.
>> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
>> * BD/DVD�RW/-RAM format utility by <ap...@fy.chalmers.se>, version 7.1.
>> :-( unable to open("/dev/dvd"): No such file or directory
>
> Elewhere, you say that /dev/dvd1 exists and points to /dev/sr0. This makes me
> think "udev", and some change in how the kernel sees the DVD writer.
>
> There's a file, /etc/udev/rules.d/70-persistent-cd.rules, which controls
> which symlinks are created. As root, you can edit this (carefully!): comment
> out any line which creates "dvd", then replace "dvd1" with "dvd"; once you've
> saved the modified file, run
> udevadm trigger --sysname-match sr0
>
> Feel free to add --verbose --dry-run to that command if you want to test
> without making any actual changes to /dev. (Which would be a good idea,
> really; I've not tested this.)
>
> BTW, you probably want to make a copy of the file before you edit it for
> comparison/restoration purposes.
>
> [snip]
I can't help thinking it had something to do with K3b and or Brasero,
the only two programs I ever used. Half the time they would not blank a
dvd oe cdrw. That's when I began to use "# dvd+rw-format -force=full
/dev/dvd" in terminal and that worked great for some time. Then one day
it decided it could not find the device anymore.
From now on I'm going to use wodim in terminal. I found that,
# wodim -v -dao speed=4 dev=/dev/scd0 /home/bjjl/my-file.iso
works just fine. I guess I'll stick with that until it decided to crash.
BJ.
unruh
> Darren Salt wrote:
>> I demand that BJ may or may not have written...
>>
>> [snip]
>>> This is what I get on the machine that don't work anymore. In Terminal I
>>> typed the dvd format command. This was the output.
>>> bjjl@bjjl-desktop:~$ dvd+rw-format -force /dev/dvd
>>> :-( unable to open("/dev/dvd"): No such file or directory
>>
>> Elewhere, you say that /dev/dvd1 exists and points to /dev/sr0. This makes me
>> think "udev", and some change in how the kernel sees the DVD writer.
>>
>> There's a file, /etc/udev/rules.d/70-persistent-cd.rules, which controls
>> which symlinks are created. As root, you can edit this (carefully!): comment
>> out any line which creates "dvd", then replace "dvd1" with "dvd"; once you've
>> saved the modified file, run
>> udevadm trigger --sysname-match sr0
>>
>> Feel free to add --verbose --dry-run to that command if you want to test
>> without making any actual changes to /dev. (Which would be a good idea,
>> really; I've not tested this.)
>>
>> BTW, you probably want to make a copy of the file before you edit it for
>> comparison/restoration purposes.
>>
>> [snip]
>
> I can't help thinking it had something to do with K3b and or Brasero,
> the only two programs I ever used. Half the time they would not blank a
> dvd oe cdrw. That's when I began to use "# dvd+rw-format -force=full
> /dev/dvd" in terminal and that worked great for some time. Then one day
> it decided it could not find the device anymore.
>
> From now on I'm going to use wodim in terminal. I found that,
> # wodim -v -dao speed=4 dev=/dev/scd0 /home/bjjl/my-file.iso
> works just fine. I guess I'll stick with that until it decided to crash.
> BJ.
You might want to use cdrtools (the real cdrecord) instead-- supports
more devices etc. cdrecord.berlios.de
Darren Salt
[snip]
> From now on I'm going to use wodim in terminal. I found that,
> # wodim -v -dao speed=4 dev=/dev/scd0 /home/bjjl/my-file.iso
> works just fine.
That should work fine without requiring root privileges.
growisofs is also good for writing to DVDs. You don't have to create the disc
image first; just point it at a directory containing the files which you want
on the disc.
> I guess I'll stick with that until it decided to crash.
Decided?
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | back!
| + Lobby friends, family, business, government. WE'RE KILLING THE PLANET.
CChheecckk yyoouurr dduupplleexx sswwiittcchh..
BJ
> I demand that BJ may or may not have written...
>
> [snip]
>> From now on I'm going to use wodim in terminal. I found that,
>> # wodim -v -dao speed=4 dev=/dev/scd0 /home/bjjl/my-file.iso
>> works just fine.
>
> That should work fine without requiring root privileges.
>
> growisofs is also good for writing to DVDs. You don't have to create the disc
> image first; just point it at a directory containing the files which you want
> on the disc.
>
>> I guess I'll stick with that until it decided to crash.
>
> Decided?
>
to say.
Thanks for the tip. I'll check out the growisofs along with cdrecord and
cdrtools.