See for sample vfstab (half way down) http://docs.sun.com/db/doc/805-3727/6j3ht4dks?q=%22%2fetc%2fvfstab%22+%2bsample&a =view If vi will not start because it cant write to a temporary location try changing the environment varilable that sets this path Home | Invite Peers | More UNIX Groups Your account is ready. INFORMATION: Unable to determine size or capacity of slice . The media contains version . http://gsbook.org/error-could/error-could-not-open-wav-file.php
yes. Great Web Hosting Relevant Unix Tutorial Return to top of pageCopyright ©2016 · eleven40 theme on Genesis Framework · WordPress · Log in Ubuntu Forums > The Ubuntu Forum Community > m.cunningham replied May 9, 2003 How about at boot Stop A into single user mode and then editing vfstab Ciao! in your mount command, use the device file name which is in the 1st column. http://www.tek-tips.com/viewthread.cfm?qid=868810
Boot of the CDROM as previously mentioned. I reburned the Solaris 9 CDROM and it worked fine. ----- Original Message ----- From: "Sun Consultant"
If I attempt mount
And after a short while more, I've learned how exactly I got my miniroot image corrupted in the first place: I had my netinstall image in the /export/vol1/jumpstart/images directory, which I PDA View Full Version : [SOLVED] Fstab Accidentally Renamed! No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers this contact form You may be able to invoke vi without a tmp file?
SUNWsrh..........................done. 1.00 Mbytes remaining. INFORMATION: After activated and booted into new BE , Auto Registration happens automatically with the following Information autoreg=disable ####################################################################### Validating the contents of the media . Or perhaps I have misunderstood the problem. Is there a way to recreate the file?
Any advice for me? https://ubuntuforums.org/archive/index.php/t-2168393.html I'm off t'chill wi't me Joolie Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... if you look in /etc/rcS.d/S40standardmounts.sh you will see that Solaris simply remounts the root filesystem read-write during the normal boot process (assuming a sane boot environment, with /etc/vfstab present). Minimize the amount of time you run with submirrors that are disabled or offline.
Halted ... http://gsbook.org/error-could/error-could-not-open-ide21201-vxd-file.php Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Creating file systems on boot environment . That took care of it Thank you all so much.
I don't have any boot media - No OS - CD or otherwise. 2.. This is release noted in the Readme of the Recommended Patchset. hope to learn from you all! Source As the result of this error, you're left with some directories of your miniroot having regular files instead of symlinks.
Romeo Ninov replied May 12, 2003 What about download RH ISO for sparc, boot from CD and try to edit file you need? <><><><><><><><><>& lt;><><><><><><> Regards: Romeo Ninov <><><><><><><><><>& lt;><><><><><><> Top So, I pressed CTRL ALT F2 and it took me to a shell that said General error mounting filesystems. If the software has encountered a failure, other slices on the same disk will likely experience failures soon.
Click Here to join Tek-Tips and talk with other members! Source boot environment is . Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... We would love to hear from you to see how your Unix infrastructure can be improved.
Connect with top rated Experts 11 Experts available now in Live! When I tried to reboot, I just got a black screen. It is: :wq! INFORMATION: Unable to determine size or capacity of slice .
Comparing source boot environment file systems with the file system(s) you specified for the new boot environment. The incorrect /etc/vfstab file looks similar to the following: #device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # /dev/dsk/c0t3d0s0 /dev/rdsk/c0t3d0s0 / ufs Patch 121431-58 has been successfully installed. Join Now For immediate help use Live now!
When at the prompt # mount /dev/dsk/c0t0d0s0 /a # cd /a/etc If using a monitor # TERM=sun;export TERM If using a terminal # TERM=vt100;export TERM # ls -l vfstab* - Check Old habits die hard. lucreate(1M) and the new (Solaris 10 10/09 and later) autoregistration file This one is actually mentioned in the Oracle Solaris 9/10 release notes. These problems can arise either through hardware failures or operator error.