LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Other *NIX Forums > Solaris / OpenSolaris
User Name
Password
Solaris / OpenSolaris This forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.

Notices

Reply
 
Search this Thread
Old 09-27-2006, 04:16 AM   #1
son_t
Member
 
Registered: Sep 2006
Posts: 49

Rep: Reputation: 15
device sd13 failed to power up error


I just installed Solaris 9 on a Ultra 1. Installation goes OK but on a reboot it comes up with the 'failed device sd13 failed to power up' error. This messages is constantly logged by syslog and is annoying since I don't have a sd13 device!

Anyone know what is causing this and how to fix it?
 
Old 09-27-2006, 06:25 AM   #2
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,522

Rep: Reputation: 365Reputation: 365Reputation: 365Reputation: 365
You probably have a CD reader as sd13.

Try turning of the automounter (/etc/init.d/volmgt stop) and see if the messages stop being sent. If true, check if no blank device is in the reader, or just install a recorded CD-ROM in the reader, enable the automounter (/etc/init.d/volmgt start) and see if that fix the errors.
 
Old 09-27-2006, 09:55 AM   #3
son_t
Member
 
Registered: Sep 2006
Posts: 49

Original Poster
Rep: Reputation: 15
Thanks for the reply - appreciated.

Looks like this is the problem. If I insert a CD in the drive - the machine boots up fine without the error message and the constant logging. But I am unable to fix this for the next reboot with out media in the drive...

It is a non-Sun CDROM drive so I guess this is the problem since I used the drive to install the OS in the first place - and doing that was OK...

PS. Putting in media and restarting vold did not work - the error constantly logs... only a reboot with media in the drive stops the logging and error.
 
Old 09-27-2006, 11:35 AM   #4
jlliagre
Moderator
 
Registered: Feb 2004
Location: Outside Paris
Distribution: Solaris10, Solaris 11, Mint, OL
Posts: 9,522

Rep: Reputation: 365Reputation: 365Reputation: 365Reputation: 365
I believe this bug is fixed in patch 113277, http://sunsolve.sun.com/pub-cgi/pdow...77-47&method=h, I would suggest you to install the recommended patch cluster for Solaris 9 from Sunsolve.
 
Old 09-28-2006, 03:57 AM   #5
son_t
Member
 
Registered: Sep 2006
Posts: 49

Original Poster
Rep: Reputation: 15
Thanks I will look into applying the patch...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Failed to open audio device (/dev/dsp): No such device stevesk Slackware 6 01-01-2009 07:29 AM
Failed to open device gt68xxLlibusb 004:002 invalid arguments error message radatan71 Linux - Hardware 1 10-24-2005 09:07 PM
Failed to open device /dev/usb/ttyUSB0: No such device efm Linux - Newbie 2 04-04-2005 09:46 PM
online_update failed - ERROR(Media:connection failed)[Connect failed] rover Suse/Novell 8 02-22-2005 08:57 AM
lpadmin: add-printer (set device) failed: client-error-not-possible Peca Linux - Hardware 7 08-14-2004 09:30 AM


All times are GMT -5. The time now is 11:54 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration