Unsolved

This post is more than 5 years old

11 Posts

10416

June 30th, 2016 12:00

Reimage X200

I inherited a cluster of 3 X200's and 3 NLs.  I have been instructed to reimage due to the sensitivity of the data. (and the system was in pieces when I received. So start from scratch).

I already have an x200 cluster and was able to download several reimage images from 8.0 to 7.1.1x. All the versions booted off the USB but failed. I then tried 7.0.2.9 which got me further than the previous versions however ultimately failed with "IMDD/Flash start failed" and sitting at the # prompt with very little capability. 

I've since found out that the version previously running on the cluster was 6.5.4.2.  I'm unable to find the re-image software for 6.5.4.2 due to the oldest version i could find under "downloads" was 7.0.

Does anyone have a 6.5 reimage image or an idea of the error above.? "IMDD/Flash start failed"   I've used a 512MB and a 1 GB Sandisk Cruzer USB.  Both return same error. 

4 Apprentice

 • 

637 Posts

June 30th, 2016 16:00

You checked KB 323035 : How to create a bootable image of OneFS on a USB flash drive           


https://support.emc.com/kb/323035

11 Posts

July 1st, 2016 05:00

Yes, Phil, I've used the document to build a USB drive.  That's how I've gotten this far.   I'm thinking that since the inherited Cluster was firmware version 6.5.4.2 something, I have to use the same re-image image. (i.e. you can't re-image a 6.5x cluster with 8.0x).

So I'm looking for a 6.5.4.2 image.  Just need someone to confirm my suspicision and possibly offer up the image.

252 Posts

July 1st, 2016 08:00

Hi wpetering,

The issue sounds like a problem with the burn itself. X200s use boot drives not IMDD boot, so you shouldn't be seeing any errors related to that. The error suggests that the image does not ever get to the point of booting, so not likely an issue with the image itself. You should be able to reimage to the latest supported version for the node type you have. The link Phil Lam provided is the most current instruction for creating the bootable image.

11 Posts

July 1st, 2016 09:00

I'm confident it's booting off the USB drive. During the boot process, the USB drive is flashing (i.e. being read) and during the boot it even shows the image version its using (OneFS_v7.0.2.9 etc).  My cluster won't boot but this is booting so I know its the USB.  I get to a root prompt and its the file system on the USB when I do an "ls".   I'd post a screen capture however, I'm waiting on approval to do so.

Plus other versions I've tried, the boot prompted me that it will wipe the system completely, "do you want to do this?".  That's not a normal boot process.

Phil's link is what I've used to burn several versions of the re-image.

Thanks. Keep the ideas coming.

4 Apprentice

 • 

637 Posts

July 1st, 2016 13:00

wpetering


"the boot prompted me that it will wipe the system completely"

I thought that's what you wanted to do. Go ahead, and it will reformat the drives.

65 Posts

July 1st, 2016 15:00

have you been able to try a reformat, its pretty much the same as re-image only it takes it back to factory defaults.

if you get to a command prompt try using:

#isi_reformat_node

65 Posts

July 1st, 2016 15:00

also depending on how you made the image can matter too. I have heard that MAC works better but that is subjective.

11 Posts

July 5th, 2016 13:00

when i get to the "#" prompt, there is no "Isi_reformat_node" command.  I can do things like "isi config", "isi version".  I think this mode is a stripped version of a live disk (if that's possible).  I have to figure out a way to post the logs.  Thanks.

11 Posts

July 5th, 2016 13:00

Sorry, I didn't complete that sentence...."the boot prompted me that it will wipe the system completely" and when I said "yes" it quickly dropped me into the "OK" prompt.  As I stated earlier, all the re image versions I tried except for 7.0.2.9 fail.  7.0.2.9 drops me into a menu:   1) recover mode, 2) continue booting & 3) Reboot.  Options 1 & 2 drop me to the root prompt, but its a limited amount of commands I can run.  (almost like a stripped live version.)  I can't run "isi_reformat_node" because that command doesn't exist from this mode.

65 Posts

July 5th, 2016 18:00

just to clarify,

the prompts and errors you are getting seem related to a few possible different things.

1. possibly bad image burn. you should not need 6.5 it is no longer supported (why you cant find an image) these nodes are recent enough they definitely are fine with running/imaging to 7.x I would recommend 7.2.1.2 personally.

2. possible that you have bad boot disks as I have seen those error when it cant write to the boot disk and fails

you have removed the usb stick at this point right? the prompt you are getting will not allow you to run most isi commands as it has not mounted /IFS and has not completed the re-image process (speculative based on information)

below is the procedure after you have a good burn of an image can you confirm you are using this method?

also for your convenience providing the link to 7.2.1.2 with the md5 hash so you can confirm the image is being downloaded whole and good to your box.

reimage file location:

https://download.emc.com/downloads/DL66066_OneFS_7.2.1.2_reimaging_file_for_USB_flash_drive.gz?source=OLS

md5 hash:  d6b68257a27752c00fea1a90c263a943

Introduction

This article describes how to reimage an Isilon node using a USB flash drive.

CAUTION!
This procedure should only be performed on a node that is not currently a member of a cluster. This includes a node that requires a new installation of OneFS or a node that has been completely smartfailed and removed from an active cluster.

Procedure

CAUTION!
Performing this procedure will erase all data on the node.

  1. Confirm that the node is not joined to the cluster using the OneFS web administration interface and checking the cluster status, or by running the isi statuscommand from the command line. For more information, see the "View node status" section of the OneFS Administration Guide (for OneFS 6.5 and earlier, see the OneFS User Guide).
  2. Connect to the management port of the node using a null modem cable. For additional information, see Isilon: How to connect to the management port of a node,16744 .
  3. If the node is already powered off, proceed to Step 4; otherwise, do one of the following:
    • If the node is powered on and displays a login prompt, log on using the "root" account and run the following command:

      shutdown -p now
    • If the node is at the configuration wizard, select option 3 to Exit wizard and configure manually. At the >>> prompt, type shutdown to power down the node.
  4. Insert the USB flash drive into one of the two USB ports on the back of the node.
    NOTE
    Some node models do not have enough space to fit both a USB flash drive and a null modem cable. You might need a USB extension cable to plug the USB flash drive into.
  5. Power on the node by pressing the power button. The node should mount the USB flash drive and start up from it.
  6. At the prompt asking Are you sure you want to proceed?, do one of the following:
    • If you do not want to reimage the node, type no, press ENTER, and then complete the following steps:
      1. At the prompt asking you to confirm a new path for shell, press ENTER to accept the default /bin/sh.
      2. Power down the node by running the following command:
        /sbin/shutdown -p now
      3. When the node has powered down, remove the USB flash drive.
    • If you want to reimage the node, type yes and press ENTER.
      The system displays a Please wait message. When the process completes, the node powers down.
  7. When the node has powered down, remove the USB flash drive.
  8. Power on the node by pressing the power button.
  9. At the prompt asking you to confirm that you want to format the /ifs partition on all drives, type yes and press ENTER.
    IMPORTANT!
    If you do not type yes, the node does not fully reimage itself and some previous configuration data might remain on the system.

    A series of dots fills the screen until the format is complete. When finished, the node returns to the factory default prompt asking for a new root password.

11 Posts

July 8th, 2016 14:00

D_Tracy, Thanks for the procedures. It verified exactly what I was doing, however It's still failing.  I was able to generate a log to help diagnose this issue.  Cheers.

/boot/kernel.amd64/kernel text=Oxa28558 data=Ox140580+0x25b3a8 syms=[Ox8+0x16495 8+0x8+0x20374f]

/boot/kernel.amd64/if_em.ko size Ox479e0 at Ox152c000

/boot/kernel.amd64/giconv.ko  size Ox31568 at Ox1574000

/boot/kernel.amd64/if_bxe.ko size Ox1fa480 at Ox15a6000

/boot/kernel.amd64/if_cxgb.ko size Ox4c708 at Ox17a1000

/boot/kernel.amd64/t5fw_cfg.ko size Ox7c770 at Ox17ee000

/boot/kernel.amd64/if_cxgbe.ko size Ox41a70 at Ox186b000

/boot/kernel.amd64/ixgbe.ko size Ox48190 at Ox18ad000

/boot/kernel.amd64/imdd.ko size Ox147a8 at Ox18f6000

/boot/kernel.amd64/mlx4_core.ko size Ox46a98 at Ox190b000

/boot/kernel.amd64/mlx4_ib.ko size Ox29af8 at Ox1952000

/boot/kernel.amd64/mpt.ko size Ox3d438 at Ox197c000

/boot/kernel.amd64/mps.ko size Ox29778 at Ox19ba000

/boot/kernel.amd64/mthca. ko size Oxd5988 at Ox19e4000

/boot/kernel.amd64/smbus.ko size Ox2738 at Ox1aba000

/boot/kernel.amd64/ipmi.ko size Ox10938 at Ox1abd000

/boot/kernel.amd64/nfscommon.ko sizeOx37660 at Ox1ace000 loading requiredmodule 'kgssapi_krb5'

/boot/kernel.amd64/kgssapi_krb5.ko sizeOxdddO at Ox1b06000 loading requiredmodule 'rc4'

/boot/kernel.amd64/rc4.ko sizeOxe60 at Ox1b14000 loadingrequired module 'kgssapi'

/boot/kernel.amd64/kgssapi.ko sizeOx1d0d8 at Ox1b15000 loading requiredmodule 'krpc'

/boot/kernel.amd64/krpc.ko size Ox2df48 at Ox1b33000

currdev = disk0s1a:

Hit [Enter) to boot immediately, or any other key forcommand prompt. Booting[/boot/kernel.amd64/kernel]. ..

GOB:debugports:sio GOB:currentport:sio

KDB:debuggerbackends: ddbgdb KDB:currentbackend: ddb

Copyright (c) 2001-2014 EMC Corporation. AllRights Reserved. Copyright (c) 1992-2011 TheFreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

FreeBSD is a registered trademark of The FreeBSD Foundation.

lsilon OneFS v7.2.1.2 B_7_2_1_ 131(RELEASE): Ox702015000200083: Mon Feb 819:08:54 GMT 2016

root@sea-build7-02:/b/mnt/obj/b/mnt/src/sys/IQ.amd64.re1ease clang version 3.3 (tags/RELEASE_33/final)  amd64

kload: Normal boot

lsilon: model 26 family 6 stepping 5;highmem disabled. MEMGUARDDEBUGGING ALLOCATORINITIALIZED:

MEMGUARD map base:Oxffffff8000400000 MEMGUARD map limit:Oxffffff87ae548000 MEMGUARD map size:32212256 KBytes

Timecounter "i8254" frequency 1193182 Hz quality O

CPU: lntel(R) Xeon(R) CPU E5504  @ 2.00GHz (2000.09-MHz KB-class CPU)

Origin = "Genuinelntel"  Id = Ox106a5  Family = 6 Model = 1a Stepping = 5

Features=Oxbfebfbff

Features2=0x9ce3bd

E4.1,SSE4.2,POPCNT>

AMO Features=Ox28100800 NX,RDTSCP, LM>

AMO Features2=0x1

TSC: P-state invariant

usable memory = 51502178304 (49116 MB)

avail memory =48142155776 (45911 MB) ACPI APIC Table:<010511 APIC2026>

FreeBSD/SMP: Multiprocessor System Detected:4 CPUs FreeBSD/SMP: 1 package{s) x 4 core{s)

cpuO{BSP):APICID: 0 cpu1{AP):APICID: 2 cpu2{AP):APICID: 4 cpu3{AP):APICID: 6

ioapicO:ChangingAPIC ID to 1 ioapic1:ChangingAPIC ID to 3

ioapicO 2.0> irqs 0-23 on motherboard ioapic1 2.0> irqs 24-47 on motherboard imdd0-9: lsilon Mirrored Disk Driver

kload_init: has notpreallocated temporaryspace cryptosoftO: crypto> on motherboard acpiO: > on motherboard

acpiO: [ITHREAD]

acpiO: Power Button {fixed)

acpiO: reservation of 0, aOOOO (3) failed

acpiO: reservation of 100000, 7ff00000 (3) failed

Timecounter "ACPl-fast" frequency 3579545 Hzquality 1000 acpi_timerO: <24-bit timer at3.579545MHz> port Ox808-0x80b on acpiO

acpi_hpetO: Precision Event Timer> iomem Oxfed00000-0xfed003ff on acpiO Timecounter "HPET" frequency 14318180 Hz quality 2000

pcibO: Host-PCI bridge> port Oxcf8-0xcff on acpiO pciO: PCI bus> on pcibO

pcib1: PCl-PCI bridge> at device 1.0 on pciO pci9: PCI bus> on pcib1

pcib2: PCl-PCI bridge> at device 3.0 on pciO pci8: PCI bus> on pcib2

cxgbcO: T320, 2 ports> mem Oxfaf7e000-0xfaf7efff,Oxfaf7f000-0xfaf7ffff irq 24 at device 0.0 on pci8

PHY O i2c read ofdev.addr aO.O timed out cxgbcO: ael2005 phy:modtype:O

PHY 1 i2c read ofdev.addr aO.O timed out cxgbcO: ael2005 phy:modtype:O

cxgbcO: using MSl-X interrupts (9 vectors)

found old FW minor version{7.8), driver compiledfor version 7.11 cxgbcO: firmware needs to beupdated to version 7.11.0

cxgbO: 0 1OGBASE-R> on cxgbcO cxgbO: Ethernet address: 00:07:43:07:db: 15 cxgb1: 1 1OGBASE-R> on cxgbcO cxgb1: Ethernet address: 00:07:43:07:db:16 cxgbcO: Firmware Version 7.8.0

pcib3: PCl-PCI bridge> at device 5.0 on pciO pci7: PCI bus> on pcib3

pcib4: PCl-PCI bridge> at device 7.0 on pciO pci6: PCI bus> on pcib4

mthcaO: Belknap> mem OxfaeOOOOO-Oxfaefffff,Oxbf800000-0xbfffffff,OxcOOOOOOO-Oxdfffffff irq 30 at device 0.0 on pci6

mthcaO: [ITHREAD]

mthcaO:[ITHREAD] mthcaO:[ITHREAD]

mthcaO: 3 MSl-X vectors enabled for pci_dev:Oxffffff0171a3db00,mdev:Oxffffff016f66e000 [mthca_main.c:275](pid O="swapper")(tid=100000) No PCl-Xcapability, not setting RBC.

mthcaO: register OxF3C14 value is c0632713

GPIO[ GPIO[

Data] -> eO 00 43 00 d4 8d 02 Of : 004300e0 Of028dd4 :e0000300d48d020f Dir] -> eO 00 00 00 00 00 00 70 : OOOOOOeO70000000 : e000000000000070

GPIO[ GPIO[

Data] -> eO 00 43 00 d4 8d 00 Of : 004300e0 Of008dd4 :e0000300d48d000f Dir] -> eO 00 00 00 00 00 04 70 : OOOOOOeO70040000 : e000000000000470

mthca:dir=Oxe0004300d48d020f ->fsr=1  pwr=O mthca: SYS_ENtype = 3 / 80000000

mthca: catastrophic errors will be reported atOxfae82a50 Ox82a50 (Ox10) mthca: release fwdetected

mthcaO: Message data prepended

mthcaO: msgbuf region reserved atOxdf5aOOOO (131072 bytes) pcib5: PCl-PCI bridge> at device 9.0 on pciO

pci5: PCI bus> on pcib5

mpsO: SAS2008> port OxeOOO-OxeOff mem Oxfad3c000-0xfad3ffff,Oxfad40000-0xfad7ffff irq 32 at device 0.0 on pci5

mpsO:Firmware:07.00.00.00 mpsO:IOCCapabilities:

1285c DiagTrace, SnapBuf, EEDP,TransRetry, EventReplay, Hostoisc> mpsO: enabling unmapped io

mpsO:mpssas_startup_incrementfreezing simq isi_sim_init mpsO

mpsO: [FILTER+ITHREAD]

pciO: peripheral, interrupt controller> at device 20.0(no driver attached) pciO: peripheral, interruptcontroller> at device 20.1 (no driver attached) pciO: peripheral, interrupt controller> at device 20.2 (no driverattached) pciO: peripheral, interrupt controller> atdevice 20.3 (no driver attached) pciO: peripheral>at device 22.0 (no driver attached)

pciO: peripheral> at device22.1 (no driver attached) pciO: peripheral> at device 22.2 (no driverattached) pciO: peripheral> atdevice 22.3 (no driver attached) pciO: peripheral> at device 22.4 (nodriver attached) pciO: peripheral> at device 22.5 (no driverattached) pciO: peripheral> atdevice 22.6 (no driver attached) pciO: peripheral> at device 22.7 (nodriver attached)

uhciO: (generic) USB controller> port Oxbe80-0xbe9f irq 16 at device 26.0 on pciO uhciO: [GIANT-LOCKED]

uhciO: [ITHREAD]

usbO: (generic) USB controller> on uhciO usbO: USB revision 1.0

uhubO: UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usbO uhubO: 2 ports with 2 removable, self powered

uhci1: (generic) USB controller> port Oxbe20-0xbe3f irq 21 at device 26.1 on pciO uhci1: [GIANT-LOCKED]

uhci1: [!THREAD]

usb1: (generic) USB controller> on uhci1 usb1: USB revision 1.0

uhub1: UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered

uhci2: (generic) USB controller> port OxbdcO-Oxbddf irq 19 at device 26.2 on pciO uhci2: [GIANT-LOCKED]

uhci2: [ITHREAD]

usb2: (generic) USB controller> on uhci2 usb2: USB revision 1.0

uhub2: UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 uhub2: 2 ports with 2 removable, self powered

ehciO: (generic) USB 2.0 controller> mem Oxfaaf6000-0xfaaf63ff irq 18 at device 26.7 on pciO ehciO: [GIANT-LOCKED]

ehciO: [ITHREAD]

usb3: EHCI version 1.0

usb3: companion controllers, 2 portseach: usbO usb1 usb2 usb3: (generic) USB 2.0 controller> on ehciO

usb3: USB revision 2.0

uhub3: EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3 uhub3: 6 ports with 6 removable, self powered

pcib6: PCl-PCI bridge> irq 17 at device 28.0 on pciO pci2: PCI bus> on pcib6

pcib7: PCl-PCI bridge> irq 17 at device 28.4 on pciO pci3: PCI bus> on pcib7

emO: PR0/1000 Network Connection 6.9.6> port Oxcf80-0xcf9f mem OxfabeOOOO-Oxfabfffff,OxfabdcOOO-Oxfabdffff irq 16 at device 0.0 on pci3

emO: Using MSIX interrupts

emO: em_flow_control_tunable is: 0 andem_flow_control_sysctl is O emO: Disablinghardware flow control

emO:[ITHREAD] emO:[ITHREAD] emO:[ITHREAD]

emO: Ethernet address: 00:25:90:3c:5d:74

pcib8: PCl-PCI bridge> irq 16 at device 28.5 on pciO pci4: PCI bus> on pcib8

em1: PR0/1000 Network Connection 6.9.6> port Oxdf80-0xdf9f mem OxfaceOOOO-Oxfacfffff,OxfacclcOOO-Oxfacdffff irq 17 at device 0.0 on pci4

em1: Using MSIX interrupts

em1: em_flow_control_tunable is: 0 andem_flow_control_sysctl is 0 em1: Disabling hardwareflow control

em1:[ITHREAD] em1:[ITHREAD] em1:[ITHREAD]

em1: Ethernet address: 00:25:90:3c:5d:75

uhci3: (generic) USB controller> port Oxbf00-0xbf1f irq 23 at device 29.0 on pciO uhci3: [GIANT-LOCKED]

uhci3: [ITHREAD]

usb4: (generic) USB controller> on uhci3 usb4: USB revision 1.0

uhub4: UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4 uhub4: 2 ports with 2 removable, self powered

uhci4: (generic) USB controller> port OxbecO-Oxbedf irq 19 at device 29.1 on pciO uhci4: [GIANT-LOCKED]

uhci4: [ITHREAD]

usb5: (generic) USB controller> on uhci4 usb5: USB revision 1.0

uhub5: UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5 uhub5: 2 ports with 2 removable, self powered

uhci5: (generic) USB controller> port OxbeaO-Oxbebf irq 18 at device 29.2 on pciO uhci5: [GIANT-LOCKED]

uhci5: [ITHREAD]

usb6: (generic) USB controller> on uhci5 usb6: USB revision 1.0

uhub6: UHCI root hub, class 9/0, rev 1.0011.00, addr 1> on usb6 uhub6: 2 ports with 2 removable, self powered

ehci1: (generic) USB 2.0 controller> mem Oxfaaf8000-0xfaaf83ff irq 23 at device 29.7 on pciO ehci1: [GIANT-LOCKED]

ehci1: [ITHREAD]

usb7: EHCI version 1.0

usb7: companion controllers, 2 portseach: usb4 usb5 usb6 usb7: (generic) USB 2.0 controller> on ehci1

usb7: USB revision 2.0

uhub7: root hub, class 9/0, rev 2.00/1.00, addr 1> on usb7 uhub7: 6 ports with 6 removable, self powered

uhub8: Ox05e3 USB2.0 Hub, class 9/0, rev 2.00/77.63, addr 2> on uhub7 uhub8: single transaction translator

uhub8: 4 ports with 4 removable, self powered

umassO: Corporation U3 Cruzer Micro, class 010, rev 2.00/0.10, addr 3> on uhub8 pcib9: PCl-PCI bridge> at device 30.0 on pciO

pci1: PCI bus> on pcib9

vgapciO: display>  mem Oxf8000000-0xf8ffffff, Oxf9ffc000-0xf9ffffff, OxfaOOOOOO-Oxfa 7fffff irq 16 at device 3.0 on pci1

isabO: bridge> at device 31.0 on pciO isaO: on isabO

atapciO: 10 SATA300 controller> port

Oxbff0-0xbff7, Oxbf8c-Oxbf8f, OxbfeO-Oxbfe 7,Oxbf88-0xbf8b, OxbfaO-Oxbfaf, Oxbf90-0xbf9f irq 19 at device

31.2 on pciO

atapciO: [GIANT-LOCKED]

atapciO: [ITHREAD]

ata2:channel#0onatapciO ata2:[GIANT-LOCKED] ata2:[ITHREAD]

ata3:channel#1onatapciO ata3:[GIANT-LOCKED] ata3:[ITHREAD]

pciO: bus, SMBus> at device 31.3 (no driver attached) atapci 1: 10 SATA300 controller> port

Oxbf80-0xbf87, Oxbf7c-Oxbf7f,Oxbf28-0xbf2f, Oxbf24-0xbf27, Oxbf60-0xbf6f, Oxbf30-0xbf3f irq 19 at device

31.5 on pciO

atapci1: [GIANT-LOCKED]

atapci1: [ITHREAD]

ata4:channel#0onatapci1 ata4:  [GIANT-LOCKED] ata4:[ITHREAD]

ata5:channel#1onatapci1 ata5:  [GIANT-LOCKED] ata5:[ITHREAD]

acpi_buttonO: Button> on acpiO

sioO: configured irq 4 not inbitmap of probed irqs 0 sioO: port may not beenabled

sioO: configured irq 4 not inbitmap of probed irqs O sioO: port may not be enabled

sioO: <16550A-compatible COM port> port Ox3f8-0x3ff irq 4 flags Ox90 on acpiO sioO: type 16550A, console

sioO: [FILTER]

sio1: configured irq 3 not in bitmap of probed irqs O

sio1: port may not be enabled

sio1: configured irq 3 not inbitmap of probed irqs 0 sio1:port may not be enabled

sio1: <16550A-compatible COM port> port Ox2f8-0x2ff irq 3 on acpiO sio1: type 16550A

sio1: [FILTER]

sio2: configured irq 5 not inbitmap of probed irqs 0 sio2:port may not be enabled

sio2: configured irq 5 not inbitmap of probed irqs 0 sio2:port may not be enabled

sio2: <16550A-compatible COM port> port Ox3e8-0x3ef irq 5 on acpiO sio2: type 16550A

sio2: [FILTER]

cpuO: CPU> on acpiO

ACPI Warning (tbutils-0241): Incorrect checksum in table [OEMB] - F5, should be F2(20070320] acpi_throttleO: CPU Throttling> on cpuO

cpu1: CPU> on acpiO

acpi_throttle1: CPU Throttling> on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: CPU> on acpiO

cpu3: CPU> on acpiO

qpiO: system bus> on motherboard

pcib10: Host-PCI bridge> pcibus 255 on qpiO pci255: bus> on pcib10

ormO: Option ROM> at iomem Oxc0000-0xc7fff on isaO scO: console> at flags Ox100 on isaO

scO: VGA <16 virtual consoles, flags=Ox100>

vgaO: ISA VGA> at port Ox3c0-0x3df iomem OxaOOOO-Oxbffff on isaO ipmiO: System Interface> on isaO

ipmiO: KCS mode found at io Oxca2alignment Ox1 on isa ataO at port Ox1f0-0x1f7,0x3f6 irq 14 on isaO

ataO:[GIANT-LOCKED] ataO:[ITHREAD]

ata1 at port Ox170-0x177,0x376 irq 15 on isaO ata1: [GIANT-LOCKED]

ata1: [ITHREAD]

atkbdcO: controller (i8042)> at port Ox60,0x64 on isaO Timecounter "TSC" frequency 2000085376 Hz quality 2500 Timecounters tick every 10.000 msec

ad4:lun4 ->(phys)unit0 ad4:lun4 ->(phys)unit0

ad4: SSD P4 8GB/SSD 8.10, SN:112841300584, 7641MB SATA150> on ata2-master

ad7:lun7 ->(phys)unit1 ad7:lun7 ->(phys)unit1

ad7: SSD P4 8GB/SSD 8.10, SN:112841301428, 7641MB SATA150> on ata3-slave

mpsO: mps_send_portenable

ipmiO: IPMI device rev. 1, firmware rev.2.2, version 2.0 ipmiO: Number ofchannels 2

ipmiO: Attached watchdog

mpsO: target 0 handle 0 changed linkrate fromOxO to OxO, status Ox3 mpsO: target 0 handle 0changed linkrate from OxO to OxO, status Ox3 mpsO: target 0 handle 0 changed linkrate fromOxO to OxO, status Ox3 mpsO: target 0 handle 0changed linkrate from OxO to OxO, status Ox3 mpsO: target O handle 0 changed linkrate fromOxO to OxO, status Ox3 mpsO: target 0 handle 0changed linkrate from OxO to OxO, status Ox3

mpsO: target O handle 0 changed linkratefrom OxO to OxO, status Ox3 mpsO: target 0handle 0 changed linkrate from OxO to OxO,status Ox3 mpsO: target 0 handle 0 changedlinkrate from OxO to OxO, status Ox3 mpsO:target 0 handle 0 changed linkrate from OxOto OxO, status Ox3 mpsO: target 0 handle 0changed linkrate from OxO to OxO, statusOx3 mpsO: target O handle 0 changedlinkrate from OxO to OxO, status Ox3 mpsO:target 0 handle 0 changed linkrate from OxOto OxO, status Ox3 mpsO: target 0 handle 0changed linkrate from OxO to OxO, statusOx3 mpsO: target 0 handle 0 changedlinkrate from OxO to OxO, status Ox3 mpsO:target 0 handle 0 phy change storm, 15changes in 2 seconds mpsO:mpssas_alloc_tm freezing simq

mpsO: target O handle 0 changed linkratefrom OxO to OxO, status Ox3 mpsO: target 0handle 0 changed linkrate from OxO to OxO,status Ox3 mpsO: phy storm reset aborted 0commands

mpsO:mpssas_free_tm  releasing simq mpsO: LSIexpander detected

mpsO: Assigned target id 120 to bOOOOOOObf>

mpsO: Found device <1902 ,Edge  Expander> <6.0Gbps> <2/0>

<1/0> bOOOOOOObf>

mpsO: Assigned target id 100 to

mpsO: Found device <4451 ,End Device> <6.0Gbps> <210>

<9/24> bOOOOOOObd>

isi_sim_add_disk sim mpsO target 100 exp 9phy 24 path O bus O mpsO:mps_startup_complete

mpsO: disestablish config intrhook

mpsO:mpssas_startup_decrementreleasing simq ndmp_sa: version20090116

sesO at mpsO bus 0 target 100 lun 0

sesO: SAS2X24 0604> Fixed Enclosure Services SCSl-5 device sesO: 600.000MB/s transfers

sesO: SCSl-3 SES Device

Initializingcompression forpanic dumps. SMP: AP CPU #1Launched!

CPU: lntel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.09-MHz KB-class CPU)

Origin = "Genuinelntel" Id = Ox106a5 Family = Model = 1a  Stepping = 5

Features=Oxbfebfbff

Features2=0x9ce3bd

AMO Features=Ox2B 1OOBOO NX,RDTSCP,LM>

AMOFeatures2=0x1 TSC: P-state invariant

SMP: AP CPU #3 Launched!

CPU: lntel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.09-MHz KB-class CPU)

Origin = "Genuinelntel" Id = Ox106a5 Family = Model = 1a Stepping = 5

Features=Oxbfebfbff DE,PSE,TSC, MSR,PAE,MCE,CXB,APIC,SEP ,MTRR,PGE,MCA,CMOV, PAT,PSE36,CLFLUSH,DTS,ACPl,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

Features2=0x9ce3bd POPCNT>

AMO Features=Ox2B 1OOBOO NX ,RDTSCP ,LM>

AMOFeatures2=0x1 TSC: P-state invariant

SMP: AP CPU #2 Launched!

CPU: lntel(R) Xeon(R) CPU E5504  @ 2.00GHz (2000.09-MHz KB-class CPU)

Origin = "Genuinelntel" Id = Ox106a5 Family = Model = 1a Stepping = 5

Features=Oxbfebfbff

Features2=0x9ce3bd POPCNT>

AMO Features=Ox28100800 NX,RDTSCP,LM>

AMO Features2=0x1

TSC: P-state invariant

daO at umass-simO bus 0 target 0 lun O

daO: U3 Cruzer Micro, FW:3.21> SCSl-2 device daO: 40.000MB/s transfers

daO: 973MB (1994385 blks)

GEOM: daO: the primary GPT table is corrupt or invalid.

GEOM: daO: using the secondary instead -- recovery stronglyadvised. currdev=disk0s1 a:

