[Linux-PowerEdge] internal disks on raid controller and linux

JHurley at SummitRacing.com JHurley at SummitRacing.com
Tue Nov 27 18:49:06 CST 2012


Dell support wants me to update BIOS and Raid Controller ( PERC H700
whatever that is ) firmware ... pretty new servers ... sounds like
default recommendation with no clue that is linked to my problem.

This is what I see in /var/log/messages on a normal boot when we come up
on /dev/sda ...

Nov 26 17:55:14 westo-02 kernel: megasas: 00.00.05.40-rh2 Thu. Aug. 4
17:00:00 PDT 2011
Nov 26 17:55:14 westo-02 kernel: megasas: 0x1000:0x0079:0x1028:0x1f17:
bus 3:slot 0:func 0
Nov 26 17:55:14 westo-02 kernel: megaraid_sas 0000:03:00.0: PCI INT A ->
GSI 33 (level, low) -> IRQ 33
Nov 26 17:55:14 westo-02 kernel: megasas: FW now in Ready state
Nov 26 17:55:14 westo-02 kernel: megasas_init_mfi:
fw_support_ieee=67108864
Nov 26 17:55:14 westo-02 kernel: megasas: INIT adapter done
Nov 26 17:55:14 westo-02 kernel: megaraid_sas: fw state:c0000000
Nov 26 17:55:14 westo-02 kernel: megasas: fwstate:c0000000, dis_OCR=0
Nov 26 17:55:14 westo-02 kernel: scsi0 : LSI SAS based MegaRAID driver
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:0:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:1:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:2:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:3:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:4:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:5:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: Emulex LightPulse Fibre Channel SCSI
driver 8.3.5.45.4p
Nov 26 17:55:14 westo-02 kernel: Copyright(c) 2004-2011 Emulex.  All
rights reserved.
Nov 26 17:55:14 westo-02 kernel: lpfc 0000:04:00.0: PCI INT A -> GSI 34
(level, low) -> IRQ 34
Nov 26 17:55:14 westo-02 kernel: scsi1 :  on PCI bus 04 device 00 irq 34
Nov 26 17:55:14 westo-02 kernel: usb 1-3: new high speed USB device
using ehci_hcd and address 3
Nov 26 17:55:14 westo-02 kernel: scsi 0:0:32:0: Enclosure         DP
BACKPLANE        1.07 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:2:0:0: Direct-Access     DELL
PERC H700        2.10 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: scsi 0:2:1:0: Direct-Access     DELL
PERC H700        2.10 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: usb 1-3: New USB device found,
idVendor=0424, idProduct=2514
Nov 26 17:55:14 westo-02 kernel: usb 1-3: New USB device strings: Mfr=0,
Product=0, SerialNumber=0
Nov 26 17:55:14 westo-02 kernel: usb 1-3: configuration #1 chosen from 1
choice
Nov 26 17:55:14 westo-02 kernel: hub 1-3:1.0: USB hub found
Nov 26 17:55:14 westo-02 kernel: hub 1-3:1.0: 3 ports detected
Nov 26 17:55:14 westo-02 kernel: usb 3-1: new low speed USB device using
uhci_hcd and address 2
Nov 26 17:55:14 westo-02 kernel: usb 3-1: New USB device found,
idVendor=0624, idProduct=0422
Nov 26 17:55:14 westo-02 kernel: usb 3-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
Nov 26 17:55:14 westo-02 kernel: usb 3-1: Product: Avocent USBIAC
Nov 26 17:55:14 westo-02 kernel: usb 3-1: Manufacturer: Avocent
Nov 26 17:55:14 westo-02 kernel: usb 3-1: configuration #1 chosen from 1
choice
Nov 26 17:55:14 westo-02 kernel: input: Avocent Avocent USBIAC as
/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input2
Nov 26 17:55:14 westo-02 kernel: generic-usb 0003:0624:0422.0001:
input,hidraw0: USB HID v1.10 Keyboard [Avocent Avocent USBIAC] on
usb-0000:00:1a.0-1/input0
Nov 26 17:55:14 westo-02 kernel: input: Avocent Avocent USBIAC as
/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/input/input3
Nov 26 17:55:14 westo-02 kernel: generic-usb 0003:0624:0422.0002:
input,hidraw1: USB HID v1.10 Mouse [Avocent Avocent USBIAC] on
usb-0000:00:1a.0-1/input1
Nov 26 17:55:14 westo-02 kernel: usb 5-2: new full speed USB device
using uhci_hcd and address 2
Nov 26 17:55:14 westo-02 kernel: usb 5-2: New USB device found,
idVendor=0624, idProduct=0248
Nov 26 17:55:14 westo-02 kernel: usb 5-2: New USB device strings: Mfr=1,
Product=2, SerialNumber=3
Nov 26 17:55:14 westo-02 kernel: usb 5-2: Product: USB Composite
Device-0
Nov 26 17:55:14 westo-02 kernel: usb 5-2: Manufacturer: Avocent
Nov 26 17:55:14 westo-02 kernel: usb 5-2: SerialNumber: 20080519
Nov 26 17:55:14 westo-02 kernel: usb 5-2: configuration #1 chosen from 1
choice
Nov 26 17:55:14 westo-02 kernel: input: Avocent USB Composite Device-0
as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input4
Nov 26 17:55:14 westo-02 kernel: generic-usb 0003:0624:0248.0003:
input,hidraw2: USB HID v1.00 Keyboard [Avocent USB Composite Device-0]
on usb-0000:00:1d.0-2/input0
Nov 26 17:55:14 westo-02 kernel: input: Avocent USB Composite Device-0
as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.1/input/input5
Nov 26 17:55:14 westo-02 kernel: generic-usb 0003:0624:0248.0004:
input,hidraw3: USB HID v1.00 Mouse [Avocent USB Composite Device-0] on
usb-0000:00:1d.0-2/input1
Nov 26 17:55:14 westo-02 kernel: lpfc 0000:05:00.0: PCI INT A -> GSI 35
(level, low) -> IRQ 35
Nov 26 17:55:14 westo-02 kernel: scsi2 :  on PCI bus 05 device 00 irq 35
Nov 26 17:55:14 westo-02 kernel: lpfc 0000:04:00.0: 0:1303 Link Up Event
x1 received Data: x1 xf7 x20 x0 x0 x0 0
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:0:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:0:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:0:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:0:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:1:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:1:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:1:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 1:0:1:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: ata_piix 0000:00:1f.2: PCI INT C -> GSI
23 (level, low) -> IRQ 23
Nov 26 17:55:14 westo-02 kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1
-- ]
Nov 26 17:55:14 westo-02 kernel: scsi3 : ata_piix
Nov 26 17:55:14 westo-02 kernel: scsi4 : ata_piix
Nov 26 17:55:14 westo-02 kernel: ata1: SATA max UDMA/133 cmd 0xbc10 ctl
0xbc08 bmdma 0xbc20 irq 23
Nov 26 17:55:14 westo-02 kernel: ata2: SATA max UDMA/133 cmd 0xbc18 ctl
0xbc0c bmdma 0xbc28 irq 23
Nov 26 17:55:14 westo-02 kernel: lpfc 0000:05:00.0: 1:1303 Link Up Event
x1 received Data: x1 xf7 x20 x0 x0 x0 0
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:0:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:0:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:0:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:0:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:1:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:1:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:1:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: scsi 2:0:1:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 17:55:14 westo-02 kernel: ata1: SATA link up 1.5 Gbps (SStatus
113 SControl 300)
Nov 26 17:55:14 westo-02 kernel: ata1.00: ATAPI: PLDS DVD+/-RW DS-8A8SH,
KD51, max UDMA/100
Nov 26 17:55:14 westo-02 kernel: ata1.00: configured for UDMA/100
Nov 26 17:55:14 westo-02 kernel: scsi 3:0:0:0: CD-ROM            PLDS
DVD+-RW DS-8A8SH KD51 PQ: 0 ANSI: 5
Nov 26 17:55:14 westo-02 kernel: ata2: failed to resume link (SControl
0)
Nov 26 17:55:14 westo-02 kernel: ata2: SATA link down (SStatus 4
SControl 0)
Nov 26 17:55:14 westo-02 kernel: sd 0:2:1:0: [sdb] 1170997248 512-byte
logical blocks: (599 GB/558 GiB)
Nov 26 17:55:14 westo-02 kernel: sd 0:2:0:0: [sda] 1170997248 512-byte
logical blocks: (599 GB/558 GiB)

