dos2unixtime kernel?? Disk image gone

Question

Level 1

0 points

dos2unixtime kernel?? Disk image gone

OK, this is a new one on me. I have a G5x2 1.8 has been just fine for it's entire life. Smooth fast and reliable. I use it mainly for production work. It is connected to the airport hub for our studio, but I prefer not to go online unless it's absolutely necessary. (mainly for updates, driver dnlds, etc.) There are five other computers on the same airport LAN. All Apple's, all happy.

The G5x2 spits out "kernel[0]: dos2unixtime month value out of range (0)" over and over. Until I turn on the airport. It starts by sending out this:

10:26:04.945313 arp who-has 10.0.1.6 tell 0.0.0.0
10:26:04.945901 arp who-has 10.0.1.6 tell 10.0.1.6
10:26:05.252492 arp who-has 10.0.1.6 tell 10.0.1.6
10:26:05.253098 arp who-has 10.0.1.1 tell 10.0.1.6
10:26:05.539008 IP 10.0.1.3.49991 > resolver1.opendns.com.domain: UDP, length 38
10:26:05.559881 IP6 fe80::211:24ff:fea6:a0d0 > ff02::1:ffa6:a0d0: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ffa6:a0d0, length 24
10:26:05.593382 IP resolver1.opendns.com.domain > 10.0.1.3.49991: UDP, length 38
10:26:05.866988 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:06.595692 IP 10.0.1.3.49992 > resolver1.opendns.com.domain: UDP, length 90
10:26:06.858798 IP resolver1.opendns.com.domain > 10.0.1.3.49992: UDP, length 90
10:26:06.868726 IP 10.0.1.3.49993 > resolver1.opendns.com.domain: UDP, length 39
10:26:06.922833 IP resolver1.opendns.com.domain > 10.0.1.3.49993: UDP, length 39
10:26:06.925819 IP 10.0.1.3.49994 > resolver1.opendns.com.domain: UDP, length 90
10:26:06.978375 IP resolver1.opendns.com.domain > 10.0.1.3.49994: UDP, length 90
10:26:07.403001 IP 10.0.1.6 > 224.0.0.251: igmp
10:26:07.711193 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 260
10:26:08.018413 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 260
10:26:08.325613 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 260
10:26:08.327948 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:08.631796 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:09.555217 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:11.398418 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:12.932654 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:15.392026 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:16.004600 IP 10.0.1.6 > 224.0.0.251: igmp
10:26:21.534447 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:23.379296 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:25.425702 IP 10.0.1.3.mdns > 224.0.0.251.mdns: UDP, length 49
10:26:25.425814 IP6 Macintosh.local.mdns > ff02::fb.mdns: UDP, length 49
10:26:25.530016 IP 10.0.1.1.mdns > 224.0.0.251.mdns: UDP, length 119
10:26:30.136166 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:32.303592 IP 10.0.1.3.49995 > 10.0.1.255.netbios-ns: UDP, length 50
10:26:32.573980 IP 10.0.1.3.49995 > 10.0.1.255.netbios-ns: UDP, length 50
10:26:32.844288 IP 10.0.1.3.49995 > 10.0.1.255.netbios-ns: UDP, length 50
10:26:32.983104 IP 10.0.1.3.49996 > resolver1.opendns.com.domain: UDP, length 41
10:26:33.037818 IP resolver1.opendns.com.domain > 10.0.1.3.49996: UDP, length 41
10:26:38.123381 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:39.353874 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:26:47.032222 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:26:48.007652 IP 10.0.1.3.ntp > time1.apple.com.ntp: UDP, length 48
10:26:48.044109 IP time1.apple.com.ntp > 10.0.1.3.ntp: UDP, length 48
10:26:48.261024 arp who-has 10.0.1.3 (00:14:51:5d:48:ec (oui Unknown)) tell 10.0.1.1
10:26:48.261063 arp reply 10.0.1.3 is-at 00:14:51:ec:e9:04 (oui Unknown)
10:26:55.634006 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:27:04.542873 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:27:09.093698 IP 10.0.1.3.mdns > resolver1.opendns.com.domain: UDP, length 64
10:27:09.238596 IP resolver1.opendns.com.domain > 10.0.1.3.mdns: UDP, length 64
10:27:11.303047 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 453
10:27:13.144521 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:27:40.485972 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 84
10:27:42.943602 IP 10.0.1.6.mdns > 224.0.0.251.mdns: UDP, length 105
10:27:42.944233 IP 10.0.1.6 > ALL-ROUTERS.MCAST.NET: igmp
10:27:43.343122 IP 10.0.1.3.49997 > resolver1.opendns.com.domain: UDP, length 40
10:27:43.498002 IP resolver1.opendns.com.domain > 10.0.1.3.49997: UDP, length 75
10:27:51.008298 IP 10.0.1.3.ntp > time1.apple.com.ntp: UDP, length 48
10:27:51.046466 IP time1.apple.com.ntp > 10.0.1.3.ntp: UDP, length 48
10:28:05.570265 IP 10.0.1.3.mdns > 224.0.0.251.mdns: UDP, length 49
10:28:05.570378 IP6 Macintosh.local.mdns > ff02::fb.mdns: UDP, length 49
10:28:05.679119 IP 10.0.1.1.mdns > 224.0.0.251.mdns: UDP, length 119
10:28:07.826731 IP 10.0.1.7 > 224.0.0.251: igmp
10:28:08.501891 IP 10.0.1.3.49998 > resolver1.opendns.com.domain: UDP, length 39
10:28:08.639855 IP resolver1.opendns.com.domain > 10.0.1.3.49998: UDP, length 39
10:28:10.242548 IP 10.0.1.3.mdns > 10.0.1.1.nat-pmp: UDP, length 2
10:28:10.243519 IP 10.0.1.1.nat-pmp > 10.0.1.3.mdns: UDP, length 12
10:28:10.898714 arp who-has 10.0.1.1 tell 10.0.1.7
10:28:11.205948 IP 10.0.1.7 > 224.0.0.251: igmp
10:28:27.796148 IP 0.0.0.0.bootpc > broadcasthost.bootps: UDP, length 300
10:28:27.796833 IP6 fe80::211:24ff:fea6:a0d0 > ff02::1:ffa6:a0d0: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ffa6:a0d0, length 24
10:28:27.797607 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2:895b:164c: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::2:895b:164c, length 24
10:28:28.409536 IP6 :: > ff02::1:ffa6:a0d0: ICMP6, neighbor solicitation, who has fe80::211:24ff:fea6:a0d0, length 24
10:28:28.643534 IP 10.0.1.3.49999 > resolver1.opendns.com.domain: UDP, length 90
10:28:28.716554 arp who-has 10.0.1.6 tell 0.0.0.0
10:28:28.907415 IP resolver1.opendns.com.domain > 10.0.1.3.49999: UDP, length 90
10:28:29.023720 arp who-has 10.0.1.6 tell 0.0.0.0
10:28:29.024355 IP 10.0.1.7 > ALL-ROUTERS.MCAST.NET: igmp
10:28:29.024968 IP 10.0.1.7 > 224.0.0.251: igmp
10:28:29.330985 arp who-has 10.0.1.6 tell 0.0.0.0
10:28:29.638183 IP6 fe80::211:24ff:fea6:a0d0 > ff02::2: ICMP6, router solicitation, length 16
10:28:29.638731 arp who-has 10.0.1.6 tell 0.0.0.0

