09-17-2001
update
i've been on HP's site for weeks awaiting any new drivers, unfortunately this server is still being tested by red hat from what i understand, I did install the newer netraid drivers and was hoping this would fix it but it didn't. I'm basically always getting the root to lock up no matter what i log in with (gnome, kde) then once i kill it, i get those errors requiring me to use the fsck command. once i login as root the very first time, its fine, its after that 2nd reboot is where it locks. thanks for the info.
Lyghtnin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a SCO Openserver 5.0.5 server running RAID5 on the hp NETRAID-1M controller and it works just fine.
However, I cannot add a tape drive in. The standard SCSI card is a Symbios and I am using the 'slha' driver, but the system doesnt see the adaptor at SCO startup. The adaptor and... (1 Reply)
Discussion started by: christate
1 Replies
2. Shell Programming and Scripting
Hi ,
Could u please tell me What is lpr -P ?
Regards
Ashish Malviya:) (2 Replies)
Discussion started by: Ashishm
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
Can anybody tell me how to configure my printer to handle lpr -o landscape? Or what I need to do to print a text file in landscape format using the lpr command.
Thanks
Monique (1 Reply)
Discussion started by: squeakywheel
1 Replies
4. UNIX for Dummies Questions & Answers
good day!
i would just like to ask for advice regarding an lp problem i have..
we currently migrated a GIS appl from sol 2.6 to sol 8 but maintained the same version of jetadmin (for the appl plotters and printers). we are able to print files on a printer but not on a plotter. the... (1 Reply)
Discussion started by: maria_iris
1 Replies
5. UNIX for Advanced & Expert Users
--------------------------------------------------------------------------------
I tried to install SCO Open Server on HP2000 U3
drivers is amrid,
at install of SCO unnix only recognize non hot plugged devices
I have 2 HD of 40 GO under ID 0 and 1 but unix does not see them at boot ?? (0 Replies)
Discussion started by: Bernardschmitt
0 Replies
6. UNIX for Dummies Questions & Answers
I tried to install SCO Open Server on HP2000 U3
drivers is amrid,
at install of SCO unnix only recognize non hot plugged devices
I have 2 HD of 40 GO under ID 0 and 1 but unix does not see them at boot ?? (1 Reply)
Discussion started by: Bernardschmitt
1 Replies
7. UNIX for Dummies Questions & Answers
This server had an HP C1555 tape drive that appears to have gone belly up. We found a replacement, an HP C1537, that we want to install. We did the hardware thing, with power off, of course, but when the box was rebooted it did not seem to recognize the drive. At least the backup software did... (4 Replies)
Discussion started by: akirson
4 Replies
8. Red Hat
Dear experts,
Can any one suggest, whether RHEL is supported in HP NetServer LH6000 U3
Thanks (2 Replies)
Discussion started by: ./hari.sh
2 Replies
9. Shell Programming and Scripting
Hi Guys,
I am using the following command in unix for printing.
pr -t -l34 "$1" | lpr -r
But i was not able to see the file getting deleted. Is anything wrong with the command.
---------- Post updated at 10:56 AM ---------- Previous update was at 10:38 AM ----------
Hi... (0 Replies)
Discussion started by: Kar1234
0 Replies
10. UNIX for Beginners Questions & Answers
Hi ,
We are trying to automate Printing the word document directly from the Server level to a Printer.
We have printer registered and command I use is
lp -d printername 1234.doc
Even though the program completes fine, a print does not reach to the printer for word document. In... (4 Replies)
Discussion started by: PrashantTalele
4 Replies
LEARN ABOUT SUSE
fsck.minix
FSCK(8) Linux Programmer's Manual FSCK(8)
NAME
fsck.minix - a file system consistency checker for Linux
SYNOPSIS
fsck.minix [-larvsmf] device
DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem. The current version supports the 14 character and 30 character
filename options.
The program assumes the file system is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ-
ing to it (and remember that the kernel can write to it when it searches for files).
The device will usually have the following form:
/dev/hda[1-63] (IDE disk 1)
/dev/hdb[1-63] (IDE disk 2)
/dev/sda[1-15] (SCSI disk 1)
/dev/sdb[1-15] (SCSI disk 2)
If the file system was changed (i.e., repaired), then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
exiting. Since Linux does not currently have raw devices, there is no need to reboot at this time.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility
that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a
mounted filesystem (i.e., the root filesystem), make sure nothing is writing to the disk, and that no files are "zombies" waiting for dele-
tion.
OPTIONS
-l Lists all filenames
-r Performs interactive repairs
-a Performs automatic repairs (this option implies -r), and serves to answer all of the questions asked with the default. Note that
this can be extremely dangerous in the case of extensive file system damage.
-v Verbose
-s Outputs super-block information
-m Activates MINIX-like "mode not cleared" warnings
-f Force file system check even if the file system was marked as valid (this marking is done by the kernel when the file system is
unmounted).
SEE ALSO
fsck(8), fsck.ext(8), fsck.ext2(8), fsck.xiafs(8), mkfs(8), mkfs.minix(8), mkfs.ext(8), mkfs.ext2(8), mkfs.xiafs(8), reboot(8)
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX file system,
fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
0 No errors
3 File system errors corrected, system should be rebooted if file system was mounted
4 File system errors left uncorrected
8 Operational error
16 Usage or syntax error
In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be returned.
AUTHOR
Linus Torvalds (torvalds@cs.helsinki.fi)
Error code values by Rik Faith (faith@cs.unc.edu)
Added support for file system valid flag: Dr. Wettstein (greg%wind.uucp@plains.nodak.edu)
Check to prevent fsck of mounted filesystem added by Daniel Quinlan (quinlan@yggdrasil.com)
Minix v2 fs support by Andreas Schwab (schwab@issan.informatik.uni-dortmund.de), updated by Nicolai Langfeldt (janl@math.uio.no)
Portability patch by Russell King (rmk@ecs.soton.ac.uk).
AVAILABILITY
The fsck.minix command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
Util-Linux 2.6 2 July 1996 FSCK(8)