Reset Search
 

 

Article

X-CM-00 fails to boot with error "ext2: Attempt toFAT: invalid media value (0x00)..."

« Go Back

Information

 
TitleX-CM-00 fails to boot with error "ext2: Attempt toFAT: invalid media value (0x00)..."
Symptoms
  • X-CM-00 fails to boot.
  • Corrupted flash drive.
Booting 'Enterasys Matrix X'

root (hd0,1)
 Filesystem type is ext2fs, partition type 0x00000083
kernel --type=biglinux /mxs_cm.xsi rw root=/dev/hda2 rootfile=mxs_cm.xsi(.ets.d
isk) rootdata=/image console=ttyS0,19200 quiet cca_IOMREV=3
loading kernel from .xsi file
ets: loaded first 8K of linux kernel
   [Linux-bzImage, setup=0x1400, size=0x1c5118]

INIT: version 2.86 booting
Starting udev:                                              [ok]
e2fsck 1.39 (29-May-2006)
fsck.ecramfs: wrong magic
ext2: Attempt toFAT: invalid media value (0x00)
 read block from filesystem resulted in short read while trying to open /dev/hda4
Could this be a zero-length partition?
mount: you must specify the filesystem type
Installing shared libraries                                 [ok]
mkdir: cannot create directory `/var/trace': Read-only file system
mount: mount point /var/trace does not exist
mounting /var/log
mkdir: cannot create directory `/var/log': Read-only file system
mounting using tmpfs
mount: mount point /var/log does not exist
scrubbing: /var/core directory
mkdir: cannot create directory `/var/core': Read-only file system
/ens/rc.d/rcS.d/S19checkcore: line 40: declare: -: syntax error: operand expected (error token is "-")
ls: cannot access /var/core: No such file or directory
No debug files detected

mkdir: cannot create directory `/var/lock': Read-only file system
mkdir: cannot create directory `/var/log': Read-only file system
mkdir: cannot create directory `/var/core': Read-only file system
mkdir: cannot create directory `/var/dhcp': Read-only file system
mkdir: cannot create directory `/var/spool': Read-only file system
mkdir: cannot create directory `/var/spool/cron': No such file or directory
mkdir: cannot create directory `/var/local': Read-only file system
mkdir: cannot create directory `/var/lib': Read-only file system
mkdir: cannot create directory `/var/lib/logrotate': No such file or directory
mkdir: cannot create directory `/var/lib/nfs': No such file or directory
mkdir: cannot create directory `/var/run': Read-only file system
mkdir: cannot create directory `/var/time': Read-only file system
Setting system time from HW clock:  Tue Aug 25 05:26:37 UTC 2015
/ens/rc.d/rcS.d/S34ksyms: line 27: /var/log/kernel.log: No such file or directory
/ens/rc.d/rcS.d/S34ksyms: line 67: /var/log/ksyms.0: No such file or directory
Configuring core dumps                                      [ok]
Setting hostname: cm2                                       [ok]
Starting portmapper portmap                                 [ok]
mkdir: cannot create directory `/var/log': Read-only file system
INIT: Entering runlevel: 1log/syslog.log': No
touch: cannot touch `/var/log/syslog.log': No such file or directory
touch: cannot touch `/var/log/xsupplicant.log': No such file or directory
Starting log daemon syslogd                                 [ok]
Starting klog daemon klogd                                  [ok]
Starting internet superserver: xinetd                       [ok]
touch: cannot touch `/var/lib/nfs/etab': No such file or directory
touch: cannot touch `/var/lib/nfs/rmtab': No such file or directory
exportfs: could not open /var/lib/nfs/etab for locking
exportfs: could not open /var/lib/nfs/etab for locking
exportfs: can't lock /var/lib/nfs/etab for writing
Starting NFS rpc.nfsd                                       []/usr/sbin/rpc.nfsd: chdir(/var/lib/nfs) failed: No such file or directory
                                                            [FAILED]
Starting NFS rpc.mountd                                     []/usr/sbin/rpc.mountd: chdir(/var/lib/nfs) failed: No such file or directory
                                                            [FAILED]
exportfs: could not open /var/lib/nfs/etab for locking
exportfs: can't lock /var/lib/nfs/etab for writing
SNMP Research EMANATE Agent with EPIC Version 16.1.0.5
Copyright 1989-2003 SNMP Research, Inc.
Starting HA policy monitor sham_ppm                         []eos_open
eos_release
                                                            [ok]
IPC nameserver nameserver                                   [ok]
linux_kernel_bde: module license 'Proprietary' taints kernel.
linux-kernel-bde (1859): set DMA retry to infinite on switch device
linux-kernel-bde (1859): set DMA retry to infinite on switch device
initialize broadcom                                         []linux-kernel-bde (1875): _interrupt_connect d 0 _d 0
linux-kernel-bde (1875): _interrupt_connect d 1 _d 1
                                                            [ok]
IPC domainlinks ipccfg                                      [ok]
IPC ping server ipcpingsvr                                  [ok]
Re-configuring core dumps                                   [ok]
Starting crond                                              []/usr/sbin/crond: can't open or create /var/run/crond.pid: No such file or directory
                                                            [FAILED]
Starting application sel_slave                              [ok]
Setting kernel printk console level to 2 (ALERT level)
Setting IPC queue depth to 64
Increasing the max size of socket send/recv buffer to 2MB/4MB
Setting RPC's minimum reserved port to 851
Starting HA replication manager sham_rep                    [ok]
Starting application sel_master                             [ok]
Starting HA arbitration manager sham_arb                    [ok]
Starting application sham_hu                                [ok]
Starting HA role manager sham_role                          [ok]
--- Baseline Initialization Complete ---
--Enterasys System Error Logger: Crash detected--

Saving databaseName = /ens/sbin/sham_arb
 environment - [PID = 2038
tar -cvzf /tmp/cTGID = 2038
oremgr/cm2-sham_Error code = 6
arb-2038-1440480406-v02.00.00.0008H.dbinfo.tz /var/db]
tar: /tmp/coremgr/cm2-sham_arb-2038-1440480406-v02.00.00.0008H.dbinfo.tz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Removing leading `/' from member names
tar: /var/db: Cannot stat: No such file or directory
!! PANIC !! CID 4 [status = 0x80040001]: Panic! File: env.cc, line 342 Database panic: Operation not permitted (1)
The component "sham_arb" (2038:/ens/sbin/sham_arb) has failed with a failure-policy of FAILOVER

flushing                                                    [FAILED]
mkdir: cannot create directory `/var/core': Read-only file system
/ens/init.d/checkcore: line 40: declare: -: syntax error: operand expected (error token is "-")
ls: cannot access /var/core: No such file or directory
clean out recovery logs                                     [ok]
saving /var/log to flash
syncing /var/log                                            []cp: cannot stat `/var/log': No such file or directory
                                                            [ok]
saving /var/trace to flash
syncing /var/trace                                          []cp: cannot stat `/var/trace': No such file or directory
                                                            [ok]
Restarting system.
¦

 
Environment
  • Matrix X.
  • X-CM-00.
  • All firmware versions.
Cause
Corrupted flash drive.
Resolution
Hardware failure.
Submit an RMA through our Support Portal or contact the GTAC for immediate technical assistance.
Submit an RMA Case on the Extreme Portal
Additional notes
Not sure what an RMA is?
For additional information about RMA please read the article Return Material Authorization RMA Process and FAQ

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255