Looks like last 2 lines show that sda and sdb are the 599 gb raid 1
"disks" ...

On a bad boot this is an example of what I see ... 

Nov 26 18:06:18 westo-02 kernel: scsi1 :  on PCI bus 05 device 00 irq 35
Nov 26 18:06:18 westo-02 kernel: lpfc 0000:04:00.0: 0:1303 Link Up Event
x1 received Data: x1 xf7 x20 x0 x0 x0 0
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:0:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:0:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:0:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:0:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:1:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:1:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:1:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 0:0:1:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: megasas: 00.00.05.40-rh2 Thu. Aug. 4
17:00:00 PDT 2011
Nov 26 18:06:18 westo-02 kernel: megasas: 0x1000:0x0079:0x1028:0x1f17:
bus 3:slot 0:func 0
Nov 26 18:06:18 westo-02 kernel: megaraid_sas 0000:03:00.0: PCI INT A ->
GSI 33 (level, low) -> IRQ 33
Nov 26 18:06:18 westo-02 kernel: megasas: FW now in Ready state
Nov 26 18:06:18 westo-02 kernel: megasas_init_mfi:
fw_support_ieee=67108864
Nov 26 18:06:18 westo-02 kernel: megasas: INIT adapter done
Nov 26 18:06:18 westo-02 kernel: megaraid_sas: fw state:c0000000
Nov 26 18:06:18 westo-02 kernel: megasas: fwstate:c0000000, dis_OCR=0
Nov 26 18:06:18 westo-02 kernel: scsi2 : LSI SAS based MegaRAID driver
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:0:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:1:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:2:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:3:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:4:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:5:0: Direct-Access     SEAGATE
ST3600057SS      ES65 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: ata_piix 0000:00:1f.2: PCI INT C -> GSI
23 (level, low) -> IRQ 23
Nov 26 18:06:18 westo-02 kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1
-- ]
Nov 26 18:06:18 westo-02 kernel: scsi 2:0:32:0: Enclosure         DP
BACKPLANE        1.07 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:2:0:0: Direct-Access     DELL
PERC H700        2.10 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi 2:2:1:0: Direct-Access     DELL
PERC H700        2.10 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: scsi3 : ata_piix
Nov 26 18:06:18 westo-02 kernel: scsi4 : ata_piix
Nov 26 18:06:18 westo-02 kernel: ata1: SATA max UDMA/133 cmd 0xbc10 ctl
0xbc08 bmdma 0xbc20 irq 23
Nov 26 18:06:18 westo-02 kernel: ata2: SATA max UDMA/133 cmd 0xbc18 ctl
0xbc0c bmdma 0xbc28 irq 23
Nov 26 18:06:18 westo-02 kernel: lpfc 0000:05:00.0: 1:1303 Link Up Event
x1 received Data: x1 xf7 x20 x0 x0 x0 0
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:0:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:0:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:0:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:0:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:1:0: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:1:1: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:1:2: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: scsi 1:0:1:3: Direct-Access     DGC
VRAID            0531 PQ: 0 ANSI: 4
Nov 26 18:06:18 westo-02 kernel: ata1: SATA link up 1.5 Gbps (SStatus
113 SControl 300)
Nov 26 18:06:18 westo-02 kernel: ata1.00: ATAPI: PLDS DVD+/-RW DS-8A8SH,
KD51, max UDMA/100
Nov 26 18:06:18 westo-02 kernel: ata1.00: configured for UDMA/100
Nov 26 18:06:18 westo-02 kernel: scsi 3:0:0:0: CD-ROM            PLDS
DVD+-RW DS-8A8SH KD51 PQ: 0 ANSI: 5
Nov 26 18:06:18 westo-02 kernel: ata2: failed to resume link (SControl
0)
Nov 26 18:06:18 westo-02 kernel: ata2: SATA link down (SStatus 4
SControl 0)
Nov 26 18:06:18 westo-02 kernel: sd 2:2:0:0: [sdi] 1170997248 512-byte
logical blocks: (599 GB/558 GiB)
Nov 26 18:06:18 westo-02 kernel: sd 0:0:0:0: [sda] 536870912 512-byte
logical blocks: (274 GB/256 GiB)
Nov 26 18:06:18 westo-02 kernel: sd 0:0:0:2: [sdc] 536870912 512-byte
logical blocks: (274 GB/256 GiB)
Nov 26 18:06:18 westo-02 kernel: sd 0:0:0:1: [sdb] 536870912 512-byte
logical blocks: (274 GB/256 GiB)
Nov 26 18:06:18 westo-02 kernel: sd 2:2:1:0: [sdj] 1170997248 512-byte
logical blocks: (599 GB/558 GiB)

Here last 5 lines show sdi and sdj getting the raid 1 "disks" ... 

Plus the line megasas: FW now in Ready state comes in much later ... 

Not sure a udev rule will fix ... when it says kernel instead of udev
... confused here!


-----Original Message-----
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of
Spike_White at Dell.com
Sent: Tuesday, November 27, 2012 1:17 PM
To: linux-poweredge at lists.us.dell.com
Subject: [Linux-PowerEdge] internal disks on raid controller and linux

We have a very similar setup as you, in our lab.   We're running OEL 6.3
and 5.x on R710s (& other server models).  

Like you, on R710s we're running RAID 1 (OS vol), RAID 1 (data vol) and
2 global hotspares).  Like you, we mount by UUID on OEL, or by logical
volume name.

I remember long ago there was a bug in the LSI driver in OEL 5.x.   For
low-end PERCs.  The LSI driver didn't pass up the unique vol identifier
associated w/ a PERC volume.  This was most notable if you destroyed
your second PERC volume and re-created it.  Suddenly, the OS vol
/dev/sda became /dev/sdb, or /dev/sdc.

This was particularly vexing when we ran SLES 10, as we didn't mount by
UUID and we used raw disk slices (instead of LVMs).  Ordinarily,
destroying an unused second PERC vol (via omconfig) and re-creating it
is an on-line operation.  But due to this bug, it'd hang the kernel.
It'd no longer be able to access its underlying filesystem on disk.

I believe this LSI driver bug was corrected long ago.  (I'm not sure, as
we started ordering our R710s w/ PERC H700s and didn't have any problem
since.)

Additionally, usually it wouldn't randomly enumerate on a reboot.   Very
rarely.  

Another responder mentioned a SSD or USB key or virtual media attached.
That's theoretically possible, particularly in OEL 6.x.  On the boot
media, it enumerates the virtual media and/or physical USB keys as
/dev/sda.   
However, I'm unsure of that explanation for two reasons.  

1. I'm looking at an OEL 6.3 server w/ attached USB drive now.  It's
enumerating the (sole) PERC vol as /dev/sda and this USB key as
/dev/sdb.  So the installed kernel differs from the OEL 6.x boot media
kernel's behavior.
2. You mentioned your first volume is found as /dev/sdi or /dev/sdj.
If it were only a USB or virtual media found first, it'd be /dev/sdb or
/dev/sdc.

I speculate that it may be enumerating your LUNs first.  And then your
PERC vols.  I've seen this before.  There's two ways to verify.

1. What does inq tell you?  (low-level utility available from EMC to
list all discovered LUNs).  If you don't have inq handy, you can use
sg_map -x -i to get enumeration + vendor.
2. pull your fiber cables to your HBA and reboot repeatedly.  See if it
always discovers as /dev/sda (or /dev/sdb if virt media or USB key
attached).

In older Linux distros, we used to have to force the enumeration of the
PERC vols before the FC LUNs by using "brokenmodules=lpfc" on the kernel
command line.   Haven't had to do that in OEL 5 or 6.

>From Dell I/T,
Spike White

-----Original Message-----
 
   1.  internal disks on raid controller and linux
      (JHurley at SummitRacing.com)
----------------------------------------------------------------------

Message: 1
Date: Tue, 27 Nov 2012 07:35:36 -0500
From: <JHurley at SummitRacing.com>
Subject: [Linux-PowerEdge] internal disks on raid controller and linux
To: <linux-poweredge at lists.us.dell.com>
Message-ID:
	
<05E4D346569A524D8567AE359EA3286D24E9974E at EXCHANGE-OHIO.summit.network>
	
Content-Type: text/plain; charset="us-ascii"

We have a set of new Dell servers R710's each with 6 internal disks.
Using 2 raid 1 mirrors and two hot spares.  EMC storage from VNX with
powerpath also defined.  Oracle Linux OL 6.2 ( clone of redhat )
installed on first raid 1 mirror and all 3rd party software.  Also going
to use Acronis to get OS backups and have bare metal restore capability.

 

Usually my OS comes up on /dev/sda ... ( so /boot on /dev/sda1 and my
root directory on /dev/sda2 etc ).

 

Sometimes though it comes up on different device ... and for various
reasons the Acronis backup/recovery will only work completely when it
sees disk 1 on /dev/sda ... the /etc/fstab is using UUID so systems will
boot up and run either way.

 

What is going on here?  Something from internal raid controller and when
linux sees the device being timing dependent?  I really need to get it
consistent because of the Acronis stuff.

 

Considering trying to force with udev rule but ... not sure how to
proceed here exactly ( Oracle DBA not linux sys admin here ).

 

Some of most recent boots ( excerpted lines ) show this kind of pattern
( from /var/log/messages ).  Most recent one from yesterday now has
/boot on /dev/sdi1 

 

(6869): Nov 26 17:07:58 westo-02 kernel: sd 0:2:1:0: [sdb] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(6870): Nov 26 17:07:58 westo-02 kernel: sd 0:2:0:0: [sda] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(8093): Nov 26 17:31:01 westo-02 kernel: sd 2:2:0:0: [sdi] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(8094): Nov 26 17:31:01 westo-02 kernel: sd 2:2:1:0: [sdj] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(9312): Nov 26 17:44:33 westo-02 kernel: sd 0:2:0:0: [sda] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(9313): Nov 26 17:44:33 westo-02 kernel: sd 0:2:1:0: [sdb] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(10528): Nov 26 17:55:14 westo-02 kernel: sd 0:2:1:0: [sdb] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(10529): Nov 26 17:55:14 westo-02 kernel: sd 0:2:0:0: [sda] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(11732): Nov 26 18:00:56 westo-02 kernel: sd 0:2:0:0: [sda] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(11733): Nov 26 18:00:56 westo-02 kernel: sd 0:2:1:0: [sdb] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(12946): Nov 26 18:06:18 westo-02 kernel: sd 2:2:0:0: [sdi] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

(12950): Nov 26 18:06:18 westo-02 kernel: sd 2:2:1:0: [sdj] 1170997248
512-byte logical blocks: (599 GB/558 GiB)

 


_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

NOTICE: The information in this electronic mail transmission, including all attachments, is intended by Autosales, Incorporated dba Summit Racing Equipment for exclusive use of the named individual or entity to which it is directed.  Please understand that this electronic mail transmission may contain information that is a trade secret or is otherwise confidential, and therefore must be protected from disclosure.  It is not intended for transmission to, or receipt by, anyone other than the named addressee (or person expressly authorized to deliver it to the named addressee).  The information contained in this electronic mail transmission must not be copied or forwarded to any unauthorized person.  If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and please notify the sender of the error by reply email or by calling Summit Racing Equipment at 330-630-5343, which will enable us to correct our records.


More information about the Linux-PowerEdge mailing list