Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-)
hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy }
ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: dma_timer_expiry: dma status == 0x21 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11242760 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11435969, high=0, low=11435969, sector=11435968 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11435968 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11277069, high=0, low=11277069, sector=11277064 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11277064 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11277069, high=0, low=11277069, sector=11277064 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11277064 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11277069, high=0, low=11277069, sector=11277064 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11277064 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11277069, high=0, low=11277069, sector=11277064 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11277064 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11277069, high=0, low=11277069, sector=11277064 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11277064 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11435269, high=0, low=11435269, sector=11435264 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 11435264 hda: dma_timer_expiry: dma status == 0x21 hda: DMA timeout error hda: dma timeout error: status=0xd0 { Busy }
ide: failed opcode was: unknown hda: DMA disabled ide0: reset: success hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown ide0: reset: success hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 31873944 hda: status timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown hda: DMA disabled hda: drive not ready for command ide0: reset: success
On Saturday 19 November 2005 13:40, Morten wrote:
Hi, I get the below from dmesg. The server seems to run fine, but it does worry me. What should I do? Other than take a backup.. :-)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760
I have seen several causes for this; three of the most common are: 1.) A failing disk; run 'smartctl -a' and see what SMART tells you about the disk's health; 2.) A disk that got 'scribbled' due to a power interruption to the drive (either through a failing power supply, or an actual electrical blip or failure) while the drive was writing; the manufacturer's 'recovery' program can typically remap sectors around this sort of damage; 3.) A corrupted filesystem that has linkages outside the drive's boundaries; if the drive tries to seek past the end of the disk you get this. The LBA numbers you have would seem to rule this out, but you didn't say how big the disk was.
In short, an UncorrectableError is exactly what it says it is; it couldn't read a sector it tried to read.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=11242764, high=0, low=11242764, sector=11242760
I have seen several causes for this; three of the most common are: 1.) A failing disk; run 'smartctl -a' and see what SMART tells you about the disk's health;
SMART overall-health self-assessment test result: PASSED
But the report does contain records of errors, eg.:
Error 5 occurred at disk power-on lifetime: 18734 hours (780 days + 14 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 03 0d 13 ac e0 Error: UNC 3 sectors at LBA = 0x00ac130d = 11277069
3.) A corrupted filesystem that has linkages outside the drive's boundaries; if the drive tries to seek past the end of the disk you get this. The LBA numbers you have would seem to rule this out, but you didn't say how big the disk was.
It's a 36G disk.
In short, an UncorrectableError is exactly what it says it is; it couldn't read a sector it tried to read.
Thanks. I'll probably replace the disk.
Br,
Morten
Hello,
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
Suggestions anyone? Thanks!
On Sun, 2005-11-20 at 16:14 -0800, Jack Bailey wrote:
Hello,
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
Suggestions anyone? Thanks!
Temporary fix idea: yum install kdm
Let everyone know if this works, I've used this before in Debian not CentOS...
Ryan wrote:
On Sun, 2005-11-20 at 16:14 -0800, Jack Bailey wrote:
Hello,
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
Suggestions anyone? Thanks!
Temporary fix idea: yum install kdm
Let everyone know if this works, I've used this before in Debian not CentOS...
# yum install kdm Setting up Install Process Setting up repositories update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files Parsing package install arguments No Match for argument: kdm Nothing to do
Jack Bailey wrote:
# yum install kdm Setting up Install Process Setting up repositories update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files Parsing package install arguments No Match for argument: kdm Nothing to do
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
KDM comes as part of the kdebase package, which of course will install most of KDE along with it. So yum install kdebase.
On 11/21/05, Jack Bailey jack@internetguy.net wrote:
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
If you can boot of any live cd you can then edit /etc/gdm/gdm.conf Go the line which has the above path and comment it out. Likely this would work.
Learning Linux
Sudev Barar wrote:
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
If you can boot of any live cd you can then edit /etc/gdm/gdm.conf Go the line which has the above path and comment it out. Likely this would work.
/etc/X11/gdm/gdm.conf? I looked at that for awhile, and for grins I changed:
GraphicalTheme=Default
to:
GraphicalTheme=Bluecurve
It's now complaining about icon-language.png instead of background.png.
On Mon, 2005-11-21 at 02:54 -0800, Jack Bailey wrote:
If you can boot of any live cd you can then edit /etc/gdm/gdm.conf Go the line which has the above path and comment it out. Likely this would work.
/etc/X11/gdm/gdm.conf? I looked at that for awhile, and for grins I changed:
GraphicalTheme=Default
to:
GraphicalTheme=Bluecurve
It's now complaining about icon-language.png instead of background.png.
Did you try yum remove gdm && yum install gdm ?
/etc/X11/gdm/gdm.conf? I looked at that for awhile, and for grins I changed:
GraphicalTheme=Default
to:
GraphicalTheme=Bluecurve
It's now complaining about icon-language.png instead of background.png.
Did you try yum remove gdm && yum install gdm ?
No, I hadn't retried that, so I just did now. No change. The problem is somewhere else, somewhere in a recent update. I now have another server doing the same thing.
Jack
On 11/21/05, Jack Bailey jack@internetguy.net wrote:
/etc/X11/gdm/gdm.conf? I looked at that for awhile, and for grins I changed:
GraphicalTheme=Default
to:
GraphicalTheme=Bluecurve
It's now complaining about icon-language.png instead of background.png.
Did you try yum remove gdm && yum install gdm ?
No, I hadn't retried that, so I just did now. No change. The problem is somewhere else, somewhere in a recent update. I now have another server doing the same thing.
I haven't run into this problem with any of our upgrades, but there are a couple things you can check. Make sure that (and I'm making the grand assumption of centos4 here) libpng is installed, that in /etc/sysconfig/selinux SELINUXTYPE is set to targeted and not strict (if it's enabled at all), and that the permissions on the directory are as they should be. A quick way to check the files would be to rpm -Vv gdm (man rpm, under verify section for what the different results mean) and see what it if anything it marks as altered. You might also consider doing this to redhat-artwork, since this is the package that actually contains the theme that's breaking.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On 11/21/05, Jack Bailey jack@internetguy.net wrote:
Sudev Barar wrote:
Went to login to the console this morning and got few errors about bad PNG files. Logged out, now I can't log back in. The lone dialog box has the following:
There was an error loading the theme Default Couldn't recognize the image file format for file '/usr/share/gdm/themes/Default/background.png'
I click OK, nothing happens.
If you can boot of any live cd you can then edit /etc/gdm/gdm.conf Go the line which has the above path and comment it out. Likely this would work.
/etc/X11/gdm/gdm.conf? I looked at that for awhile, and for grins I changed:
GraphicalTheme=Default
to:
GraphicalTheme=Bluecurve
It's now complaining about icon-language.png instead of background.png.
In my book that is progress. First make sure that the directory /usr/share/gdm/themes/Default exists. If not then what some else mentioned yum upgrade gdm is your answer. If it does then you need to work out why permissions or such are being denied.
The file is very well commented. You can find a line saying something about greeter? change this to standard instead of graphic. See the line which pertains to remote greeter.
HTH -- Sudev Barar Learning Linux
-
Jack Bailey -
Jim Perrin -
Lamar Owen -
Morten -
Ryan -
Sudev Barar -
Tim Edwards