| -< Drives show up twice w/ 2.7 upgrade >-
Some how I missed this note until Hans replied to it today.
Engineering is not working on your problem. V2.7 is working correctly.
From the Host or HSD console (consoles if duel redundant) you should
always see each drive. From the Host each drive will show up twice in
duel redundant when you type >>>sho dev.
In reference to -.1 reply Engineering is working on a problem with V5.0
that when you have most of the drives preferred to different
controllers >>>sho dev from a Host does NOT show all the drives on the
controller with the higher node number. All drives should show up twice.
This could be a boot problem only if you have the system disk preferred
to the higher controller node number and the second controller in the
pair did not see the disk. The workaround for this is to not prefer the
system disk or to prefer the system disk on the controller with the
lower node ID.
Engineering has never seen the problem you have described below. I would
suggest a configuration problem or old Host console code. Without ALL the
details we could not suggest more help.
Let me know if you still need more help.
Regards
John Kowall
I tried to update 2 redundant pairs(4-hsd30's) to v2.7 last week.
After I installed the 2.7 cards the system would not boot, the >>>sho
dev command listed all the drives twice.
ex: $1$dua0(hsd000)
$1$dua0(hsd001)....
If I powered off one hsd30 in the pair the disks would show up only
once and would work fine. I reinstalled the original 2.5 and the drives
showed up fine with the controllers back in redundant mode..
The HSD30's are shared between 2 4710 systems running 3.6 firmware.
I worked with Chris Howe from storage works support, we thought we had
the 2.7 firmware cards for an HS1CP but Chris checked with engineering and
they said they were the same cards for the HSD30's and HS1CP's..
Has anyone else seen this problem?
Harry
|