On a freshly rebooted U4, or V2, when I kick off the network scan, I get the following error: I need to exit out of the browser, and restart my network interface, and once that completes, I can then return to the network browser and successfully scan the network.
Looking at /var/log/messages, I see this odd error on my U4 (but not on the V2).
Code: Select all
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x0
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: irq_stat 0x40000000
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: cmd 60/f0:c0:78:b0:da/01:00:8f:00:00/40 tag 24 ncq dma 253952 in
May 24 19:30:38 beyonwizu4 user.err kernel: res 41/40:f0:78:b0:da/00:01:8f:00:00/00 Emask 0x409 (media error) <F>
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: status: { DRDY ERR }
May 24 19:30:38 beyonwizu4 user.err kernel: ata1.00: error: { UNC }
May 24 19:30:38 beyonwizu4 user.info kernel: ata1.00: configured for UDMA/133
May 24 19:30:38 beyonwizu4 user.info kernel: sd 0:0:0:0: [sda] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
May 24 19:30:38 beyonwizu4 user.info kernel: sd 0:0:0:0: [sda] tag#24 Sense Key : 0x3 [current]
May 24 19:30:38 beyonwizu4 user.info kernel: sd 0:0:0:0: [sda] tag#24 ASC=0x11 ASCQ=0x4
May 24 19:30:38 beyonwizu4 user.info kernel: sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 8f da b0 78 00 01 f0 00
May 24 19:30:38 beyonwizu4 user.err kernel: blk_update_request: I/O error, dev sda, sector 2413473912
May 24 19:30:38 beyonwizu4 user.info kernel: ata1: EH complete
Not sure if that is a clue, or a red herring.
Anyone else seeing network browser scan errors after a reboot?