Fedora Account System
Red Hat Associate
Red Hat Customer
+++ This bug was initially created as a clone of Bug #1525070 +++ +++ This bug was initially created as a clone of Bug #1524207 +++ Description of problem: Any access to the CD/DVD drive usually ends up in a system freeze that requires a power reset to get started again. Version-Release number of selected component (if applicable): Fedora 29 Fedora 4.18.17-300.fc29.x86_64 How reproducible: Any access to a CD/DVD drive Steps to Reproduce: 1. Insert CD or DVD into drive 2. Access CD or DVD 3. Eject CD or DVD Actual results: System freezes Expected results: CD or DVD is ejected and system is sill useable Steps to Reproduce: 1. Insert CD or DVD into drive 2. Start CD or DVD burning software 3. Eject CD or DVD Actual results: System freezes when blank CD or DVD is inserted Burning software starts then System freeze Expected results: CD or DVD created and system is sill useable Additional info: Fedora 29Fedora 4.18.17-300.fc29.x86_64 GNOME 3.30.2 desktop burn cds or dvds results in system lockup that requires hard power reset tried BRASERO, K3B and dd (to burn iso image) attempts read or write CDs hangs on screen and shutdown waits on task to complete requiring hard power reset attempts read or write DVDs are mostly successful but sometimes hangs on screen and shutdown waits on task to complete requiring hard power reset attempt to turn on computer with CD in drive results in system lockup (before login screen appears) that requires hard power reset attempt to turn on computer with DVD in drive does not affect anything CDROM eject with drawer close results in system lockup that requires hard power reset CDROM eject with drawer open followed by log out/shutdown results in system lockup that requires hard power reset attempts read CDs and DVDs are successful but DVD eject message hangs on screen and shutdown waits on task to complete requiring hard power reset
(In reply to Sabertooth from comment #0) ... > Actual results: > System freezes ... Can you toggle the caps-lock light on the keyboard? Can you get to a console (ctrl-alt-f2)?
I have no caps-lock or num-lock light in my keyboard, so i can't say. I can't get to a console. Pressing power button on the case does not activate sleep mode.
(In reply to Sabertooth from comment #2) > I have no caps-lock or num-lock light in my keyboard, so i can't say. > I can't get to a console. > Pressing power button on the case does not activate sleep mode. OK. Developers will need a log file, so here are some more things to try: Can you ping the system from another computer on the same network? Can you ssh to it? If none of that is possible: Run "journalctl -f" in a full-screen window and take a photograph of the screen after the system hangs. Attach that photograph.
(In reply to Steve from comment #3) I can't ping the system. Photo of journalctl is on Your mail.
(In reply to Sabertooth from comment #4) > (In reply to Steve from comment #3) > > I can't ping the system. OK. > Photo of journalctl is on Your mail. Please attach the photo to this bug report. Use the "Add an attachment" link at the top of the page.
Created attachment 1504759 [details] Bug 1648675, journalctl -f (In reply to Steve from comment #5) Photo of "journalctl -f"
(In reply to Sabertooth from comment #6) > Created attachment 1504759 [details] > Bug 1648675, journalctl -f > > (In reply to Steve from comment #5) > Photo of "journalctl -f" Thanks. It looks like "brasero" started, but that is all. I'm trying to reproduce this, but the F29 Workstation Live ISO image doesn't have "brasero", so I am going to have to do a test install. What kind of optical disk did you insert? (blank DVD? burned DVD? commercial DVD? etc.) Have you made any changes to the automount settings? And for completeness, could you attach dmesg from before the system hangs? $ dmesg > dmesg-1.txt Attach dmesg-1.txt.
(In reply to Steve from comment #7) ... > I'm trying to reproduce this, ... ... Could you confirm that your system is fully updated? # dnf update -y
Created attachment 1504816 [details] Bug 1648675, dmesg (In reply to Steve from comment #7) System was installed yesterday from net-instal iso. Brasero was installed by choice. In drive is CD-RW No changes in automount settings System is up to date Some details from today: 1. insert cd-rw - ok 2. copy existing data from cd to hdd - ok 3. start brasero (and not touching anything in it) -> cd-rw start spin (maybe brasero recognise available CD's) -> system freezes in less than a minute
Created attachment 1504846 [details] Bug 1648675, journalctl errors after cdrw insertion I did some other testing: 1. I burned a DVD-RW with brasero and it was successful - with data veryfication (yesterday it fails, but there were some updates for Fedora today, so maybe it helps or it was blind luck - hard to say) 2. insert cdrw - OS is ok (no freeze) but there are some errors in journalctl (it's not wisible on screen after brasero starts because lines scroll up) start brasero - system freezes in less than a minute 3. Start computer with cdrw in drive - system freezes on login screen before any typing or touching keyboard or mouse -> so it's not particularly brasero's fault (tested few times) 4. Start computer with cdrw in it, but booting other OS - everything is normal. (the same computer, the same cdrw). OS boots up. Burning cdrw is ok. -> so it's not a hardware
Thanks for your followup replies and attachments. I now have F29 Workstation installed (via netinst) and fully updated. Brasero is installed. My initial test was to simply insert a new CDRW and start Brasero. Everything behaved as expected. The dmesg output you attached has some "sr0" errors at the end, so you appear to be getting errors even without the system hanging. [ 6096.487465] sr 7:0:0:0: [sr0] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6096.487468] sr 7:0:0:0: [sr0] tag#5 Sense Key : Medium Error [current] [ 6096.487470] sr 7:0:0:0: [sr0] tag#5 Add. Sense: L-EC uncorrectable error [ 6096.487473] sr 7:0:0:0: [sr0] tag#5 CDB: Read(10) 28 00 00 05 03 04 00 00 02 00 [ 6096.487474] print_req_error: I/O error, dev sr0, sector 1313808 [ 6103.042342] sr 7:0:0:0: [sr0] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 6103.042344] sr 7:0:0:0: [sr0] tag#9 Sense Key : Medium Error [current] [ 6103.042347] sr 7:0:0:0: [sr0] tag#9 Add. Sense: L-EC uncorrectable error [ 6103.042349] sr 7:0:0:0: [sr0] tag#9 CDB: Read(10) 28 00 00 05 03 05 00 00 01 00 [ 6103.042351] print_req_error: I/O error, dev sr0, sector 1313812 [ 6103.042353] Buffer I/O error on dev sr0, logical block 328453, async page read
Indeed there are errors. I have insert that CDRW that seems to be damaged. Fedora works fine until start brasero or reboot. Next I found DVDRW which not generate errors. Fedora works perfectly fine (burn and reboot). Apparently something is going on when damage disc is inserted. Obviously CDRW is going to trash but how to prevent system in the future? It's impossible to see every scratch or surface damage. Besides that, on the other system everything is all right (reboot and burn - I assume that data may be inconsistent because of disc quality). Fedora 28 seemed to be fine too.
(In reply to Sabertooth from comment #12) > Indeed there are errors. I have insert that CDRW that seems to be damaged. > Fedora works fine until start brasero or reboot. Next I found DVDRW which > not generate errors. Fedora works perfectly fine (burn and reboot). > Apparently something is going on when damage disc is inserted. Obviously > CDRW is going to trash but how to prevent system in the future? It's > impossible to see every scratch or surface damage. Besides that, on the > other system everything is all right (reboot and burn - I assume that data > may be inconsistent because of disc quality). Fedora 28 seemed to be fine > too. I have had unused CDRs that showed large discolored regions and that were defective, so that is a possibility. Another issue is that if you burn with "Leave the disc open to add other files later" in Brasero, you get errors like these (which I just reproduced): Nov 12 13:58:02 fir kernel: sr 5:0:0:0: [sr0] tag#27 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 12 13:58:02 fir kernel: sr 5:0:0:0: [sr0] tag#27 Sense Key : Illegal Request [current] Nov 12 13:58:02 fir kernel: sr 5:0:0:0: [sr0] tag#27 Add. Sense: Illegal mode for this track Nov 12 13:58:02 fir kernel: sr 5:0:0:0: [sr0] tag#27 CDB: Read(10) 28 00 00 04 a2 22 00 00 02 00 Nov 12 13:58:02 fir kernel: print_req_error: I/O error, dev sr0, sector 1214600 Nov 12 13:58:02 fir kernel: attempt to access beyond end of device Nov 12 13:58:02 fir kernel: sr0: rw=0, want=1214608, limit=1214600 Nov 12 13:58:02 fir kernel: Buffer I/O error on dev sr0, logical block 151825, async page read If you want more flexibility in how your discs are burned, you might try "wodim", which is the command-line program that I use for making backups: $ cat ~/bin/bakburn.sh | fgrep wodim wodim $BURNDUMMY -v -dao -eject dev=$BURNER $ISONAME $ whatis wodim wodim (1) - write data to optical disk media Note the "-dao" option, in particular.
Wodim works fine for me. I have burned some discs and everything was perfectly fine. I also try to burn that broken CDRW. Wodim refuses to operate because of errors but Fedora didn't freeze. I think my problem is solved. In fact, there is still an issue booting the system with a damaged CD in the drive, but I will simply pay attention not to leave any optical discs in the drive. Thank you Steve for advice and support.
(In reply to Sabertooth from comment #14) > Wodim works fine for me. I have burned some discs and everything was > perfectly fine. I also try to burn that broken CDRW. Wodim refuses to > operate because of errors but Fedora didn't freeze. I think my problem is > solved. Thanks for your followup report. You can close the bug by changing the "Status" to "CLOSED" and setting the "Resolution" to "NOTABUG". (There is a "Status" link at the top of the page.) > In fact, there is still an issue booting the system with a damaged CD in the > drive, but I will simply pay attention not to leave any optical discs in the > drive. > Thank you Steve for advice and support. There could be an issue with how the optical drive's firmware handles disc errors. The DVD firmware may be more robust than the CD firmware. The "hdparm" command may give more info about the drive: # hdparm -i /dev/sr0 # hdparm -I /dev/sr0 See, also, the "smartctl" command: # smartctl -x -d sat /dev/sr0 (NB: With "SMART" hard drives, "smartctl" returns a lot more data, and the "-d" option is not needed.) There are man pages for both commands.