The pfSense Store

Author Topic: MOD_LOAD and ATA errors on boot.  (Read 2642 times)

0 Members and 1 Guest are viewing this topic.

Offline Com DAC

  • Jr. Member
  • **
  • Posts: 42
  • Karma: +1/-0
    • View Profile
MOD_LOAD and ATA errors on boot.
« on: January 20, 2015, 03:18:04 pm »
I'm running the latest pfsense 2.2 release in Hyper-V on Server 2012 R2 and these MOD_LOAD errors come up during boot:

Quote
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff8062def0, 0) error 1
Jan 20 15:49:55 kernel: iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff8062de40, 0) error 1
Jan 20 15:49:55 kernel: iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff8062dd90, 0) error 1
Jan 20 15:49:55 kernel: iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80606720, 0) error 1
Jan 20 15:49:55 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80606670, 0) error 1
Jan 20 15:49:55 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Jan 20 15:49:55 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff806065c0, 0) error 1
Jan 20 15:49:55 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Jan 20 15:49:55 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.

and these ATA errors:

Quote
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): Error 5, Retries exhausted
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): RES: 51 00 00 00 00 00 00 00 00 00 00
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 00 ()
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): SETFEATURES ENABLE WCACHE. ACB: ef 02 00 00 00 40 00 00 00 00 00 00
Jan 20 15:49:55 kernel: da0: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C)
Jan 20 15:49:55 kernel: da0: Command Queueing enabled
Jan 20 15:49:55 kernel: da0: 300.000MB/s transfers
Jan 20 15:49:55 kernel: da0: <Msft Virtual Disk 1.0> Fixed Direct Access SCSI-4 device
Jan 20 15:49:55 kernel: da0 at blkvsc0 bus 0 scbus2 target 0 lun 0
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): Retrying command
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): RES: 51 00 00 00 00 00 00 00 00 00 00
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 00 ()
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error
Jan 20 15:49:55 kernel: (ada0:ata0:0:0:0): SETFEATURES ENABLE WCACHE. ACB: ef 02 00 00 00 40 00 00 00 00 00 00
Jan 20 15:49:55 kernel: ada0: Previously was known as ad0
Jan 20 15:49:55 kernel: ada0: 2048MB (4194304 512 byte sectors: 16H 63S/T 4161C)
Jan 20 15:49:55 kernel: ada0: 16.700MB/s transfers (WDMA2, PIO 65536bytes)
Jan 20 15:49:55 kernel: ada0: <Virtual HD 1.1.0> ATA-8 device
Jan 20 15:49:55 kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0

Are they anything I should be concerned about? Am I maybe missing a setting somewhere?

Thank you,
David

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Re: MOD_LOAD and ATA errors on boot.
« Reply #1 on: January 20, 2015, 04:11:27 pm »
the first is normal in all circumstances, the second is normal at this point in Hyper-V but seems to only be cosmetic for most people (it's one that Microsoft's looking into).