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
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
chown(1), mknod(1), sd(4), mount(8)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 HD(4)