Description of problem: DVD writer test failed in RHEL 5.0 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: OSERVATIONS noted after the test failed: 1.I tried to take the screen of the error but it is not possible to take. after pressing print screen key "only a blank screen opened" then i take the screenshot through camera. 2.when excuted a command #neat, only blank screen opened. 3.when excuted a command #system-config-display only blank screen opened. 4.we restarted the machine, The machine is not booted inot the OS.It came stopped in the matainence mode by giving the statement "Press control+D to continue" I could not also able to copy "output.log" file. it showing the error as "you don't have enough permission".
Created attachment 295155 [details] picutre 1
Created attachment 295156 [details] picture2
(In reply to comment #0) > Description of problem: DVD writer test failed in RHEL 5.0 > Version-Release number of selected component (if applicable): > How reproducible: > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > Expected results: > Additional info: > OSERVATIONS noted after the test failed: > 1.I tried to take the screen of the error but it is not possible to take. after > pressing print screen key "only a blank screen opened" then i take the > screenshot through camera. > 2.when excuted a command #neat, only blank screen opened. > 3.when excuted a command #system-config-display only blank screen opened. > 4.we restarted the machine, The machine is not booted inot the OS.It came > stopped in the matainence mode by giving the statement "Press control+D to > continue" > I could not also able to copy "output.log" file. it showing the error as "you > don't have enough permission". Some more Details: Motherboard: ECS MCP61PM-AM ver 1.0A DVD writer: Lite ON DH-16A3P OS: RHEL 5.0 Tool: hts-5.0-48.noarch.rpm let me know how to resolvet his issue.
Elavazhagan, I'd guess this likely isn't a test suite problem; my guess is based on the 'Read only filesystem error'. The two cases I've seen for this are if you've network mounted /var and the second and more likely IMO is the system had some underlying fault which triggered the kernel to attempt to protect the filesystem by forcing it to read-only. This setup seems the most likely given your description of the events post reboot. I'd suggest checking the kernel logs to see what error occurred in the background, if it's reproducable you may also be able to enable remote logging to better capture any data that's currently being lost to the local logs. Also, FYI, these kinds of issues should be addressable using your regular support entitlement @ http://www.redhat.com/support instead of needing to open a bug in bugzilla.
(In reply to comment #4) > Elavazhagan, > I'd guess this likely isn't a test suite problem; my guess is based on the 'Read > only filesystem error'. The two cases I've seen for this are if you've network > mounted /var and the second and more likely IMO is the system had some > underlying fault which triggered the kernel to attempt to protect the filesystem > by forcing it to read-only. This setup seems the most likely given your > description of the events post reboot. I'd suggest checking the kernel logs to > see what error occurred in the background, if it's reproducable you may also be > able to enable remote logging to better capture any data that's currently being > lost to the local logs. > Also, FYI, these kinds of issues should be addressable using your regular > support entitlement @ http://www.redhat.com/support instead of needing to open a > bug in bugzilla. Dear rlandry, now we reload the OS and againg put the test with the new fresh media. This time we are not faced the issued esclated above. but the test gets failed. please find the attached log. let me know hpw to resolve this issue. with regards, Elavazhagan K
Created attachment 295241 [details] DVD writer failed test log
The log looks like a compare in the middle of the set failed, seems the media and the original didn't match. This combined with the previous failures really looks more like a hardware issue. If you manually burn an a media ISO will the media check pass?