disk_id = 0, partition = a

/dev/da0s1:f0x11051pO id=O Disk tomountfrom is:/dev/da0s1a

Disk to mountfrom is:ufs:da0s1a Trying to mountroot from ufs:da0s1a

(pid 1="swapper") Time stepped from 37.023415709 to 1468005101.000001084 (1468005101.000000000)

(pid 1="swapper") Time stepped from 1468005101.011810343 to1468005272.000002359 (1468005272. 000000000)

starting

Executing script isi_init_config

Executing script isi_module_init

Executing script isi_baud_init Configuring console port baudrate...   115200

2016-07-08T19:14:32Z ifconfig: Configure: /sbin/ifconfig loO 127.0.0.1 netmask255.0.0.0 up kern.cam.log_access_denied_no_rights: O -> 1

Loadingallmodules kldloadcpuctl kldloadfcdm

kldloadib_nvram kldloadib_user kldloadif_lagg kldloadisi_dspcom kldloadisi_i2c kldloadisp

kldloadispfw kldloadrnv kldloadInv kldloadsdp kldloadacpi_sel

Fibre Channel DeviceManager (fcdm) isloaded ib_nvram:initialization complete

[nvram_ib.c: 1090](pid 134="nvram connection th")(tid=100126)Trying restart [nvram_ib.c:210](pid 134="nvram connection th")(tid=100126) NVRAM started on lid O ibO: WARNING: usingobsoleted if_watchdog interface

ib1: WARNING: using obsoleted  if_watchdog interface sel: loaded

isi i2c: found Intel ICH10 SMBus Controller

isi=i2c0 port Ox400-0x41f mem OxfaafaOOO-OxfaafaOff irq 18.atdevice 31.3 on pciO isi_i2c0: [GIANT-LOCKED]

isi_i2c0: [ITHREAD]

[sdp_conn.c: 1649](pid 132="kldload")(tid=100099) HCA supports 59 s/g per WR.Consider increasing SOP_MAX_ GS (28).

registered firmwareset registered firmwareset registered firmwareset registered firmwareset 1080_it> registered firmware set 12160> registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set registered firmware set Completed module load

Executing script isi_bootdisk_init Executing IMDD/Flash bootdisk startup... Discovering mount information

Detecting currentimdd informationInitializing /dev/imddO

Initializing/dev/imdd1 Initializing/dev/imdd2 Initializing/dev/imdd3 Initializing/dev/imdd4 Initializing/dev/imdd6 Initializing/dev/imdd5 Initializing/dev/imdd7 Discoveringavailabledevices including/dev/daO

including/dev/ad7 including/dev/ad4

/dev/adO: Checking for device present.

/dev/adO: Device not present

/dev/imddO my mountpoint has already beentaken by da0s1a Attaching devices to file imdds

/dev/imddO my mountpoint has already been taken by da0s1a

/dev/imddO needs to remirror children

/dev/imddO composed of 0 partitions has been created for I

/dev/imdd1 needs to remirror children

/dev/imdd1 composed of 0 partitions has been created for /var

/dev/imdd2 needs to remirror children

/dev/imdd2 composed of 0 partitions has been created for /var/crash

/dev/imdd3 needs to remirror children

/dev/imdd3 composed of 0 partitions has been created for /usr/update/root

/dev/imdd4 needs to remirror children

/dev/imdd4 composed of 0 partitions has been created for /usr/update/var

/dev/imdd6 needs to remirror children

/dev/imdd6 composed of 0 partitions has beencreated for dump

/dev/imdd5 needs to remirror children

/dev/imdd5 composed of 0 partitions has been created for/var/journal Attaching devices to stack dump imdds

/dev/imdd7 needs to remirror children

/dev/imdd7 composed of 0 partitions hasbeen created for sdump Repairingunformatted devices

Panic: Couldn'tmount rootIMDD/Flash startfailed

Please contact EMC Customer Support:

United States: 1 800 782 4362 (1 800 SVC 4EMC)

Canada: 1 800 543 4782 (1 800 543 4SVC)

Worldwide Country Code: 1 508 497 7901