If I disable the airport, turn it off in syspref's, then re-boot, this little message starts reeling it out until I connect to my AP. It does it's thing then it's over.

The other day I was working in Digital Performer and noticed my processor was spiking and the comp was otherwise sluggish. That's where I found the console message log dispensing the messages. Turning the AP on and letting the kernel run resulted in a faster quieter good ole mac. And maybe this isn't related but my main HD image is gone. It's listed as a folder?

Someone have a clue?

Thanks

G52x 1.8 4g 2HD, Mac OS X (10.4.11)

Posted on Nov 28, 2007 10:10 AM

Reply

Answer 1

Curious1 Author

Level 1

0 points

Nov 28, 2007 12:23 PM in response to Curious1

OK, after a little sleuthing I turned off an external HD, which I hadn't realized was formatted "Fat-32".

When I turned it off those dos2unixtime messages stopped.

Any clues? I use the HD for my Audio Units.

Thanks,

Reply

Answer 2

BDAqua

Level 10

239,183 points

Nov 28, 2007 1:39 PM in response to Curious1

Is that Volume/HD set to Automount? SMB or NFS?

Reply

Answer 3

Curious1 Author

Level 1

0 points

Nov 28, 2007 1:53 PM in response to BDAqua

I don't know. How do I tell, what do I look at?

Thanks!

Reply

Answer 4

BDAqua

Level 10

239,183 points

Nov 28, 2007 2:11 PM in response to Curious1

Hmmm, not sure exactly how to check it, but one would usually have dragged it to Accounts>Login Items, or used something like Sharepoints Automounter to make it so. There can be things in the System part that mount it also.

Is this a NAS drive, or USB? FW?

Another thought is there some APP on the internal drive that is set to automatically save to or use that drive?

Last time I saw the dos2unixtime thing was when connecting to an NFS or Windows server that would fail if the Time between the two was off by a minute or so.

Reply

Answer 5

Curious1 Author

Level 1

0 points

Nov 28, 2007 7:23 PM in response to BDAqua

Hi, and thanks for the help, again.

OK, I guess there would be some connection between midi over LAN and the FAT 32 external HD. I have enabled at start up core-audio/midi. It looks for the connection from a networked computer, which sometimes I don't turn on. Then I think I should be able to somehow make a setting in the sysprefs that I look for it when I need it and not when I don't. Got any ideas? Thanks for your input! I am not the greatest on the networking stuff. I don't like to mess with anything once it's up and running.

Reply

Answer 6

BDAqua

Level 10

239,183 points

Nov 28, 2007 8:27 PM in response to Curious1

You could write a script to check for the Networked computer before it tries looking for it, and put that in startup, or just remove that core-audio/midi from startup, and just pounce on it when you know it's up & running... then there is a little ShareWare app that can handle such things...

MountWatcher...
http://www.macupdate.com/info.php/id/21357

Reply

Answer 7

Curious1 Author

Level 1

0 points

Nov 29, 2007 6:23 AM in response to BDAqua

Thanks BD!

Reply