Original Message:
Sent: Fri May 12, 2023 02:47 AM
From: John Mortensen
Subject: V7000 - ghost drive removal
Hi Christian,
I suspected so, yes I know it is cosmetic, however it is annoying (to me at least :-)), what I was looking for was some command that could fix it for me (a variation on chdrive for instance). :-)
------------------------------
John Mortensen
Original Message:
Sent: Fri May 12, 2023 02:40 AM
From: Christian Schroeder
Subject: V7000 - ghost drive removal
I am afraid it is not possible to supply the ifix then.
As I have learned in that context though, it's rather a cosmetical issue which can be safely ignored.
Sorry for not being able to be more helpful on this.
------------------------------
Christian Schroeder
IBM SpecV Storage Support with Passion
Original Message:
Sent: Fri May 12, 2023 02:19 AM
From: John Mortensen
Subject: V7000 - ghost drive removal
Hi Christian,
The system is a 2076-524 running code level 8.4.0.6, as the system is old it is no longer in IBM service, in this case is it still possible to raise a support ticket?
/John
------------------------------
John Mortensen
Original Message:
Sent: Fri May 12, 2023 01:51 AM
From: Christian Schroeder
Subject: V7000 - ghost drive removal
Hi John,
what code level is the V7000 running at the moment?
In fact there is an issue with unsupported "ghost drive" back at certain code levels.
We can provide an ifix to remedy this.
If need be, you might need to raise a support ticket to get hold of that ifix.
Best regards,
Christian Schroeder
------------------------------
Christian Schroeder
IBM SpecV Storage Support with Passion
Original Message:
Sent: Thu May 11, 2023 04:22 AM
From: John Mortensen
Subject: V7000 - ghost drive removal
Hi,
I have, by mistake, swapped a V5000 drive into a V7000, after this replaced the V5000 drive with the correct V7000 drive. Now I am stuck with a ghost drive which I cannot figure out to remove.
Drive information:
>lsdrive |grep -v online
id status error_sequence_number use tech_type capacity mdisk_id mdisk_name member_id enclosure_id slot_id node_id node_name auto_manage drive_class_id
178 offline failed unsupported 7.3TB inactive
Normal I remove these using chdrive, but that does not work here:
>chdrive -use unused 178
CMMVC6595E The command cannot be initiated because a drive that you have specified has a technology type that is not supported for the command.
I have tried to reboot the active node to get rid of it, but it still hangs on.
Any clues to how this can be removed?
/John
------------------------------
John Mortensen
------------------------------