Sponsored Content
Operating Systems Solaris Unable to login Solaris 10 Sparc - Data Access Error Post 302490326 by mfsaeed on Monday 24th of January 2011 02:45:14 PM
Old 01-24-2011
More updates on this issue. At the boot command ("ok" prompt) - if I type "boot device", I get the following results:
Code:
Boot device: /pci@1e,600000/ide@d/disk@0,0:a File and args: device
can't open device
Warning: Fcode sequence resulted in a net stack depth change of 1 Evaluating:
Evaluating:
the file just loaded does not appear to be executable.

I will try to post this question on other forums as well but so far I think this is the best forum on Unix questions.

Thanks.

Last edited by Scott; 01-24-2011 at 04:26 PM.. Reason: Code tags
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris 8 hangs and data access error on reboot

Hi using solaris 5.8 on UltraSPARC-IIi 360MHz. I know it is an old hardware but similiar hardware is running fine. here is the issue, System booted : works okay for some time then display was hung so system was rebooted ..it gave data access error. again rebooted and it came up... (6 Replies)
Discussion started by: upengan78
6 Replies

2. Solaris

Unable to access open solaris across the network.

Hi Everyone, I have installed open solaris 10 on one of the x86 machines available but inspite of configuring the IP i am unable to access the machine through the network. Can anyone please help me wih the settings required to access the machine across the network.Its really Urg..Any help is... (13 Replies)
Discussion started by: sankasu
13 Replies

3. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

4. UNIX for Dummies Questions & Answers

can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?

Hi Gurus can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC? regards, Israel. (9 Replies)
Discussion started by: iga3725
9 Replies

5. Solaris

Unable to access serial port from non-global solaris zone on netra 240

I am trying to use a serial communications device that is connected to /dev/ttyb on a netra 240 server. This is a solaris zone configuration using solaris 10 0910. I am able to access /dev/ttyb from the global zone but not throught he non-global zone. I have enabled all of the tty devices in my... (0 Replies)
Discussion started by: disagreeable
0 Replies

6. Solaris

unable to login Solaris 10

I have inherited a solaris 10 server. I went to log into it the other day over the console connection, and after sucessfully entering the password, I was booted back to the login prompt with no errors visible. If I enter an incorect password, the console displays 'incorrect password' and kicks... (8 Replies)
Discussion started by: Sol-nova
8 Replies

7. Red Hat

Unable to access NFS share on Solaris Server from Linux client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. share -F nfs -o rw /var/share & then ran the following svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies

8. Solaris

Solaris SPARC boot error

Hi Admins, When i tried to boot the system from ALOM console i am getting below error and not sure what caused this error. Btw the machine is running on Solaris SPARC 10. Can you shed some light on this? {b} ok boot -sv SC Alert: Host System has Reset SC Alert: Host system has... (23 Replies)
Discussion started by: prash358
23 Replies

9. Solaris

Newly relabelled disc unable to initialize to Solaris 8 login - please help

We are having a problem with initializing Solaris 8 installed on a Sunblade 1500 after having cloned the hard disc. (The cloning process was done in a windows environment. Not a UNIX environment.) Immediately after the cloning process neither hard disc would boot until the format label... (10 Replies)
Discussion started by: DR_RALT
10 Replies

10. Solaris

Solaris 10 boot problem - ERROR: Last Trap: Fast Data Access MMU Miss

Hello, We have a T5140 server with Solaris 10 and its suddenly throwing "segmentation core" when I login into the server and not showing any output for commands like df, mount etc. so I had to reboot the server to fix this issue. Please note that there's no boot disk mirroring. But... (2 Replies)
Discussion started by: prvnrk
2 Replies
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
All times are GMT -4. The time now is 01:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy