07-08-2008
s/w errors are not disk errors. If HDD needs replacement, you will know by lookingat the iostat -En output. Hard Errors and Transport Errors can tell you if your disk is gone bad. Soft errors are not critical and the counter can be resetted via a reboot. But hard errors will be incrementing if its really critical
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
When I came officce this morning I saw this error messages on the screen
-----
PANIC:srmountfun - Error 6 mounting rootdev hd (1/42)
Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages
Dump not completed
--------
and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies
2. UNIX for Advanced & Expert Users
I've got htis message on our sun U60 machine:
"Reboot after panic:errID 0x000004eff........." ,this message have been issued on the /var/adm/messages file & cause system rebooting randomly.
Any comment.
Thanks,
--Nikk (1 Reply)
Discussion started by: nikk
1 Replies
3. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
4. HP-UX
Hi all,
Does anybody know what kinds of events can prompt the following?
I found our test db box had rebooted itself. I'd like to know how I can go about finding our why. Thanks folks... (1 Reply)
Discussion started by: Kozmo
1 Replies
5. AIX
Hi,
Is there an option to disable saving of system dump when a user invokes a kernel panic
using sysdumpstart command.
Also, is there any other way of invoking a kernel panic other than using
sysdumpstart?
Thanks,
Kanna (3 Replies)
Discussion started by: kanna_geekworkz
3 Replies
6. Solaris
Hi All,
I have installed Solaris 10 on my AMD 64 3000+ system. I was playing with grub commands eeprom and bootadm commands. I screwed my boot-file and now am unable to boot the system. Gets error msg as "panic: cannot open /kernel/amd64/unix". I booted the system is filesafe and tried update the... (2 Replies)
Discussion started by: Manjunath K V
2 Replies
7. Red Hat
Hi,
I am experiencing frequent system hangs, hard kernel panics, etc almost thrice a day. The system would be totally unresponsive and the only way is to reboot is hard power recycling (plug out the power cable and plug in back after 30 secs). I enabled kdump, but unfortunately the kdump files... (3 Replies)
Discussion started by: massoo
3 Replies
8. HP-UX
Hello
I have some hpux 11.23/31 systems ,and some other (linux,solaris)
I know if i want change the mtu size ,need use lanadmin.
But:if i try on 11.23 : ifconfig lan1 mtu 8000,system paniced.
If i try on 11.31 :ifconfig lan1 mtu 8000,remove ip address from interface.
Ithink is not a best... (1 Reply)
Discussion started by: zoldkalap
1 Replies
9. Linux
Hi All,
Yesterday my Linux server went panic and even a small command took a lot of time to run.
When i monitored pl find the below output
Cpu(s): 0.1%us, 98.4%sy, 0.0%ni, 1.5%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
the time spent on kernel mode is 98 % and also idle time is around 1.5 %...... (4 Replies)
Discussion started by: jegaraman
4 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT LINUX
mkfs.minix
MKFS.MINIX(8) Linux System Administrator's Manual MKFS.MINIX(8)
NAME
mkfs.minix - make a Linux MINIX filesystem
SYNOPSIS
mkfs.minix [-c|-l filename] [-n namelength] [-i inodecount] [-v] device [size-in-blocks]
DESCRIPTION
mkfs.minix creates a Linux MINIX file-system on a device (usually a disk partition).
The device is usually of the following form:
/dev/hda[1-8] (IDE disk 1)
/dev/hdb[1-8] (IDE disk 2)
/dev/sda[1-8] (SCSI disk 1)
/dev/sdb[1-8] (SCSI disk 2)
The size-in-blocks parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omit-
ted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.
OPTIONS
-c Check the device for bad blocks before creating the file system. If any are found, the count is printed.
-n namelength
Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30. The default is 30. Note that kernels
older than 0.99p7 only accept namelength 14.
-i inodecount
Specify the number of inodes for the filesystem.
-l filename
Read the bad blocks list from filename. The file has one bad block number per line. The count of bad blocks read is printed.
-v Make a Minix version 2 filesystem.
EXIT CODES
The exit code returned by mkfs.minix is one of the following:
0 No errors
8 Operational error
16 Usage or syntax error
SEE ALSO
mkfs(8), fsck(8), reboot(8)
AVAILABILITY
The mkfs.minix command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
Util-linux 2.6 2 July 1996 MKFS.MINIX(8)