probe-scsi message Error
Hi,
This error may be is the reason of my eth card problem.
i tried to run the probe-scsi in a V440 Sun Server, and I have the following error:
{1} ok probe-scsi
This command may hang the system if a Stop-A or halt command
has been executed. Please type reset-all to reset the system
before executing this command.
Do you wish to continue? (y/n) y
ERROR: LSI1030 MPT Firmware, Fault code: 8112: PCI bus fault
ERROR: LSI1030: Could not set initiator ID.
ERROR: LSI1030 MPT Firmware, Fault code: 8112: PCI bus fault
ERROR: LSI1030: Could not set initiator ID.
Can't open SCSI host adapter
Can somebody tell me what does it mean ?
Thks in advc
Sebastian
# 1
I am receiving the same errrors when I executed probe-scsi-all. This is the first time I have dealt with this deivice, and the LSI. I created a mirror for my root drive and was researching.Did you get any response? I want to check firmware upgrades.Thanks
# 2
I am receiving the same errrors when I executed probe-scsi-all. This is the first time I have dealt with this deivice, and the LSI. I created a mirror for my root drive and was researching.Did you get any response? I want to check firmware upgrades.Thanks
# 3
If you execute the command properly, you won't get those errors.
At OBP, set auto-boot to `false` and then do reset-all.
That writes the change of settings and will power-cycle the system.
It will automatically stop at the OBP prompt and all your data registers will be clear.
Then when you run your probe of the SCSI bus, it won't bark at you.
It's been a while (few weeks?) but this has been discussed
over and over and over again in these Hardware forums,
and that is why there had not been any response to the initial post.
--
OBP 4.x Command Reference Manual
http://docs.sun.com/app/docs?q=816-1177(document 816-1177)
(be patient, it loads slowly)
# 4
I had run an init 0 before running the probe-scsi-all, I didn't interrupt the system.
Also, I mirrored the root drive and when I tried to boot disk2 (which the Sun manual said you should be able to do after mirroring), it failed no boot device.
What do those error mean on the LSI regarding MPT Firmware Faultcode 8112.
Thanks
Jun 7 15:18:54 kristinampt0 Firmware version v1.3.27.0 (IM/IME)
Jun 7 15:19:36 kristinampt1 Firmware version v1.3.27.0 (IM/IME)
# raidctl
RAIDVolume RAIDRAIDDisk
Volume TypeStatus DiskStatus
c1t0d0 IMRESYNCINGc1t0d0 OK
c1t2d0 OK
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@0,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@1,0
2. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@1f,700000/scsi@2/sd@3,0
# 5
Sorry, can't help with those.It's been far too long since I had to support that product.I just don't remember any longer, and don't have access to the support documentsthat I used to reference when I used to work for Sun.
# 6
I followed your suggestions about the auto-boot and it worked. Do you have any idea why I still can't boot off disk2 (the mirrored drive)?
ok> setenv auto-boot? false
ok> reset-all
ok> probe-scsi-all
and the errors went away.
Afterwards when I switched it to
ok> setenv auto-boot? true
ok> reset-all
The system rebooted to disk0.
When I try to boot off the mirrored drive (disk2) it says "cannot open boot device". Is there more that has to be done?
Thanks
# 7
try disk1, perhaps ?0, 1, 2, 3not 1, 2, 3, 4
# 8
Thanks but if you look at the format, its disk 2 that I created the mirror on (it doesn't show up).
When I executed the raidctl -c command, it took seconds for the prompt to come back, although there is quite a bit of data on it. Also, does create the boot block on the disk when the mirror is created?
Thanks so much.
# 9
Sunfire V440 ?
Have you had a chance to glance through the System Administration Manual
for that platform (document 816-7728) ?
http://www.sun.com/products-n-solutions/hardware/docs/pdf/816-7728-10.pdf
Quoting from it:When you create a RAID mirror, the slave drive
(in this example case, c1t1d0)
disappears from the Solaris device tree.
I don't "do " storage very well.
I've always been in environments where other did that, while I did other things.
Let's hope that others join this thread with their guidance.
# 10
And that is exactly what is happening, but the manual also says you should be able to do "boot disk2" and it should boot. I'm wondering if I have to break the mirror to boot the second drive because it indicated the drive had to be unmounted to create the mirror. With the source disk still functioning, maybe it doesn't mount it.
Thanks for your suggestions.
