SUSE / openSUSE This Forum is for the discussion of Suse Linux.
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
02-02-2017, 12:27 AM
#16
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,804
you can try to execute dmesg to check how this device was recognized (during boot)
02-02-2017, 03:27 AM
#17
Member
Registered: Aug 2008
Location: Yorkshire
Distribution: openSUSE(Leap and Tumbleweed) and a (not so) regularly changing third and fourth
Posts: 627
Rep:
Quote:
Originally Posted by
Crb999
k3b reports
"No optical drive found. K3b did not find any optical device in your system."
I had this problem a few years ago and needed to update the firmware on the optical device before it was recognised by linux. Of course this isn't easy without MS windows (usually).
If the device is picked by the system but not k3b then it may be a permission problem with k3b. Check 'Configure k3b' under 'Settings'.
02-02-2017, 05:21 AM
#18
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
Hi Pan64, dmesg has uncovered something I hope will be useful to you, and me eventually!
This is what it reports but I have truncated it severely, these same messages are repeated hundreds of times.
Code:
[586466.716160] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586466.716168] sr 1:0:0:0: [sr0] tag#0 CDB: Test Unit Ready 00 00 00 00 00 00
[586468.716372] sr 1:0:0:0: [sr0] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586468.716378] sr 1:0:0:0: [sr0] tag#6 CDB: Test Unit Ready 00 00 00 00 00 00
[586470.716577] sr 1:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586470.716583] sr 1:0:0:0: [sr0] tag#12 CDB: Test Unit Ready 00 00 00 00 00 00
[586472.716785] sr 1:0:0:0: [sr0] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586472.716793] sr 1:0:0:0: [sr0] tag#18 CDB: Test Unit Ready 00 00 00 00 00 00
[586474.717003] sr 1:0:0:0: [sr0] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586474.717011] sr 1:0:0:0: [sr0] tag#24 CDB: Test Unit Ready 00 00 00 00 00 00
[586476.717212] sr 1:0:0:0: [sr0] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586476.717218] sr 1:0:0:0: [sr0] tag#30 CDB: Test Unit Ready 00 00 00 00 00 00
[586478.717411] sr 1:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586478.717417] sr 1:0:0:0: [sr0] tag#5 CDB: Test Unit Ready 00 00 00 00 00 00
[586480.717620] sr 1:0:0:0: [sr0] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586480.717626] sr 1:0:0:0: [sr0] tag#11 CDB: Test Unit Ready 00 00 00 00 00 00
[586482.717831] sr 1:0:0:0: [sr0] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586482.717836] sr 1:0:0:0: [sr0] tag#17 CDB: Test Unit Ready 00 00 00 00 00 00
[586484.718042] sr 1:0:0:0: [sr0] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586484.718047] sr 1:0:0:0: [sr0] tag#23 CDB: Test Unit Ready 00 00 00 00 00 00
[586486.718244] sr 1:0:0:0: [sr0] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[586486.718252] sr 1:0:0:0: [sr0] tag#29 CDB: Test Unit Ready 00 00 00 00 00 00
02-02-2017, 05:49 AM
#19
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,804
would be nice to see from the first related message
02-02-2017, 08:08 AM
#20
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
OK but it's big!
I have various other outputs I have been exploring but will make a separate reply for those.
Code:
crb999@linux-dxa1:~> cat dmsgfile.txt | more
[592301.338997] sr 1:0:0:0: [sr0] tag#19 CDB: Test Unit Ready 00 00 00 00 00 00
[592303.339231] sr 1:0:0:0: [sr0] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592303.339237] sr 1:0:0:0: [sr0] tag#25 CDB: Test Unit Ready 00 00 00 00 00 00
[592305.339452] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592305.339458] sr 1:0:0:0: [sr0] tag#0 CDB: Test Unit Ready 00 00 00 00 00 00
[592307.339659] sr 1:0:0:0: [sr0] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592307.339665] sr 1:0:0:0: [sr0] tag#6 CDB: Test Unit Ready 00 00 00 00 00 00
[592309.339876] sr 1:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592309.339882] sr 1:0:0:0: [sr0] tag#12 CDB: Test Unit Ready 00 00 00 00 00 00
[592311.340083] sr 1:0:0:0: [sr0] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592311.340088] sr 1:0:0:0: [sr0] tag#18 CDB: Test Unit Ready 00 00 00 00 00 00
[592313.340308] sr 1:0:0:0: [sr0] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592313.340314] sr 1:0:0:0: [sr0] tag#24 CDB: Test Unit Ready 00 00 00 00 00 00
[592315.340519] sr 1:0:0:0: [sr0] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592315.340524] sr 1:0:0:0: [sr0] tag#30 CDB: Test Unit Ready 00 00 00 00 00 00
[592317.340725] sr 1:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592317.340731] sr 1:0:0:0: [sr0] tag#5 CDB: Test Unit Ready 00 00 00 00 00 00
[592319.340943] sr 1:0:0:0: [sr0] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592319.340949] sr 1:0:0:0: [sr0] tag#11 CDB: Test Unit Ready 00 00 00 00 00 00
[592321.341169] sr 1:0:0:0: [sr0] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592321.341174] sr 1:0:0:0: [sr0] tag#17 CDB: Test Unit Ready 00 00 00 00 00 00
[592323.341379] sr 1:0:0:0: [sr0] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592323.341384] sr 1:0:0:0: [sr0] tag#23 CDB: Test Unit Ready 00 00 00 00 00 00
[592325.341596] sr 1:0:0:0: [sr0] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592325.341601] sr 1:0:0:0: [sr0] tag#29 CDB: Test Unit Ready 00 00 00 00 00 00
[592327.341823] sr 1:0:0:0: [sr0] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592327.341829] sr 1:0:0:0: [sr0] tag#4 CDB: Test Unit Ready 00 00 00 00 00 00
[592329.342037] sr 1:0:0:0: [sr0] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592329.342043] sr 1:0:0:0: [sr0] tag#10 CDB: Test Unit Ready 00 00 00 00 00 00
[592331.342261] sr 1:0:0:0: [sr0] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592331.342267] sr 1:0:0:0: [sr0] tag#16 CDB: Test Unit Ready 00 00 00 00 00 00
[592333.342473] sr 1:0:0:0: [sr0] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592333.342479] sr 1:0:0:0: [sr0] tag#22 CDB: Test Unit Ready 00 00 00 00 00 00
[592335.342696] sr 1:0:0:0: [sr0] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592335.342701] sr 1:0:0:0: [sr0] tag#28 CDB: Test Unit Ready 00 00 00 00 00 00
[592337.342907] sr 1:0:0:0: [sr0] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592337.342913] sr 1:0:0:0: [sr0] tag#3 CDB: Test Unit Ready 00 00 00 00 00 00
[592339.343133] sr 1:0:0:0: [sr0] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592339.343138] sr 1:0:0:0: [sr0] tag#9 CDB: Test Unit Ready 00 00 00 00 00 00
[592341.343349] sr 1:0:0:0: [sr0] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592341.343355] sr 1:0:0:0: [sr0] tag#15 CDB: Test Unit Ready 00 00 00 00 00 00
[592343.343574] sr 1:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592343.343579] sr 1:0:0:0: [sr0] tag#21 CDB: Test Unit Ready 00 00 00 00 00 00
[592345.343780] sr 1:0:0:0: [sr0] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592345.343786] sr 1:0:0:0: [sr0] tag#27 CDB: Test Unit Ready 00 00 00 00 00 00
[592347.343970] sr 1:0:0:0: [sr0] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592347.343975] sr 1:0:0:0: [sr0] tag#2 CDB: Test Unit Ready 00 00 00 00 00 00
[592349.344685] sr 1:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592349.344691] sr 1:0:0:0: [sr0] tag#8 CDB: Test Unit Ready 00 00 00 00 00 00
[592351.344896] sr 1:0:0:0: [sr0] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592351.344903] sr 1:0:0:0: [sr0] tag#14 CDB: Test Unit Ready 00 00 00 00 00 00
[592353.345121] sr 1:0:0:0: [sr0] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592353.345126] sr 1:0:0:0: [sr0] tag#20 CDB: Test Unit Ready 00 00 00 00 00 00
[592355.345356] sr 1:0:0:0: [sr0] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592355.345363] sr 1:0:0:0: [sr0] tag#26 CDB: Test Unit Ready 00 00 00 00 00 00
[592357.345565] sr 1:0:0:0: [sr0] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[592357.345571] sr 1:0:0:0: [sr0] tag#1 CDB: Test Unit Ready 00 00 00 00 00 00
[592359.345871] sr 1:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
You can see I'm not an expert at this! I'll now add the last page.
Code:
[596385.787919] sr 1:0:0:0: [sr0] tag#14 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596385.787924] sr 1:0:0:0: [sr0] tag#14 CDB: Test Unit Ready 00 00 00 00 00 00
[596387.788144] sr 1:0:0:0: [sr0] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596387.788151] sr 1:0:0:0: [sr0] tag#20 CDB: Test Unit Ready 00 00 00 00 00 00
[596389.788347] sr 1:0:0:0: [sr0] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596389.788352] sr 1:0:0:0: [sr0] tag#26 CDB: Test Unit Ready 00 00 00 00 00 00
[596391.788559] sr 1:0:0:0: [sr0] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596391.788565] sr 1:0:0:0: [sr0] tag#1 CDB: Test Unit Ready 00 00 00 00 00 00
[596393.788787] sr 1:0:0:0: [sr0] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596393.788792] sr 1:0:0:0: [sr0] tag#7 CDB: Test Unit Ready 00 00 00 00 00 00
[596395.789011] sr 1:0:0:0: [sr0] tag#13 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596395.789017] sr 1:0:0:0: [sr0] tag#13 CDB: Test Unit Ready 00 00 00 00 00 00
[596397.789225] sr 1:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596397.789233] sr 1:0:0:0: [sr0] tag#19 CDB: Test Unit Ready 00 00 00 00 00 00
[596399.789437] sr 1:0:0:0: [sr0] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596399.789445] sr 1:0:0:0: [sr0] tag#25 CDB: Test Unit Ready 00 00 00 00 00 00
[596401.789666] sr 1:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596401.789675] sr 1:0:0:0: [sr0] tag#0 CDB: Test Unit Ready 00 00 00 00 00 00
[596403.789891] sr 1:0:0:0: [sr0] tag#6 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596403.789899] sr 1:0:0:0: [sr0] tag#6 CDB: Test Unit Ready 00 00 00 00 00 00
[596405.791935] sr 1:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596405.791939] sr 1:0:0:0: [sr0] tag#12 CDB: Test Unit Ready 00 00 00 00 00 00
[596407.792115] sr 1:0:0:0: [sr0] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596407.792120] sr 1:0:0:0: [sr0] tag#18 CDB: Test Unit Ready 00 00 00 00 00 00
[596409.792354] sr 1:0:0:0: [sr0] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596409.792360] sr 1:0:0:0: [sr0] tag#24 CDB: Test Unit Ready 00 00 00 00 00 00
[596411.792581] sr 1:0:0:0: [sr0] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596411.792587] sr 1:0:0:0: [sr0] tag#30 CDB: Test Unit Ready 00 00 00 00 00 00
[596413.792815] sr 1:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596413.792821] sr 1:0:0:0: [sr0] tag#5 CDB: Test Unit Ready 00 00 00 00 00 00
[596415.793046] sr 1:0:0:0: [sr0] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596415.793051] sr 1:0:0:0: [sr0] tag#11 CDB: Test Unit Ready 00 00 00 00 00 00
[596417.793269] sr 1:0:0:0: [sr0] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596417.793275] sr 1:0:0:0: [sr0] tag#17 CDB: Test Unit Ready 00 00 00 00 00 00
[596419.793503] sr 1:0:0:0: [sr0] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596419.793509] sr 1:0:0:0: [sr0] tag#23 CDB: Test Unit Ready 00 00 00 00 00 00
[596421.793731] sr 1:0:0:0: [sr0] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596421.793736] sr 1:0:0:0: [sr0] tag#29 CDB: Test Unit Ready 00 00 00 00 00 00
[596423.793978] sr 1:0:0:0: [sr0] tag#4 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596423.793982] sr 1:0:0:0: [sr0] tag#4 CDB: Test Unit Ready 00 00 00 00 00 00
[596425.794294] sr 1:0:0:0: [sr0] tag#10 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596425.794300] sr 1:0:0:0: [sr0] tag#10 CDB: Test Unit Ready 00 00 00 00 00 00
[596427.794553] sr 1:0:0:0: [sr0] tag#16 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596427.794559] sr 1:0:0:0: [sr0] tag#16 CDB: Test Unit Ready 00 00 00 00 00 00
[596429.794777] sr 1:0:0:0: [sr0] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596429.794783] sr 1:0:0:0: [sr0] tag#22 CDB: Test Unit Ready 00 00 00 00 00 00
[596431.794993] sr 1:0:0:0: [sr0] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596431.794999] sr 1:0:0:0: [sr0] tag#28 CDB: Test Unit Ready 00 00 00 00 00 00
[596433.795197] sr 1:0:0:0: [sr0] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596433.795202] sr 1:0:0:0: [sr0] tag#3 CDB: Test Unit Ready 00 00 00 00 00 00
[596435.795388] sr 1:0:0:0: [sr0] tag#9 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596435.795394] sr 1:0:0:0: [sr0] tag#9 CDB: Test Unit Ready 00 00 00 00 00 00
[596437.795601] sr 1:0:0:0: [sr0] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596437.795606] sr 1:0:0:0: [sr0] tag#15 CDB: Test Unit Ready 00 00 00 00 00 00
[596439.795817] sr 1:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596439.795822] sr 1:0:0:0: [sr0] tag#21 CDB: Test Unit Ready 00 00 00 00 00 00
[596441.796050] sr 1:0:0:0: [sr0] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596441.796055] sr 1:0:0:0: [sr0] tag#27 CDB: Test Unit Ready 00 00 00 00 00 00
[596443.796268] sr 1:0:0:0: [sr0] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596443.796272] sr 1:0:0:0: [sr0] tag#2 CDB: Test Unit Ready 00 00 00 00 00 00
[596445.796485] sr 1:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[596445.796491] sr 1:0:0:0: [sr0] tag#8 CDB: Test Unit Ready 00 00 00 00 00 00
crb999@linux-dxa1:~>
02-02-2017, 08:23 AM
#21
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
I have executed a few more salient commands and show the responses below:
Code:
linux-dxa1:/var/log # df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4021660 0 4021660 0% /dev
tmpfs 4035712 15112 4020600 1% /dev/shm
tmpfs 4035712 2332 4033380 1% /run
tmpfs 4035712 0 4035712 0% /sys/fs/cgroup
/dev/sda2 41946112 18969716 22302156 46% /
/dev/sda2 41946112 18969716 22302156 46% /usr/local
/dev/sda2 41946112 18969716 22302156 46% /var/log
/dev/sda2 41946112 18969716 22302156 46% /opt
/dev/sda2 41946112 18969716 22302156 46% /var/lib/mysql
/dev/sda2 41946112 18969716 22302156 46% /var/lib/mailman
/dev/sda2 41946112 18969716 22302156 46% /var/lib/named
/dev/sda2 41946112 18969716 22302156 46% /var/lib/libvirt/images
/dev/sda2 41946112 18969716 22302156 46% /var/lib/mariadb
/dev/sda2 41946112 18969716 22302156 46% /.snapshots
/dev/sda2 41946112 18969716 22302156 46% /srv
/dev/sda2 41946112 18969716 22302156 46% /tmp
/dev/sda2 41946112 18969716 22302156 46% /var/tmp
/dev/sda2 41946112 18969716 22302156 46% /var/spool
/dev/sda2 41946112 18969716 22302156 46% /var/lib/machines
/dev/sda2 41946112 18969716 22302156 46% /boot/grub2/i386-pc
/dev/sda2 41946112 18969716 22302156 46% /boot/grub2/x86_64-efi
/dev/sda2 41946112 18969716 22302156 46% /var/lib/pgsql
/dev/sda2 41946112 18969716 22302156 46% /var/crash
/dev/sda2 41946112 18969716 22302156 46% /var/opt
/dev/sda3 932256000 23080444 909175556 3% /home
tmpfs 807144 28 807116 1% /run/user/1000
Code:
linux-dxa1:/var/log # wodim -version
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd
Wodim 1.1.11
Copyright (C) 2006 Cdrkit suite contributors
Based on works from Joerg Schilling, Copyright (C) 1995-2006, J. Schilling
linux-dxa1:/var/log # wodim dev=sr0
wodim: No tracks specified. Need at least one.
linux-dxa1:/var/log # wodim -devices
wodim: Overview of accessible drives (0 found) :
Code:
crb999@linux-dxa1:/var/log> cat /etc/mtab
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=4021660k,nr_inodes=1005415,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
/dev/sda2 / btrfs rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=22,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
/dev/sda2 /usr/local btrfs rw,relatime,space_cache,subvolid=265,subvol=/@/usr/local 0 0
/dev/sda2 /var/log btrfs rw,relatime,space_cache,subvolid=273,subvol=/@/var/log 0 0
/dev/sda2 /opt btrfs rw,relatime,space_cache,subvolid=262,subvol=/@/opt 0 0
/dev/sda2 /var/lib/mysql btrfs rw,relatime,space_cache,subvolid=270,subvol=/@/var/lib/mysql 0 0
/dev/sda2 /var/lib/mailman btrfs rw,relatime,space_cache,subvolid=268,subvol=/@/var/lib/mailman 0 0
/dev/sda2 /var/lib/named btrfs rw,relatime,space_cache,subvolid=271,subvol=/@/var/lib/named 0 0
/dev/sda2 /var/lib/libvirt/images btrfs rw,relatime,space_cache,subvolid=267,subvol=/@/var/lib/libvirt/images 0 0
/dev/sda2 /var/lib/mariadb btrfs rw,relatime,space_cache,subvolid=269,subvol=/@/var/lib/mariadb 0 0
/dev/sda2 /.snapshots btrfs rw,relatime,space_cache,subvolid=258,subvol=/@/.snapshots 0 0
/dev/sda2 /srv btrfs rw,relatime,space_cache,subvolid=263,subvol=/@/srv 0 0
/dev/sda2 /tmp btrfs rw,relatime,space_cache,subvolid=264,subvol=/@/tmp 0 0
/dev/sda2 /var/tmp btrfs rw,relatime,space_cache,subvolid=276,subvol=/@/var/tmp 0 0
/dev/sda2 /var/spool btrfs rw,relatime,space_cache,subvolid=275,subvol=/@/var/spool 0 0
/dev/sda2 /var/lib/machines btrfs rw,relatime,space_cache,subvolid=575,subvol=/@/var/lib/machines 0 0
/dev/sda2 /boot/grub2/i386-pc btrfs rw,relatime,space_cache,subvolid=260,subvol=/@/boot/grub2/i386-pc 0 0
/dev/sda2 /boot/grub2/x86_64-efi btrfs rw,relatime,space_cache,subvolid=261,subvol=/@/boot/grub2/x86_64-efi 0 0
/dev/sda2 /var/lib/pgsql btrfs rw,relatime,space_cache,subvolid=272,subvol=/@/var/lib/pgsql 0 0
/dev/sda2 /var/crash btrfs rw,relatime,space_cache,subvolid=266,subvol=/@/var/crash 0 0
/dev/sda2 /var/opt btrfs rw,relatime,space_cache,subvolid=274,subvol=/@/var/opt 0 0
/dev/sda3 /home xfs rw,relatime,attr2,inode64,noquota 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=807144k,mode=700,uid=1000,gid=100 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0
tracefs /sys/kernel/debug/tracing tracefs rw,relatime 0 0
Code:
crb999@linux-dxa1:/var/log> cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: sr0
drive speed: 125
drive # of slots: 1
Can close tray: 1
Can open tray: 1
Can lock tray: 1
Can change speed: 1
Can select disk: 0
Can read multisession: 1
Can read MCN: 1
Reports media changed: 1
Can play audio: 1
Can write CD-R: 1
Can write CD-RW: 1
Can read DVD: 1
Can write DVD-R: 1
Can write DVD-RAM: 1
Can read MRW: 0
Can write MRW: 0
Can write RAM: 1
Code:
crb999@linux-dxa1:/var/log> eject /dev/sr0
eject: unable to eject
crb999@linux-dxa1:/var/log> cdrecord -prcap
Cdrecord-ProDVD-ProBD-Clone 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling
cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient 'network' privileges. You will not be able to do remote SCSI.
cdrecord: Permission denied. Cannot open '/dev/sg0'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
Code:
crb999@linux-dxa1:/var/log> sudo cdrecord -scanbus
crb999's password:
Cdrecord-ProDVD-ProBD-Clone 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling
Linux sg driver version: 3.5.36
Using libscg version 'schily-0.9'.
scsibus0:
0,0,0 0) 'ATA ' 'ST31000520AS ' 'CC38' Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
scsibus1:
1,0,0 100) *
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
crb999@linux-dxa1:/var/log>
02-02-2017, 09:26 AM
#22
Member
Registered: Aug 2008
Location: Yorkshire
Distribution: openSUSE(Leap and Tumbleweed) and a (not so) regularly changing third and fourth
Posts: 627
Rep:
Try adding yourself to 'cdrom' group. Go to 'Security and Users' in Yast2 and click edit on your entry.
I can't be sure but there is a mention of permissions in your code outputs.
02-02-2017, 10:50 AM
#23
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,804
I'm really sorry, but the dmesg log you sent is incomplete.
Code:
[ 2.106059] sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.106061] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.106201] sr 3:0:0:0: Attached scsi CD-ROM sr0
we are looking for something like this, but actually it is mine, your one will be definitely different.
probably
dmesg | less and
/sr0 inside the less window will help you to find that part
02-04-2017, 08:01 AM
#24
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
Hi Pan65
I have nothing like that in the file.
Code:
crb999@linux-dxa1:/var/log> dmesg | grep CD-ROM
crb999@linux-dxa1:/var/log> dmesg | grep scsi
crb999@linux-dxa1:/var/log> dmesg | grep Uniform
crb999@linux-dxa1:/var/log>
but if I grep sr0 I get everything!
Now, Yast2 has a 'Media Check' facility in the 'Software' tab.
it identifies the Optical device as "PLDS DVD+RW DH-16AAS (/dev/sr0)
When I tick the box to start the check, I get
Cannot read the medium in drive /dev/sr0
I can see that it is a scsi machine:
Code:
crb999@linux-dxa1:/var/log> lsscsi
[0:0:0:0] disk ATA ST31000520AS CC38 /dev/sda
[1:0:0:0] cd/dvd PLDS DVD+-RW DH-16AAS JD12 /dev/sr0
So when I try to mount it:
Code:
linux-dxa1:/dev # mount -t iso9660 /dev/dvd-rw /media/
mount: special device /dev/dvd-rw does not exist
and yet....
Code:
linux-dxa1:/ # cd dev
linux-dxa1:/dev # dir | grep dvd
lrwxrwxrwx 1 root root 3 Jan 26 17:33 dvd -> sr0
lrwxrwxrwx 1 root root 3 Jan 26 17:33 dvdrw -> sr0
I know that k3b can't find an optical drive so maybe I have to get one that ot does recognise..
Back to the linux hardware list!
02-04-2017, 08:05 AM
#25
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
I spotted a small error there. I was trying to mount /dev/dvd-rw whereas the device was identified as dvdrw so I tried again:
Code:
linux-dxa1:/dev # mount -t iso9660 /dev/dvdrw /media/
mount: no medium found on /dev/sr0
Needless to say Slowhand Clapton is still there waiting to be played.
02-04-2017, 11:29 AM
#26
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,804
ok, once more:
dmesg will print a lot, from the beginning (that means the boot). You can do:
Code:
dmesg | grep 'sr0' | head -20
dmesg | grep 'cdrom' | head -20
or something similar to get the first 20 lines containing sr0.
That will show us how the device was recognized by the system.
what you posted is related only to the "usage", a program tried to access that device which was not successful.
02-04-2017, 01:32 PM
#27
Moderator
Registered: Aug 2002
Posts: 25,681
Has this drive worked recently with other operating systems? Did you replace the drive yet?
You can not mount an audio or blank disc since they do not contain a filesystem. Since no program can detect that a disc is inserted in the drive then you probably have a mechanical problem. I found posts with your same error (FAILED Result: hostbyte=DID_BAD_TARGET...) where the OP was having hard disk problems but not with an optical drive.
02-04-2017, 02:15 PM
#28
Member
Registered: Oct 2014
Posts: 176
Rep:
Quote:
Originally Posted by
Crb999
I spotted a small error there. I was trying to mount /dev/dvd-rw whereas the device was identified as dvdrw so I tried again:
Code:
linux-dxa1:/dev # mount -t iso9660 /dev/dvdrw /media/
mount: no medium found on /dev/sr0
Needless to say Slowhand Clapton is still there waiting to be played.
I'm going to say this again...
PUT A DATA DISC IN THE DRIVE. Audio discs do not work the same way, and you CAN NOT mount them!!!
02-04-2017, 02:31 PM
#29
Member
Registered: Jan 2017
Location: West Coast Scotland
Distribution: Suse Linux 42.2 Now 15.1
Posts: 319
Original Poster
Rep:
Thanks guys and gals,
Pan 64 I'll do that next
Michaelk it was a win machine and yes it worked I installed Linux from it. Bye the bye, k3b can write dad's which implies that it can see, and I guess mount blank disks..
Ember1205 sorry. I now realise that a data disc and a disk with data are significantly different.
I don't have one. I'll write one on the win machine.
02-05-2017, 04:23 AM
#30
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 21,804
blank disks cannot be mounted, only disks containing real filesystems (of type iso9660, and probably others) can be mounted.
All times are GMT -5. The time now is 08:37 PM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News