Sponsored Content
Full Discussion: kernerl corrupted
Operating Systems SCO kernerl corrupted Post 40850 by RTM on Wednesday 24th of September 2003 10:09:54 AM
Old 09-24-2003
You might try looking at PCUNIX.com - SCO FAQ

I searched for corrupt boot and found the following and more:

Quote:
Sco boot from older kernel: at boot prompt just type "unix.old"- type "dir" to see available kernels
 

9 More Discussions You Might Find Interesting

1. AIX

LV corrupted

I'm getting the following error after we replaced a failed disk in a mirrored logical volume. We cleared the device entry in ODM before adding the new disk but when we create the mirror we get the following error after running lslv. 0516-022 lslv: Illegal parameter or structure value.... (1 Reply)
Discussion started by: Alfredo Jimenez
1 Replies

2. HP-UX

Could be a corrupted file?

Hello! Do you know the meaning of... "crw-rw---- 1 informix informix 64 0x020001 Jan 21 2004 rifxroot" I don't know what the first "c" means. Furthermor, if I try to copy this file (rifxroot) it appears a message: "cp: cannot open rifxroot: No such device or address" I don't... (1 Reply)
Discussion started by: kaugrs
1 Replies

3. Red Hat

Corrupted Hard Drive

I am running FC-7 which I realize is an older distro. But my question would apply to any distro. I ran fsck on my mounted file system (I know, I shouldn't have). Now it won't boot. I get a kernel panic message. I booted to a Knoppix Live Cd. The desktop icon shows /dev/sda2 mounted at... (4 Replies)
Discussion started by: 2buck56
4 Replies

4. Emergency UNIX and Linux Support

/etc/name_to_sysnum corrupted

Hi all , i have an issue in netra 20 server when i boot the system its getting rebooting and it is giving tha" /etc/name_to_sysnum " file not found i done OK> boot -ar then also not solved please can any body send the answer ASAP regards (3 Replies)
Discussion started by: wkbn86
3 Replies

5. Solaris

corrupted motherboard

hi i have a sun server V890 and i added two cpu/memory modules to it but it caused the motherboard to become corrupted could you please help me find what causes this problem and how to avoid it because i changed the corrupted motherboard and i want to do the expansion and I'm scared that ... (2 Replies)
Discussion started by: bahjatm
2 Replies

6. Shell Programming and Scripting

cronjob corrupted

dear all , i was trying to run a cron as root , something happened because it displayed "/tmp/crontabC5a4lB" 14 lines, 495 characters cron may not be running - call your system administrator does anyone knows the problems? thanks ---------- Post updated at 01:05 PM... (2 Replies)
Discussion started by: semaan
2 Replies

7. Solaris

solaris 10 corrupted repository.db

Recently had a SAN issue which somehow resulted in my repository.db getting corrupted. I tried using the restore_repository script as suggested by the OS. This did not work due to / being in read only. Per instructions I ran /lib/svc/method/fs-root. This seemed to work. Now on to... (3 Replies)
Discussion started by: KSFlyer
3 Replies

8. UNIX for Dummies Questions & Answers

Passwd Utility Corrupted

I have a legacy Solaris 8 machine. Someone has overwitten the passwd utility so I now can't change passwords. Is there somwhere I can download a copy? I do have the installation CDs as well. Thanks (1 Reply)
Discussion started by: hawess
1 Replies

9. Hardware

Files getting corrupted

$ uname -a Linux darksun 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:45 UTC 2014 i686 athlon i686 GNU/Linux My files are getting corrupted on a frequent basis. $ sudo fdisk -l /dev/sda Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total... (10 Replies)
Discussion started by: rlopes
10 Replies
GPTZFSBOOT(8)						    BSD System Manager's Manual 					     GPTZFSBOOT(8)

NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a GPT-partitioned disk with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less. BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is used as a default boot pool. The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is present in the boot filesystem, boot options are read from it in the same way as boot(8). The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables. USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports. The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is [zfs:pool/filesystem:][/path/to/loader] Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and filesystem are specified, then /boot/zfsloader is used as a path. Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool status (see zpool(8)). The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial value of the currdev variable. FILES
/boot/gptzfsboot boot code binary /boot.config parameters for the boot block (optional) /boot/config alternative parameters for the boot block (optional) EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gptzfsboot can also be installed without the PMBR: gpart bootcode -p /boot/gptzfsboot -i 1 ada0 SEE ALSO
boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8) HISTORY
gptzfsboot appeared in FreeBSD 7.3. AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>. BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off- sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen. BSD
September 15, 2014 BSD
All times are GMT -4. The time now is 08:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy