02-16-2009
Hello,
When you start to see this sort of errors it means most likely that the hard drive is dying.
Some part of the disk has lost informations and sco could NOT recover it.
I would sugest you to relpace that drive.
another possibility is with a drive array with the write back cache enabled is the battery on the controler is dead and the controler lost/corrupted part of the info before comiting it to the drive.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
HELP is urgently required,
I run on SCO Unix 3 and this is the panic message that I get every time that I reboot 10U
k_trap - kernel mode trap type 0x0000000E
I have checked the swap already having the following results:
#swap -l
path dev swaplo blocks free... (3 Replies)
Discussion started by: alex_slb
3 Replies
2. UNIX for Dummies Questions & Answers
I've installed rh 7.3 a fewday ago and I'm trying to boot it and I get this" Kernel panic: no init found. try passing init=options to kernel" ????? What do I do.
Thanks.
F,Ruiz. (2 Replies)
Discussion started by: ruizf
2 Replies
3. UNIX for Dummies Questions & Answers
hello :-)
I have one problem with my LiLO... I installed PLD Linux on my computer but when it boots, the last thing I can see is:
request_module Root fs not mounted
VFS: Cannot open root device 03:01
Kernel panic: VFS: unable to mount root fs on 03:01
and the system stops :-(
what... (1 Reply)
Discussion started by: pgas
1 Replies
4. SCO
hi,
I am trying to install sco openserver 5.0.4 on an old system. However, l was not able to proceed after putting the bootstr
l have this panic message of
PANIC: K_trap - kernel mode trap tupe 0x00000006
will someone kindly help to decode this error
kayode (1 Reply)
Discussion started by: kayode
1 Replies
5. Linux
I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies
6. Solaris
One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly?
Thanks
Margaret Floyd
Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies
7. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
8. SCO
hi
I've virtualized physical SCO 5.0.6 on ESX 4 according to:
Blog du DS45: HOWTO SCO P2V in the real life
SCO starts with the network, but during shutdown I'm getting this message:
PANIC: k_trap.
My /etc/default/boot:
# cat /etc/default/boot
#ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies
9. SCO
I shutdown my sco 5.0.7 machine about a month and a half ago and upon bringing it back up got the following kernel panic:
Panic: k_trap - Kernel mode trap type0x0000000E
Unable to freeze processor 2, proceeding....
Cannot dump ?????? pages (I don't remember how many pages it was)
Dump not... (0 Replies)
Discussion started by: powwm
0 Replies
10. UNIX for Advanced & Expert Users
Hi, all:
How should I obtain the reason of kernel panic?
How should I debug the program which result in a kernel panic?
What can I get from the panic information?
li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies
LEARN ABOUT DEBIAN
diskseekd
diskseekd(1) General Commands Manual diskseekd(1)
Name
diskseek, diskseekd - disk seek daemon; simulates Messy Dos' drive cleaning effect
Note
This manpage has been automatically generated from fdutils's texinfo documentation. However, this process is only approximative, and some
items, such as cross-references, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate rep-
resentation in the manpage format. Moreover, only the items specific to each command have been translated, and the general information
about fdutils has been dropped in the manpage version. Thus I strongly advise you to use the original texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips fdutils.dvi
* To generate a HTML copy, run:
./configure; make html
A pre-made HTML can be found at: `http://www.tux.org/pub/knaff/fdutils'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as HTML. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
Description
Several people have noticed that Linux has a bad tendency of killing floppy drives. These failures remained completely mysterious, until
somebody noticed that they were due to huge layers of dust accumulating in the floppy drives. This cannot happen under Messy Dos, because
this excuse for an operating system is so unstable that it crashes roughly every 20 minutes (actually less if you are running Windows).
When rebooting, the BIOS seeks the drive, and by doing this, it shakes the dust out of the drive mechanism. diskseekd simulates this effect
by seeking the drive periodically. If it is called as diskseek, the drive is sought only once.
Options
The syntax for diskseekd is as follows:
diskseekd [-d drive] [-i interval] [-p pidfile]
-d drive
Selects the drive to seek. By default, drive 0 (`/dev/fd0') is sought.
-i interval
Selects the cleaning interval, in seconds. If the interval is 0, a single seek is done. This is useful when calling diskseek from a
crontab. The default is 1000 seconds (about 16 minutes) for diskseekd and 0 for diskseek.
-p pidfile
Stores the process id of the diskseekd daemon into pidfile instead of the default `/var/run/diskseekd.pid'.
Bugs
1. Other aspects of Messy Dos' flakiness are not simulated.
2. This section lacks a few smileys.
See Also
Fdutils' texinfo doc
fdutils-5.5 03Mar05 diskseekd(1)