Sponsored Content
Full Discussion: Update Solaris from 8 to 10
Operating Systems Solaris Update Solaris from 8 to 10 Post 302394233 by SmartAntz on Wednesday 10th of February 2010 11:18:01 PM
Old 02-11-2010
=)

the problem is when i boot cdrom, when proceed to half, it come out the error say update fail, could not mount the root, swap, and other filesystem.

and i suspect is when i run the # format
in single usermode, and normal mode, the output is different.

any idea?
 

10 More Discussions You Might Find Interesting

1. Solaris

How to update patches to Solaris 10?

I am seeking help to add patches to Solaris 10 on 64 bit Sparc server. This is to prepare the server for the installation of Oracle 10g. Please list command and specific directory that patches should be added to. Thanks (4 Replies)
Discussion started by: duke0001
4 Replies

2. Solaris

How update Solaris ?

I have Solaris 10 01/06 version on my server, but i wanna update her from my DVD-Disc to 08/07. How i can do it ? I has try boot from disc, but don't find Upgrade function =( Please help me anyone! (1 Reply)
Discussion started by: jess_t03
1 Replies

3. Solaris

update openshh on solaris 10

Hi All, I've downloaded and extracted openssh4.1 on solaris 10. When I run the install-sh, it replied with "./install-sh: no input file specified". The file is executable and been move to owner root or the rest of the files. Why is that? Please help. Thanks in advance, itik (4 Replies)
Discussion started by: itik
4 Replies

4. Solaris

Undo the Veritas mirroring and update from Solaris 8 to Solaris 10

Hi all I wish to undo the mirroring for root and update the Solaris version from 8 to 10. Since i am lack of knowledge and experience on this, hope you all can help me double check the step and correct me. Existing disk groups details root@leo # vxdg list NAME STATE ID... (3 Replies)
Discussion started by: SmartAntz
3 Replies

5. Solaris

Update Solaris patch

Hi All I had update the solaris version, and now wish to update the patch. but when i check my patch version, i cant find any version for that. any idea? root@leo # showrev Hostname: leo Hostid: 839b58a3 Release: 5.10 Kernel architecture: sun4u Application architecture: sparc... (8 Replies)
Discussion started by: SmartAntz
8 Replies

6. Solaris

Solaris Update 2 to 7

I need to get from Solaris 10 update 2 to update 7, whats the quickest way just apply kernel patch or live upgrade? If it is just kernel patching can i go straight from update 2 to 7 or do I have to apply each revision level patch i.e. go from update 2 to 3 to 4 etc... (2 Replies)
Discussion started by: mr_crosby
2 Replies

7. Solaris

Install update 6 on solaris with update 3

I want to update my solaris 10 server which is currently on update 3 stage. A new application require it to be on update 6. What is the best way to make it update 6. should i just install the patch or should i go for the liveupgrade?? thanks for you help in advance (3 Replies)
Discussion started by: uxravi
3 Replies

8. Solaris

Solaris 11 to 11.1 update help

If anyone has any solid documents on updating Solaris 11.0 to 11.1 please share. I have been spinning my wheels for day now. I got past running the pre-update step. Rebooted the system and trying to continue with update to 11.1 using IPS repo and keeps failing with message that it can't reach... (5 Replies)
Discussion started by: fly3rs
5 Replies

9. Solaris

Solaris Repo Update

Hi Folks, Just a quick question on this, I've tried to run this a couple of times now - first time it failed I increased the swap. I'm not sure that increasing the physical memory will do any good, but will try later today - has anyone seen this or anything similar? SunOS fvssphsun01 5.11... (8 Replies)
Discussion started by: gull04
8 Replies

10. Solaris

How to update Solaris 10 Update 3 to Update 11?

Hi friends, We have a Solaris machine running 10 update 3 -bash-3.2# cat /etc/release Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. ... (6 Replies)
Discussion started by: prvnrk
6 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 11:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy