On Fri, Aug 1, 2008 at 5:49 PM, darren <darren.e at sky.com> wrote: > hartz, sorry about that I posted my last msg before your post. > > may I first extend my sincere gratitude for the detailed and insighful > assitance you provided above. this is most useful and courteous of you. > > regretably I am unable to action ANY command that requires a write to a > file. > > I just get the error > > [code]svcadm: <service>: Repository read-only[/code] > > I cannot write to anywhere (touch >tmpfiletoday) gives: > [code]-bash: <any command i give>: Read-only filesystem. > > It sounds like your system is in service mode, though you did not say which commands you WERE able to execute successfully or what their output was.
The boot process mounts the boot archive read-only. It then figures out where it is (system architechture, drivers, disks). It then mounts the root disk read/write and the starts to load the rest of the kernel, configure device drivers, and then starts processes. To figure out where you are: 1) What is the last few messages you get before the # prompt appears? 2) What is the output from "mount"? It will tell you what is mounted as read-only and what is read-write. You want to see ZFS devices or real devices. Depending on the answers to those I will figure out where to from here. You can also check "who -r" to tell you the run-level, and svcs -a | grep milestone To see what has started. If you can tell us which ones are started it will help to find out what is going on. We will probably need to transition you to single-user and get the file systems mounted. To this extent, the output from svcs -x will also be helpfull. _Johan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20080801/1fb2f8a2/attachment.html>
