It's usually a bit and miss to be honest. I only have one of the
machines I run smartos on report a UUID that is not all 0.
Most of them are SuperMicro too, I guess it is more of a OEM BIOS verder
specific thing, I think they were all AMI.
On 2017-04-03 23:42, Robert Mustacchi wrote:
On 4/3/17 0:22 , 강경원 wrote:
Hello.
We are testing SDC with same SMBIOS uuid servers.
We recommend that you talk to your hardware vendor and have them
provide
tooling to fix the server's UUID. If they have the same UUID, they've
not properly implemented the SMBIOS spec (though it's far from the
first
time we've heard of this).
So we tried to modify images's sysinfo script to test and after
modifing the
sysinfo, the fake uuid can be created successfully and can be setup.
But when we try to reboot the node, below error message is shown and
rebooting
is not working.
The only thing that we can do is ipmi power reset.
How can we avoid the errors?
svc.startd: Killing user processes.
WARNING: Error writing ufs log state
WARNING: ufs log for /usr changed state to Error
WARNING: Please umount(1M) /usr and run fsck(1M)
Given what little information we have to work on, I'd suggest you
review
your procedure for building and modifying the live image for how you
updated sysinfo to your custom version. Without knowing what you've
done
or not done or how you've done it, it's hard to suggest actionable
steps
to take.
Robert
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
