[Deepsea-users] Orch discovery not finding all disks
suse at ash4d.com
Thu Jun 15 08:35:59 MDT 2017
Here's a zip file with the supportconfig from all 5 of the boxes.
Each of the boxes has a single ~500GB IDE drive on the HCI controller
and 8 2TB drives on the HPSA (each is set up as single-drive RAID0).
On ses1 (manual install) the root filesystem went to the single drive
on the HCI controller, and it detected the 8 drives on the HPSA and
added them to the profile. On the ses1 through ses6 systems (deployed
via autoyast) the root filesystem was put on one of the 8 drives on the
HPSA, and the discovery only created profiles for the single IDE drive.
The ses5 system was pulled out due to hardware issues with the HPSA,
hence the hole in the numbering.
On Thu, 2017-06-15 at 09:19 +0200, Jan Fajerski wrote:
> I have never seen this behaviour. Could you please provide some more
> info about
> the hardware configuration?
> Disks, controllers and so on.
> On Thu, Jun 15, 2017 at 05:30:35AM +0000, Rick Ashford wrote:
> > I'm installing SES4 via DeepSea and in the discovery stage it
> > appears that the runner only discovers drives that are attached to
> > the same controller as the root disk, which is leaving my profiles-
> > <ID> section very underpopulated. Has anybody else seen behavior
> > like this and/or know how to work around?
> > Rick Ashford
> > Sales Engineering Manager - West
> > rick.ashford at suse.com
> > (512)731-3035
> > _______________________________________________
> > Deepsea-users mailing list
> > Deepsea-users at lists.suse.com
> > http://lists.suse.com/mailman/listinfo/deepsea-users
More information about the Deepsea-users