Forum Discussion

Sunkwan_Kim_147's avatar
Sunkwan_Kim_147
Icon for Nimbostratus rankNimbostratus
Jun 23, 2014

error log 'dma_intr:error=' inmessage log file

Dear All

I did reboot bigip6400. And then check the logs whether there is any error or not.

I found the error or something ,below.. 

Jun 21 12:47:50 dmz hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 21 12:47:50 dmz hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=79853387, high=4, low=12744523, sector=27012352
Jun 21 12:47:50 dmz end_request: I/O error, dev 16:08 (hdc), sector 27012352
Jun 21 12:48:03 dmz hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 21 12:48:03 dmz hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=79853387, high=4, low=12744523, sector=27012360
Jun 21 12:48:03 dmz end_request: I/O error, dev 16:08 (hdc), sector 27012360
.
.
.

I know, BIG-IP 6400 have Compact flash. It dosen’t support DMA. And read that related Sol doc.

I think that message logs should be up when the unit is rebooted only.. However; after the reboot is completed, it appears continuesly…

I want to know that these errors will not impact the operational status of the BIG-IP system

application delivery
dma
LTM
management
TMOS
TMSH

4 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jun 23, 2014

    I know, BIG-IP 6400 have Compact flash. It dosen’t support DMA. And read that related Sol doc.

    i understand 6400 has both compact flash (hda) and hard drive (hdc).

    e.g.

    [root@B6400-R69-S11:Active] config  fdisk -l
Ignoring extra extended partition 4

Disk /dev/hdc: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             2       124    987997+   b  Win95 FAT32
/dev/hdc2           125      7525  59448532+  83  Linux
/dev/hdc3          7526      8768   9984397+   5  Extended
/dev/hdc4          8769     10011   9984397+   5  Extended
/dev/hdc5          7526      7650    998439+  83  Linux
/dev/hdc6          7650      7774    998439   82  Linux swap
/dev/hdc7          7774      7898    998439   83  Linux
/dev/hdc8          7898      8644   5990637+  83  Linux
/dev/hdc9          8644      8768    998439   83  Linux

Disk /dev/hda: 521 MB, 521773056 bytes
16 heads, 63 sectors/track, 1011 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             2        11      5040    b  Win95 FAT32
/dev/hda3            12      1011    504000    5  Extended
/dev/hda5            12       791    393117+  83  Linux
/dev/hda6           791       791         1   82  Linux swap
/dev/hda7           792       911     60479   83  Linux
/dev/hda8           911      1011     50399   83  Linux
/dev/hda9          1011      1011         1   83  Linux

    have you tried file system check? if the error persists, i think you had better open a support case.

    sol10328: Forcing a file system check on the next system reboot

    http://support.f5.com/kb/en-us/solutions/public/10000/300/sol10328.html
    • Sunkwan_Kim_147's avatar
      Sunkwan_Kim_147
      Icon for Nimbostratus rankNimbostratus
      Jun 25, 2014
      Thanks nitass, I receive RMA because 'UncorrectableError' support team said, UncorrectableError usually means that some parts of your hard drive is not readable. If a build up of these errors occur, it can be that the hard drive may fail in the future or parts of it have already failed. If parts of the hard drive cannot be read or written due to these uncorrectable errors. In worst case scenario, it would fail completely and the system will fail to boot up.
  • nitass_89166's avatar
    nitass_89166
    Icon for Noctilucent rankNoctilucent
    Jun 23, 2014

    I know, BIG-IP 6400 have Compact flash. It dosen’t support DMA. And read that related Sol doc.

    i understand 6400 has both compact flash (hda) and hard drive (hdc).

    e.g.

    [root@B6400-R69-S11:Active] config  fdisk -l
Ignoring extra extended partition 4

Disk /dev/hdc: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             2       124    987997+   b  Win95 FAT32
/dev/hdc2           125      7525  59448532+  83  Linux
/dev/hdc3          7526      8768   9984397+   5  Extended
/dev/hdc4          8769     10011   9984397+   5  Extended
/dev/hdc5          7526      7650    998439+  83  Linux
/dev/hdc6          7650      7774    998439   82  Linux swap
/dev/hdc7          7774      7898    998439   83  Linux
/dev/hdc8          7898      8644   5990637+  83  Linux
/dev/hdc9          8644      8768    998439   83  Linux

Disk /dev/hda: 521 MB, 521773056 bytes
16 heads, 63 sectors/track, 1011 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             2        11      5040    b  Win95 FAT32
/dev/hda3            12      1011    504000    5  Extended
/dev/hda5            12       791    393117+  83  Linux
/dev/hda6           791       791         1   82  Linux swap
/dev/hda7           792       911     60479   83  Linux
/dev/hda8           911      1011     50399   83  Linux
/dev/hda9          1011      1011         1   83  Linux

    have you tried file system check? if the error persists, i think you had better open a support case.

    sol10328: Forcing a file system check on the next system reboot

    http://support.f5.com/kb/en-us/solutions/public/10000/300/sol10328.html
    • Sunkwan_Kim_147's avatar
      Sunkwan_Kim_147
      Icon for Nimbostratus rankNimbostratus
      Jun 25, 2014
      Thanks nitass, I receive RMA because 'UncorrectableError' support team said, UncorrectableError usually means that some parts of your hard drive is not readable. If a build up of these errors occur, it can be that the hard drive may fail in the future or parts of it have already failed. If parts of the hard drive cannot be read or written due to these uncorrectable errors. In worst case scenario, it would fail completely and the system will fail to boot up.