This content has been marked as final. Show 37 replies
We are seeing the exact same thing happening at our site. We rebooted two and they both had the exact same symptom..
Jan 4 07:43:20 servername SunPCi: [ID 702911 user.error] Your System Time appears to be set in the future
Jan 4 07:43:20 servername SunPCi: [ID 702911 user.error] I can't believe it's really Mon Jan 4 07:43:20 2010
Jan 4 07:43:20 servername SunPCi: [ID 702911 user.error] Please set the system time correctly
Confirm that get the failure with SunPCI3:
Another machine with SunPCI2 fitted doesn't suffer this problem.
bash-3.00$ /opt/SUNWspci3/bin/sunpci -vga -C /tmp/2K.diskimge SunPCi: This machine has multiple network interfaces. If you are using SunPC networking, you need to set the environment variable NVL_INTERFACE to indicate the desired network interface. Type netstat -i for a list of interfaces on this machine. Opening a SunPCi window... Your System Time appears to be set in the future I can't believe it's really Mon Jan 4 23:35:52 2010 Please set the system time correctly
(In both cases was using a Windows 2K professional disk image)
I placed a call to Sun. They are working on this bug, but they don't know when a fix will be available. We couldn't wait, so here is how we started our cards. Depending on your setup, configuration or site policies, some of you may not be able to do this. Do this at your own risk - one of our systems crashed the first time we did this:
- Shutdown any non-essential processes, in case the system crashes or hangs.
- Temporarily change the date/time back to 2009.
- Run the sunpci command.
- As soon as the SunPCI window appears, change the date/time back to the present.
- The card should continue to boot. Once it is up, it will show the current date/time.
I have the same problem. The only way I got this to work was to set the system time back to 2009. As you say once the card boots up there is nothing stopping you from adjusting the system back to what it was. Of course to do this you need root access. So your mileage may vary. This bug really sucks.
Here is the response we recieved from Sun when a case was opened:
The problem you are observing is being addressed in CR 6913785, which was opened on Dec 31, 2009 when 4 other customer's called with the same issue (there has been quite a few more cases since then). The problem is in the sunpci binary and engineering thinks they are close to having a fix available very soon, but we'll see. As I am now your case owner, I'll let you know when I get an update, and with all the cases being opened, there should be one soon. I will also add this SR to the bug during my work hours on Tuesday.
Found that the validate_system_time function in the sunpcbinary program is the one which causes the error.
In a hex editor (ghex2) I changed the longword at offset 4CF8 in sunpcbinary from 7FFFFE2E to 01000000. This replaces the call to validate_system_time with a nop. With this modified sunpcbinary managed to get SunPCI3 to boot without having to change the date.
This modification was made to the sunpcbinary from SUNWspci3 version 3.2.2, and may not apply to other versions. Since the sunpcbinary has been manually modified, pkgchk will report the following error:
# pkgchk SUNWspci3 ERROR: /opt/SUNWspci3/bin/sunpcbinary modtime <09/09/04 05:19:09 AM> expected <01/05/10 11:08:38 PM> actual file cksum <47458> expected <46777> actual
Thanks Sun-Worshipper. I'm a newby to the forums and your solution is a lifesaver.
I actually downloaded sweetscapes hexeditor:
It's very easy if you have a windows box available. I've never worked with binary files or editors before. I moved the sunpcbinary to a windows machine downloaded the editor, Installed the software and had it edited in less than five minutes. Place the file back in place and am now up and running.
Using SweetScape to edit the binary, I see 00000001 at offset 4CF8. This is the data when read from left to right ie. from 4CF8h to 4CFBh. Wondering, if this reads as 01000000 if considered little-endian, correct ?
I am running OS, if matters any:
5.8 Generic_108528-13 sun4u sparc SUNW,Sun-Blade-100
Sun-Worshiper. I was able to fix SunPCI 3.2.2 binary. I'm in the process of using a hexeditor to find the validate_system_time call in the SunPCI 3.1 binary. Being new to this I was wondering if you might be able to educate me on how you figured out the offset where the call was made.
Any help you can give would be greatly appreciated.