Hallo together,
I have a litle problem with some of my external devices.
If I type mount there are some "panic" massages.
Is this a real mistake or is this a normal behavior of a Solaris 8 system ?
/export/jumpstart on /dev/dsk/c5t4d0s7 read/write/setuid/intr/largefiles/onerror... (4 Replies)
please help me about unixware 7.1.3
--------------------------------------------------------------------------------
msg:
vfs_mountroot:cannot mount root
%%%%%%
system don't start (1 Reply)
Presently I have mounted a disk as su. I believe only root can mount disks -- is this correct?
I had to run mozilla in the root account so I can download the new SuSE distribution to the new disk.
How can I mount the disk so non-root accounts can access the disk?
Thanks,
Siegfried (4 Replies)
I have a USB disk on a little NAS controller (NSLU2 running unslung 6.8) that I can access nicely with root with
mount -t cifs \\\\10.134.23.23\\DISK\ 2 /mnt/LKGD7F73A
However, when I run emacs from an user mode xterm prompt, emacs cannot read and write the files on /mnt/LKGD7F73A. Emacs can... (11 Replies)
Is it possible to mount a disk from a non-root account?
I'm developing a Java application which executes commands in the shell using the java.lang.Runtime.exec api, which runs fine for commands ls, df, etc., but for commands mount and umount, i have problems as I need to be root to eecute these.... (8 Replies)
i have a major problem, i renamed the ld.so.1 file.
so i want to reboot into single user mode / fail safe / cdrom single user but i will not mount the root disk.
if i look in /dev/dsk all i see is ide disks (cdrom) and no actual disks. (2 Replies)
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13:
F13, F12 & F11 Nvidia driver guides - FedoraForum.org
Here's the tutorial:
And this is what I did:
First I executed the following commands:
su
rpm -Uvh ... (0 Replies)
I see the following warning message during the boot sequence of any FreeBSD machine on stock hardware:
acd0: FAILURE: READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
Trying to mount root from ufs:/dev/ad6s1
What does this mean and is it really a warning or something that should be fixed?
... (2 Replies)
I have a Debian OpenBox that boots from any usb port. The Debian LXDE will only boot from one specific port. It needs to look at all of them to find and be root, and mount the root filesystem by UUID. Both are full installs to 16GB flash drives.
That is not being done.
It says during boot... (0 Replies)
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
LEARN ABOUT SUNOS
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)