Sponsored Content
Full Discussion: Problem booting unix
Top Forums UNIX for Advanced & Expert Users Problem booting unix Post 80035 by reborg on Tuesday 2nd of August 2005 03:42:27 PM
Old 08-02-2005
It might be possible if we knew what hardware and OS we are dealing with.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Advanced & Expert Users

Booting Problem

Hai I have installed win 98 o.s in my system after that i have installed Red Hat Linux 7.0,there is a problem in dual booting,by default win98 is being booted, when i insert bootable linux floppy linux is loaded My doubt how to overwrite windows MBR and palce the lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies

3. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

4. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

5. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

6. Solaris

problem while booting from hdd

hello gurus, i have just installed the os on hdd, when i write down boot command on ok prompt, I get following error continuously. what could be the possible problem WARNING: /ssm@0,0/pci@18,600000/scsi@2/sd@0,0 (sd0): auto request sense failed (reason=reset) WARNING:... (2 Replies)
Discussion started by: sameergrover
2 Replies

7. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

8. AIX

AIX Booting problem

Hi, I have IBM RS/6000 44P MODEL 170 server with Aix 5.1 Till the morning server is working fine, i turned off properly but now i tried to start it is showing below error on LED and going down (power off) E051 >>>E0E0 >>>> E0E1>>>> 种种种种 >>>> 40210014 P1-C1-F1 ccccccc >>>> 40210014 >>>>E043... (3 Replies)
Discussion started by: ANAND KURADE
3 Replies

9. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)
All times are GMT -4. The time now is 08:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy