Sponsored Content
Full Discussion: Ufsrestore on SunBlade 2500
Top Forums UNIX for Beginners Questions & Answers Ufsrestore on SunBlade 2500 Post 303011666 by hicksd8 on Monday 22nd of January 2018 09:10:22 AM
Old 01-22-2018
You have one of two scenarios.

The /var is either (a) a separate filesystem (which you will have dumped separately from the original system), or (b) it is not separate and is therefore included in the root filesystem.

If it is (a) then when you boot from DVD and mount your hard disk root filesystem under /a, when you look in /a/var it will be empty since the other /var slice will be mounted here. Also, in this case, there will be an entry in /a/etc/vfstab to mount this other slice under /var at boot time.

If it is (b) then when you boot from DVD and mount your hard disk root filesystem under /a, when you look in /a/var the normal files will be in there. Also, there will be no entry in /a/etc/vfstab to mount anything on /var.

If you have checked everything is in order for (a) or (b) and the system still won't boot correctly, then recreate the device nodes for all disks using 'devfsadm' as described previously.
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. Linux Benchmarks

AMD 2500 / 1G RAM / Soyo KT600 Ultra MB

System Notes: CPU/Speed: AMD Athlon 2500+ 1.8Ghz Ram: 1 GB DDR 333 PC2700 Motherboard: Soyo KT600 Dragon Ultra Bus: PCI Cache: 512KB (corrected earlier error stating 512MB!) HD Controller: EIDE Benchmarks: ... (5 Replies)
Discussion started by: Neo
5 Replies

2. Solaris

Anyone has problems with new Blade 2500????

Hi guys, I am a new member here. This is my first post. I try to purchase some new Blade 2500 for the company. However, the vendor suggests me to get Blade 2000 instead. The vendor said he has many problems with new Silver Blade 2500's. Has anyone here had simlar experience with blade 2500?... (4 Replies)
Discussion started by: facaizhu
4 Replies

3. Filesystems, Disks and Memory

SB2000, 2500 server client convert

Hi, Sir, I have a customer who use a SB2000 as server and just upgraded three client machine with SB2500. The system is used for planning and all boxes likely share the same source on server, so pretty slow when all machines are in operation. The customer wish to do a server-to-client and... (0 Replies)
Discussion started by: howhowzz
0 Replies

4. UNIX for Dummies Questions & Answers

Sunblade 1000

Hi everyone this is my first post I have used linux a couple of times and was impressed, so i bought an old sunblade 1000, just to learn something new. I cannot get the thing to work! I have tried to install solaris 10 and several types of linux. I am beginning to wonder if i was sold a... (3 Replies)
Discussion started by: Kawakaze
3 Replies

5. What is on Your Mind?

Now Over 2500 FB Fans for Our New Timeline

Progress! 25% there on our way 10,000 FB fans on the new timeline: https://www.unix.com/members/neo-albums-forum-pics-picture503-facebook-timeline-now-over-2-500-fans.png (0 Replies)
Discussion started by: Neo
0 Replies

6. Hardware

StorageTek 2500

Hi, I recently got StoragaTek 2500 and I would like to connect it to my solaris machine, since I don't have much experience with storages, could someone point me how to do so, how can i present disks from storage on my solaris os? (everything is already connected) thanks in advance (1 Reply)
Discussion started by: sprehodec
1 Replies

7. BSD

Installing OpenBSD for Xorg on Sunblade 2500

Hello All, I am new to the forum so forgive me for any mistakes. I have a question. I have been doing alot of reading about how to get a supportable operating system on my sunblade 2500. I also want to use it for Xorg. I have been having trouble getting the sun XVR drivers working... (2 Replies)
Discussion started by: harqobi22
2 Replies

8. UNIX for Beginners Questions & Answers

Need in for a script that should check for errors in multiple log file (approx 2500) and should mail

hello everyone, I am new to linux and got this deliverable to write a script that should check for error in multiple log file (count is approx 2500 log files on single server) and once error is found, it should mail that error My logic says: we can put all log files path/location in one... (2 Replies)
Discussion started by: Pratik_CTS
2 Replies

9. Solaris

Cloning a Sunblade 2500

Good Morning, I took a mirror drive from one Solaris 9 machine and used it to set up another. After syncing another mirror on the second machine I restarted but I don't get a login screen. I see a message:The X-server cannot be started on display :0 Also during startup I see:... (8 Replies)
Discussion started by: Stellaman1977
8 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 03:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy