Yesterday you allocated five new LUNs for a Solaris 9 host. Today the Solaris administrator is concerned about corrupt data because the host system log has several entries referencing the new LUNs wit

Question

Options

• AThat they need to configure Device Mapper for the newly allocated LUNs.
• BThat they should shut down the server right away and that you will allocate five new LUNs.
• CThat the message is normal for new LUN allocations and that they just need to label the new
• DThat the Master Boot Record (MBR) on one of the disks has become corrupt and that rebooting

• A
  8% (3)
• B
  3% (1)
• C
  83% (30)
• D
  6% (2)

Explanation

On Solaris, when a new LUN is presented to a host for the first time, it has no disk label yet - the "Corrupt label; wrong magic number" message is Solaris's way of saying the disk is unlabeled, not that data is actually damaged. The administrator simply needs to run format and label the new disks before use, which is standard procedure after any new LUN allocation.

Why the distractors are wrong:

• A is wrong because Device Mapper is a Linux (not Solaris) concept - it has no relevance here.
• B is wrong because shutting down and reallocating LUNs is a drastic, unnecessary overreaction; nothing is actually corrupt.
• D is wrong because this is not an MBR corruption issue - the message is about a missing Solaris disk label (VTOC), not a damaged boot record, and rebooting would accomplish nothing.

Memory tip: Think of "wrong magic number" as Solaris saying "I don't recognize this disk - it has no name tag yet." New LUNs are blank slates; the "corrupt label" warning is just Solaris complaining that no one has introduced it to the disk yet. Label = introduce; no label = not corrupt.

No community discussion yet for this question.