Solaris 10 boot hang up
Hi
I have a problem.My solaris 10 hangs up during boot.The last message displayed is
/dev/rdsk/c1t2d0s6 is logging
after this message is nothing happening.I dont know what to do.The last change I made was that I added to in.routed parameter -T /var/log/routed for logging.
I tried to boot the instalation CD and go to console but mounting of my drives was unsuccesfull.I hoped that I will do chroot to root partition and fix the in.routed but I cannot mount drives :(
Please help me.
Thank YOU
[544 byte] By [
simkoa] at [2007-11-25 22:55:40]

# 3
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>simkoa wrote on Fri, 07 October 2005 15:25</b></td></tr><tr><td class="quote">
So I run interactive mode from the Solaris 10 installation CD and go to the console.
</td></tr></table>
Btw. you are using Solaris 10 x86 (and not SPARC hardware), correct?
This is the "Solaris on x86" forum, but you never know...
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr>& lt;td class="quote">
When I tried to
mount /dev/rdsk/c1t2d0s6 /mnt I get is not a block device.
</td></tr></table>
Yep, /dev/rdsk/* are raw devices. Mounting a filesystem works using the
block device, which is /dev/dsk/*
Btw. are you sure that Slice #6 contains the root filesystem?
Or is slice #6 just a slice for a separate filesystem?
Convention is to use slice #0 for the root filesystem, slice #1 for swap space
(and slice #2 for all of the disk). But it is possible to ignore these
conventions and install a solaris system to use slice #6 for root.
The following command lists the available slices on the c1t2d0 disk:
prtvtoc /dev/rdsk/c1t2d0s2
Btw. if slice #6 is <b>not</b> the root filesystem but some data slice,
you can try to boot Solaris from the HDD into single user mode. To do
that, enter the boot command
b -s
at the Solaris boot prompt.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr>& lt;td class="quote">
I tried also other devices like /dev/dsk/c0t0d0s1 and I get already mounted or /mnt busy.
</td></tr></table>
You can use "iostat -En" to list the installed disks.
My guess is that c0t0d0 is your CDROM device.
Unfortunatelly iostat won't list IDE disks on Solaris x86. An alternate
command is to run "format", it starts by printing a menu with the
available disks (you can press the EOF character "Ctrl-D" at this menu
to leave format).
But the disk name c1t2d0s6 is a hint that it's a scsi device that you're
trying to mount, so iostat -En should work ....
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr>& lt;td class="quote">
I read somewhere to start boot CD from freesbie.org and when I trie to mount I gat bad super block.
</td></tr></table>
Huh?
freesbie.org is about a FreeBSD live CD.I'm not sure if the use of a foreign
operating system is a good idea to fix Solaris OS problems. Even if they
have SunOS x86 UFS filesystem support ....
Of cause you have to boot from a Solaris CD to fix / repair a Solaris
installation.
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr>& lt;td class="quote">
I tried also to run in.routed again and I get error opening /etc/inet/routing.conf read-only system.
</td></tr></table>
When you have booted from the Solaris installation CD?
That won't work. When you have booted from the Solaris CD you
should mount the HDD root filesystem - for example at "/a" - and fix
the configuration files on the HDD using pathes like /a/etc/inet/routing.conf
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr>& lt;td class="quote">
So my question is.How can I remount the system to read-write?And what I should change to skip logging message?Is there in solaris any Interactive startup like in linux when you press "i"?
</td></tr></table>
I'd try the Solaris HDD boot with the "-s" (single user mode) option, and
if that is able to startup in single user mode, you might be able to fix the
problem from the single user mode login. You can also use boot options
"-vs" (that is, boot with: b -vs) to boot into single user mode with verbose
kernel messages.
If that does not work, you can try the Solaris CD boot, and mount the root
filesystem in read/write mode on the /a mount point, and fix the configuration
problem on the filesystem mounted under /a.
jkeil at 2007-7-5 17:11:03 >
