On 12 April 2015 at 22:45, Michael Tiernan <michael.tier...@gmail.com> wrote:
> On 4/12/15 1:25 PM, c...@vinny.peecee3.com wrote: > > Michael Tiernan wrote: > >> Normally, what will happen is that the kickstart process will wipe and > >> rebuild on the drive in Slot1 since it is the first drive. This is not > >> the desired outcome. > >> > >> What I want to do is confirm that the drive I'm focusing on is the > >> "correct" one in the physical hardware slot 0. > > Curious why the 'for whatever reason' has gone unremarked. > > What's the use case? (Frankly, could this happen to me and > > should I pay close attention?) One response seemed to assume you > > have data on other disks you want to preserve. Maybe you're > > trying to track a physical disk that contains the root > > filesystem? Fail the install if any disks are inop? Something > > else? > First off, a preface/reminder. We don't always get to choose the > entirety of our infrastructure that we inherit. :( (i.e. suspend > preferred logic and assume to pick one battle at a time.) > > So, my use case, as screwy as it may seem is this: > > I've got a machine with > 1 drives in it. Usually the number is 6, 8, or > greater now that we've got some new slot rich Dells in the racks. > > Machine is running along with the system on the disk in slot 0 and the > other 6, 8, etc drives configured as individual RAID0 containers or just > as raw disks. Don't ask, just go with it. Principle rule, data (on data > drives) is sacred and should never be lost. > [snip] I don't think you can reach the "never" threshold, as the order in which drives are presented to the system by the controller is going to be dependent on the controller, and the controller is a black box which you don't have the specifications for. Even if testing shows a pattern of behaviour, you can't eliminate the possibility that it missed an edge case. Adding to the other suggestions - given that you already have access to the machines, you could create a configuration management DB recording the host, disk serial numbers and usage. If the DB has a simple network API, then you could query it from the kickstart's %pre section to identify which disks can't be used as installation targets. Alternatively, could you identify the data disks so you know to ignore them? For example Oracle ASM disks appear empty to the OS, but have an identifiable header. Although RAID0's are going to be tough to identify if they weren't built with metadata... Cheers -- Jonathan Barber <jonathan.bar...@gmail.com>
_______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
