07-01-2015
Quote:
Acquire a single disk, install it, and create a new RAID0 configuration.
Install 7.1.4, and in this process create the same file system names as on the original. The actual size of the file systems does not matter.
Create an emergency boot cd, or download and install Microlite Edge (microlite.com) and create their recovery CD.
Remove the single hard drive and replace with the RAID5 configuration.
Boot from the newly made recovery cd, and run fsck on the root file system and the stand file system.
Hi jgt, I have done above as suggested so now I have the RAID5 system booted with an emergency boot cd...
But I am not sure how to proceed.
I have tried to fsck the root filesystem but there isn't a vfstab on the system so I get an error.
I have tried running an fsck (the VXFS version) on all the devices in /dev/rdsk but that just resulted in an error from most of them.
So I am now unsure what steps to take to troubleshoot the original issue?
I can recreate the vfstab to be the same as the vanilla install I did on a single disk from which I created the emergency cd. Would that help??
10 More Discussions You Might Find Interesting
1. Programming
dear all ,
iam trying to compile a progam using gcc compiler on a sun 280 R machine running solaris 9 .
iam getting an error in the last step when the compiler tries to link the objects , although the compiler executes some applicarions that contains no objects smoothly,
the error that... (1 Reply)
Discussion started by: ppass
1 Replies
2. UNIX for Dummies Questions & Answers
Hi
i have both Linux and Windows XP on my PC.
i used to use grub as a boot loader and everything was perfect, until
i reinstalled Windows.
apparently, Windows installer installed its own bootloader, that
doesn't recognize Linux.
i tried using a tool called GrubInstaller for Windows, and now... (4 Replies)
Discussion started by: shx2
4 Replies
3. Programming
Hi,
I just pulled out my code from source control, then I compiled, the compilation is successful at that time.
Then I modified one of the source file, Then I compiled, I got the following error
ld: fatal: Symbol referencing errors. No output written to ../../CM/bin/cato
Before... (1 Reply)
Discussion started by: sarwan
1 Replies
4. UNIX for Dummies Questions & Answers
zero experience Unix user here. Cannot boot our Sparc10.
Running:
SunOS release 5.3 Version Generic_Patch
message says:
(Can't load swapgeneric)
Program terminated
Tried to 'boot -s' , but this looks like a problem w/ Generic_Patch maybe?
At bootup, the devices come up fine and it... (0 Replies)
Discussion started by: man_of_action
0 Replies
5. Solaris
I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed".
Why does this happen?
I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies
6. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
7. Solaris
This is the error message that I am getting on a Solaris 10 sparc server
scsi: no major number
cannot load drivers for /pci@400.....
Can't load the root filesystem
Type 'go' to resume
{0} ok
Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up... (5 Replies)
Discussion started by: trinityforce
5 Replies
8. Solaris
Dear all,
I Need your help,my server v240 with sun solaris 10 can't remote login.I try conncet via rsc and then go to OK prom....and i get the status :
{1} ok boot -a
FATAL: system is not bootable, boot command is disabled
{1} ok boot cdrom -s
FATAL: system is not bootable, boot command is... (2 Replies)
Discussion started by: fredginting
2 Replies
9. Solaris
I have M10-1. Installation OS 10 from cdrom external.
Here message from OK Prompt
{0} ok probe-scsi-all
/pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1
Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00
But..
{0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies
10. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT MOJAVE
systemd-fsck
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)
NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but
only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root
file system in the initramfs.
These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
rotating disk.
systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
mounts, unclean unmount, etc.
If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
fsck.repair=
One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.
SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)
systemd 237 SYSTEMD-FSCK@.SERVICE(8)