Command Options:

1)     Enter recovery shell

2)     Continue booting

3)     Reboot option>

117 Posts

July 9th, 2016 03:00

You probably have a bad boot disk, you'll have to get support involved to replace it.

--

Sent from my iPhone

11 Posts

July 11th, 2016 07:00

Thanks Yan and D_Tracy.  I have 5 other nodes and I will give those a try.

Question:  Is the "Boot disk" part of the 12 drives? or is it onboard ROM?  We moved the chassis' by truck but had all the disks shipped separately by FedX.  When the drives were put back into the chassis (in the correct order) we got a lot of red lights.  Thinking FedX kicked the crap out of our boxes (big surprise huh?)

65 Posts

July 11th, 2016 07:00

Hey wpetering,

To Echo Yan, this looks like a boot disk issue to me. I would recommend opening a ticket with that boot log information but the tell all is the last little bit. its actually creating a panic when trying to mirror the boot disk.

Panic: Couldn'tmount rootIMDD/Flash startfailed

/dev/imdd5 composed of 0 partitions has been created for/var/journal Attaching devices to stackdump imdds

/dev/imdd7 needs to remirror children

/dev/imdd7 composed of 0 partitions hasbeen created for sdump Repairingunformatted devices

Panic: Couldn'tmount rootIMDD/Flash startfailed

Please contact EMC Customer Support:

United States: 1 800 782 4362 (1 800 SVC 4EMC)

Canada: 1 800 543 4782 (1 800 543 4SVC)

Worldwide Country Code: 1 508 497 7901

Have you had this issue on any other nodes or is it just this one? you may want to try other nodes just so you can get them all in one go if needed on more than one node. If these were older nodes they likely do not have the netlist smart boot disks that give proactive warnings on the wear life threshold. so new boot disks are a good idea for that alone. it will notify you on 7.2.1 when the life expectancy of these disks reaches a point where we know it is more likely to fail due to the number of writes. naturally you need to have /ifs mounted for those to work but that should resolve this issue.

Regards,

D_Tracy

117 Posts

July 11th, 2016 12:00

The boot disks in the X200 are on-board mSATA SSDs, they are separate from the 12 drives.

0 events found

No Events found!

Top