I am trying to iSCSI boot RHEL6.1 using our B200 and M81KR Palo nic.
Installation of RHEL6.1 is successful, but I encounter a "Kernel panic - not syncing: Attempted to kill init!" error message when I attempt to boot the OS.
-Service profile has four vNICs configured. Two of these vNICs (named 'eth0' and 'eth1') are used for management and on vlan100. The other two vNICs (named 'eth2' and 'eth3') are used for data purposes and are both on vlan7.
-I have one iSCSI vNIC configured with the default iSCSI Adapter Policy applied. iSCSI vNIC is overlayed on 'eth2'.
-native vlan enabled on each interface and vlan.
Storage configuration is a Nimble Storage CS240.
Data ports of the array are directly connected to the FI and FI ports are configured as Appliance ports.
Can someone please explain to me why RHEL is able to iSCSI boot if I have a local disk installed? In my original post, I did installation with the local SAS drives physically removed from the blade. In this setup, booting without SAS drives caused the Kernel Panic after ~80% of the OS had loaded. The only device in this setup, and during installation, is the iSCSI device itself.
Howerver, if I choose the same installation options, but I have SAS drives phyically attached to the blade, then RHEL is able to iSCSI boot??? Your likely thinking in this setup I made a mistake and that I am booting from the local drive. It's posible my loader configuration is wrong, but when I do a 'du -h' is it shows that my root partition is on my 50GB iSCSI disk.
And the question would still remain as to why the Kernel Panic occured if there were no physical disks installed?
For my (in)sanity check, can someone please remove all non-iSCSI disks from their B200, try to install RHEL6.1to an iSCSI device, and then iSCSI boot it? Possible RHEL bug here?
And perhaps it is user error. Below are the installation screenshots of the major installation steps. Can someone please point out what I'm doing wrong that would somehow involve the local SAS disk?
There is a prevalence of network threats across the world, and the rate, at which these threats continue to emerge, is more rapid than ever before. Cisco Next Generation Firepower (CNGFW) security technologies is information security service that provides...
Upload the Script to Datastore
1. Browse to any Datastore of ESXi Host2. Upload the folder "lsigetvmware_022817" ex. Suppose the datastore name is "Datastore3"
Run the Commands
Enable SSH of ESXi Host
SSH to ESX...
SymptomsCisco Prime is unresponsive. Web GUI will not load. Device doesn't respond to ping.DiagnosisPrime chassis is off.SolutionSince the CIMC uses Flash you can no longer use your bowser. SSH to CIMC address instead. show chassis detailChassis:Powe...
Very first data cloud — Evolution of data lake to hybrid cloud
Today, in this digitized world, data is being generated at a very high rate and from many different sources, and it is growing exponentially in many use ca...
PXE (Preboot eXecution Environment) Server allows unattended or automated OS installation over the Network. The main benefit of pxe is that we don’t need any bootable drive to boot OS(Operating system) and we do not need to to burn any ISO file into DVD o...