However, since installation, the system no longer boots. I've tried appending the above parameters to the kernel line in grub, but is still doesn't boot.
It starts to boot, and everything looks fine, until it tries to remount the root fs in read/write mode, at which point it appears to hang.
There are several messages on screen, all of which are normal, except two instances of the following:
Code:
hdc: status error: status = 0x58
NOTE: For some reason, the two hard drives were picked up as hdc and hde, but it seemed to install OK.
If i boot up into rescue mode on the installation CD, i can mount the drives fine, and chroot into my newly built system, but it just won't boot up by itself.
I believe i have most of samba configured right but i get this error each time time try to run it. I was given suggestion that i touch the file, i did, but i still cannot rid myself of this error.
Any suggestions (2 Replies)
hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request...
the installation crashes when trying to detect the NICS... (0 Replies)
Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Hi,
I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines.
I receive a 'EFAULT' when I try to access /dev/mem on these servers.
I suspect some... (1 Reply)
I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site.
The only device names in /dev for a tape drive were
/dev/xStp0
/dev/xcdt0
/dev/xct0
... (6 Replies)
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
My server has /var/log/messages with 'init: initLogger main process (608798) terminated with status 1' errors. I researched about the error and also followed the steps from stackexchange :
157059/error-init-ttys0-dev-ttys0-main-process-1612-terminated-with-status-1]linux - ERROR: init: ttyS0... (0 Replies)
Discussion started by: Paras Pandey
0 Replies
LEARN ABOUT NETBSD
boot
BOOT(8) BSD System Manager's Manual BOOT(8)NAME
boot -- system bootstrapping procedures
DESCRIPTION
This document provides information on using common features in the NetBSD boot loader. Additional information may be found in architecture-
specific boot(8) manual pages.
In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see
boothowto(9)).
Interactive mode
In interactive mode, the boot loader will present a prompt, allowing input of these commands:
boot [device:] [filename] [-1234abcdmqsvxz]
The default device will be set to the disk that the boot loader was loaded from. To boot from an alternate disk, the full name of
the device should be given at the prompt. device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit
number, and x is the partition letter.
The following list of supported devices may vary from installation to installation:
hd Hard disks.
fd Floppy drives.
The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a
kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz. Alternate system images
can be loaded by just specifying the name of the image.
Options are:
-1 Sets the machine-dependent flag RB_MD1 in boothowto.
-2 Sets the machine-dependent flag RB_MD2 in boothowto.
-3 Sets the machine-dependent flag RB_MD3 in boothowto.
-4 Sets the machine-dependent flag RB_MD4 in boothowto.
-a Sets the RB_ASKNAME flag in boothowto. This causes the kernel to prompt for the root file system device, the system crash
dump device, and the path to init(8).
-b Sets the RB_HALT flag in boothowto. This causes subsequent reboot attempts to halt instead of rebooting.
-c Sets the RB_USERCONF flag in boothowto. This causes the kernel to enter the userconf(4) device configuration manager as soon
as possible during the boot. userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard-
ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices.
-d Sets the RB_KDB flag in boothowto. Requests the kernel to enter debug mode, in which it waits for a connection from a kernel
debugger; see ddb(4).
-m Sets the RB_MINIROOT flag in boothowto. Informs the kernel that a mini-root file system is present in memory.
-q Sets the AB_QUIET flag in boothowto. Boot the system in quiet mode.
-s Sets the RB_SINGLE flag in boothowto. Boot the system in single-user mode.
-v Sets the AB_VERBOSE flag in boothowto. Boot the system in verbose mode.
-x Sets the AB_DEBUG flag in boothowto. Boot the system with debug messages enabled.
-z Sets the AB_SILENT flag in boothowto. Boot the system in silent mode.
consdev dev
Immediately switch the console to the specified device dev and reprint the banner. dev must be one of pc, com0, com1, com2, com3,
com0kbd, com1kbd, com2kbd, com3kbd, or auto. See Console Selection Policy in boot_console(8).
dev [device]
Set the default drive and partition for subsequent filesystem operations. Without an argument, print the current setting. device
is of the form specified in boot.
help Print an overview about commands and arguments.
ls [path]
Print a directory listing of path, containing inode number, filename, and file type. path can contain a device specification.
quit Reboot the system.
In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used.
FILES
/boot boot program code loaded by the primary bootstrap
/netbsd system code
/netbsd.gz gzip-compressed system code
/usr/mdec/boot master copy of the boot program (copy to /boot)
/usr/mdec/bootxx_fstype primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8).
SEE ALSO
Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9)BUGS
The kernel file name must be specified before, not after, the boot options. Any filename specified after the boot options, e.g.:
boot -d netbsd.test
is ignored, and the default kernel is booted.
BSD September 4, 2009 BSD
07-11-2006
Installing RedHat 8.0 onto Dell PowerEdge SC1425 - hdc: status error: status = 0x58
