Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help Can't Open boot device

Status
Not open for further replies.

AlexRabbot

Programmer
Nov 15, 2003
17
US
I have an Ultra 10 with Solaris 2.5.1 that I would like to use only as a test environment to play with #ufsdump and then #ufsrestore for /, /var and /usr partitions only and then later install Veritas Netbackup 5.0 for the same purposre and when I get comfortable with ufsdump; ufsrestore and NetBackup I will install NetBackUp on SUN FIRE V880. The Ulta 10 was a working unit, I replaced it with SUN BLADE 1500 for the user's request. The Ultra 10
was at the other location (IP address 172.30.41.62).
I disconected everything and brougt to a different location where I plan on working on it. Network administrator assigne4d IP address 172.30.7.265 and after I connected everything, I can't boot the station, receiving the message: 'SUNW,hme0: Link down Cable problem?'
I took the Ultra 10 back to the original location just as a test and was able to boot it without any problem.
Any suggestions and comments would be appreciated.
Thank you,
Alex


 
I have found the 'SUNW,hme0: Link down Cable problem?' to be spurious in the past and machines I have had it on have gone on to boot OK, including the network adapter. Have you the opportunity to boot it from CD and examine /etec/hosts etc to see what the settings there are?
 
Ken,
I had a similar problem recently. I moved my ultra 5 to a non-networked location and have been getting this message during bootup

"SUNW,hme0 No response from ethernet network : linkdown cable problem". I have tried "boot /reconfigure" without success. When the system comes up I get this message "sendmail [204] : id [ID 702911 mail.crit] my unqualified hostname (localhost) unknown; sleeping for retry"

then

"sendmail [204] : id [ID 702911 mail.alert] unable to qualify my own domain name (localhost) - using short name"

what's up with that?
 
Hi. Nothing is really wrong, it's just a warning that sendmail isn't finding what it expects. You have two options - if you aren't planning to use sendmail, don't start it. To do this change the name of S88sendmail in /etc/rc2.d to s88sendmail (ie a lower case s). If you do want it running add <boxname>. (note the period) at the end of the entry in /etc/hosts. Something like this:

xxx.x.xxx.x boxname boxname. #loghost

That should get rid of this message. HTH.
 
hme link problem:
did you try a sys-unconfig and boot the host at it's final destination?
link problems might be caused by non working autonegotiation, I suggest to set link mode and speed by hand!
-> search this Forum or google for "ndd -set /dev/hme"

sendmail:
>> xxx.x.xxx.x boxname boxname. #loghost
please do not! Ether disable sendmail (since you do not need it running if your host is not a MTA/MX or configure it.
Add ether a FQHN to /etc/hosts
xxx.x.xxx.x boxname boxname.mydomain.com
or set Dj in /etc/mail/sendmail.cf
# my official domain name
# ... define this only if sendmail cannot automatically determine your domain
#Dj$w.Foo.COM


Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years
 
OK Franz, I'm intrigued. Why the warning not to simply add the period? I think that's a tip I picked up on here some time back so if there's anything untoward about it, I'd be glad to know. Cheers.
 
in my eyes adding a period to hostname it's like going to the dentist because of a whole in a tooth and the dentist prescribes Aspirin... ;-)
I prefere ether to remove the tooth or fix it... :)

afaik: sendmail tries to get domainnaim ether from /etc/domainname or tries to derive it from the hostname. If you create /etc/domainname Solris tries to start a NIS or NIS+ Domain. In many installations you will not need this or have other solutions -> bad idea
derive it from hostname: ok, my FQHN is hostname. so the domainame is "." -> sendmail is pacified but it's technically not a fix...

But how do the English say: Chacun à son goût

;-)

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top