Sponsored Content
Full Discussion: Boot CD for DD command
Special Forums Hardware Filesystems, Disks and Memory Boot CD for DD command Post 30791 by nicolascure on Monday 28th of October 2002 06:40:30 AM
Old 10-28-2002
Thanks for your reply. I tried ClosedBSD. I downloaded the ISO image and booted it up. Apperently the DD command is not available. It gives me a message "crunch: dd not compiled in". I have no idea where to go from here. If anyone has any comments I'd appreciate it.

I'll be looking into your other suggestions to see if I have better luck.


Thanks
Nicolas

Last edited by nicolascure; 10-28-2002 at 10:32 AM..
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

3. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

4. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

5. Solaris

Solaris 10 init 0 and boot disk1 on same command line

Hello all, Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
Discussion started by: tording99z28
2 Replies

6. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

7. Solaris

After command setenv auto-boot false machine's console not displaying

hi Alll, I want to install solaris 10 on exixting solaris mahcine. I tried for OK boot cdrom-install but it gave me fatal error - disk not bootable , boot command disable so i tried with ok setenv auto-boot? false Ok reset-all after this server rebooted automatically and... (2 Replies)
Discussion started by: sunray
2 Replies

8. Solaris

FATAL: system is not bootable, boot command is disabled

Dear all, I Need your help,my server v240 with sun solaris 10 can't remote login.I try conncet via rsc and then go to OK prom....and i get the status : {1} ok boot -a FATAL: system is not bootable, boot command is disabled {1} ok boot cdrom -s FATAL: system is not bootable, boot command is... (2 Replies)
Discussion started by: fredginting
2 Replies
kdump-config(8) 					Linux System Administrator's Manual					   kdump-config(8)

NAME
kdump-config - configure kdump, check status, or save a vmcore file SYNOPSIS
kdump-config { help | test | show | status | load | unload | savecore } DESCRIPTION
kdump-config manages the kdump feature of the Linux kernel. When a kdump enabled kernel panics, it immediately boots into a clean kernel called the kdump kernel. The memory image of the panicked kernel will be presented in /proc/vmcore while the kdump kernel (or "capture kernel") is running. kdump-config loads the kdump kernel into the current kernel and after a kdump, captures the vmcore image via kdump kernel. kdump-config can take advantage of the linux-image-$(uname -r)-dbg package and will try to use makedumpfile to capture the vmcore. The crash tool can then be used to analyze the vmcore at a later time. kdump-config exits with 0 on success and 1 on failure. COMMANDS
help Print a usage summary. test Determine the parameters that would be used to load the kdump kernel, but do not load the kdump kernel. Useful for evaluating your configuration settings. show Show current parameters and the saved kexec command from the last kdump-config load. status Evaluate /sys/kernel/kexec_crash_loaded and print a corresponding message. load Load the kdump kernel. unload Unload the kdump kernel. savecore If /proc/vmcore exists, save it using makedumpfile. FILES
/etc/init.d/kdump-tools init script to automatically load a kdump kernel, or save a vmcore and reboot. /etc/default/kdump-tools configuration file /var/crash/kernel_link a link to the current debug kernel /var/crash/kexec_cmd the last kexec_cmd executed by kdump-config DIAGNOSTICS
USE_KDUMP is not set or zero The variable USE_KDUMP in the file /etc/default/kdump-tools is 0. To use kdump, edit the file and change the value to 1. kdump is not supported by this kernel The file /sys/kernel/kexec_crash_loaded does not exist. This means that the currently running kernel either was not configured to support kdump, or that a crashkernel= commandline parameter was not used when the currently running kernel booted. no crashkernel= parameter in the kernel cmdline a crashkernel= commandline parameter was not used when the currently running kernel booted. You will need to add a crashkernel= parameter to your /etc/lilo.conf, /etc/elilo.conf or grub /boot/grub/menu.lst file and reboot, before kdump will work. See installed READMEs for suggestions. could not find an installed debug vmlinux image and DEBUG_KERNEL is not specified in /etc/default/kdump-tools Warning: makedumpfile will be limited to -d 1. A debug version of the currently booted kernel could not be found. KDUMP_KERNEL does not exist: $KDUMP_KERNEL A KDUMP_KERNEL was specified in /etc/default/kdump-tools, but it cannot be found. KDUMP_INITRD does not exist: $KDUMP_INITRD A KDUMP_INITRD was specified in /etc/default/kdump-tools, but it cannot be found. no KDUMP_KERNEL in $KDUMP_DEFAULTS and can't find a kdump package directory in /usr/lib no kdump kernel could be found. found a linux-kdump package in $KDUMP_PKG_DIR but can't find a kdump kernel in $KDUMP_PKG_DIR this indicates a broken linux-kdump package installation. no kdump initrd image: $KDUMP_INITRD an initrd will not be used this indicates that although a kdump kernel was found, a corresponding initrd was not found. kdump kernel relocation address does not match crashkernel= parameter For non-relocatable architectures, the kdump kernel must be built with a predetermined start address. This message indicates that the start address of the kdump kernel and the start address in the crashkernel= parameter do not match. failed to load kdump kernel kexec reported that it could not load the kdump kernel. failed to unload kdump kernel kexec reported that it could not unload the kdump kernel. Run 'kexec -u' directly for more detail. makedumpfile failed, falling back to 'cp' this message is printed if the kdump-tools init script attempts to save a /proc/vmcore file using makedumpfile and the save fails. failed to save vmcore in $KDUMP_STAMPDIR this message indicates that makedumpfile and the fallback method of using cp has failed. This usually occurs if pathnames are wrong or if the disk is full. SEE ALSO
/usr/share/doc/kdump-tools/README /usr/share/doc/kdump-tools/README.Debian kdump-tools(5), kexec(8), crash(8), gdb(1), makedumpfile(8) AUTHOR
Terry Loftin <terry.loftin@hp.com> kdump-tools v1.1.3 April 2007 kdump-config(8)
All times are GMT -4. The time now is 03:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy