• October 17, 2018, 07:41:37 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: WS5100 Failed  (Read 2954 times)

0 Members and 1 Guest are viewing this topic.

Offline hnorbi

  • Rookie
  • **
  • Posts: 13
WS5100 Failed
« on: January 04, 2017, 07:06:19 AM »
I have big problem :/
After an accidentaly power loss my WS5100 won't start up.

On cli:
"
LILO 22.6-CCB boot:
Loading 3.2.0.0-040R..........................
BIOS data check successful
Welcome to WS5100
Starting daemons............
LILO 22.6-CCB boot:
Loading 3.2.0.0-040R..........................
BIOS data check successful
Welcome to WS5100
Starting daemons............
LILO 22.6-CCB boot:
"
(infinitive)

I tried to do an fsck:

"
/ # e2fsck -f -p /dev/hda1
/boot: recovering journal
/boot: 17/1536 files (5.9% non-contiguous), 3969/6128 blocks
/ # e2fsck -f -p /dev/hda2
/etc2: recovering journal
/etc2: 51/3456 files (2.0% non-contiguous), 1536/13824 blocks
/ # e2fsck -f -p /dev/hda3
e2fsck: while trying to open /dev/hda3
/dev/hda3:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

e2fsck:
/ # e2fsck -f -p /dev/hda4
e2fsck: while trying to open /dev/hda4
Could this be a zero-length partition?
e2fsck:
/ # e2fsck -f -p /dev/hda5
/img1: 2911/24752 files (1.5% non-contiguous), 69887/98800 blocks
/ # e2fsck -f -p /dev/hda6
/dev/hda6: 3026/24752 files (1.5% non-contiguous), 71929/98800 blocks
/ # e2fsck -f -p /dev/hda7
e2fsck: while trying to open /dev/hda7
/dev/hda7:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

e2fsck:
/ # e2fsck -f -p /dev/hda8
/flash: recovering journal
/flash: 22/4944 files (0.0% non-contiguous), 1689/19696 blocks
"

but the problem still exists :/

The Dmesg output:
"/ # dmesg
Linux version 2.6.16.51-ws-symbol (wios-eng@wios-build) (gcc version 3.4.5) #1
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000000ff40000 (usable)
 BIOS-e820: 000000000ff40000 - 000000000ff50000 (ACPI data)
 BIOS-e820: 000000000ff50000 - 0000000010000000 (ACPI NVS)
 BIOS-e820: 00000000fec80000 - 00000000fec81000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65344
  DMA zone: 4096 pages, LIFO batch:0
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 61248 pages, LIFO batch:15
  HighMem zone: 0 pages, LIFO batch:0
DMI 2.3 present.
ACPI: RSDP (v000 ACPIAM                                ) @ 0x000f7720
ACPI: RSDT (v001 A M I  OEMRSDT  0x01000609 MSFT 0x00000097) @ 0x0ff40000
ACPI: FADT (v002 A M I  OEMFACP  0x01000609 MSFT 0x00000097) @ 0x0ff40200
ACPI: MADT (v001 A M I  OEMAPIC  0x01000609 MSFT 0x00000097) @ 0x0ff40300
ACPI: OEMB (v001 A M I  OEMBIOS  0x01000609 MSFT 0x00000097) @ 0x0ff50040
ACPI: DSDT (v001  1ABVF 1ABVF007 0x00000007 INTL 0x02002026) @ 0x00000000
Allocating PCI resources starting at 20000000 (gap: 10000000:eec80000)
Built 1 zonelists
Kernel command line: BOOT_IMAGE=3.2.0.0-040R ro noinitrd root=/dev/hda5 console=ttyS0,19200 init=/bin/sh
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Detected 1994.657 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 255572k/261376k available (1705k kernel code, 5316k reserved, 748k data, 172k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 3999.39 BogoMIPS (lpj=7998793)
kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz stepping 09
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0800)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=3
PCI: Using configuration type 1
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1.P1P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1.P1P3._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:01:01.0
  IO window: e000-efff
  MEM window: fe700000-fe9fffff
  PREFETCH window: ffd00000-ffdfffff
PCI: Bridge: 0000:01:02.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:01.0
  IO window: e000-efff
  MEM window: fe700000-feafffff
  PREFETCH window: ffd00000-ffdfffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Initializing Cryptographic API
io scheduler noop registered (default)
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 40960K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
hda: STI Flash 8.0.0, ATA DISK drive
Probing IDE interface ide1...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 501760 sectors (256 MB), CHS=980/16/32
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 >
NET: Registered protocol family 2
IP route cache hash table tries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.
Using IPI Shortcut mode
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 172k freed
kjournald starting.  Commit interval 5 seconds
"

what can I do?

Thanks,
Norbert


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3838
    • michaelfmcnamara
    • Michael McNamara
Re: WS5100 Failed
« Reply #1 on: January 04, 2017, 09:51:14 AM »
Unfortunately that's usually how these units fail... the flash memory that's acting as a disk usually either goes bad or gets corrupted. I'm not sure if Motorola will even accept these for factory repair anymore since they are EoS. Even if you manage to replace the flash you end up with licensing issues because the license key will be lost and is tied to the MAC address of the hardware. Your best option might be looking at the used market and purchased a unit from a reputable reseller.

Good Luck
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline hnorbi

  • Rookie
  • **
  • Posts: 13
Re: WS5100 Failed
« Reply #2 on: January 04, 2017, 10:21:06 AM »
Dear Michael,

Thanks!
The license info will not lost, I wrote them.
 :/

Thanks,
Norberft

Unfortunately that's usually how these units fail... the flash memory that's acting as a disk usually either goes bad or gets corrupted. I'm not sure if Motorola will even accept these for factory repair anymore since they are EoS. Even if you manage to replace the flash you end up with licensing issues because the license key will be lost and is tied to the MAC address of the hardware. Your best option might be looking at the used market and purchased a unit from a reputable reseller.

Good Luck

Offline Radio_Head

  • Jr. Member
  • **
  • Posts: 48
Re: WS5100 Failed
« Reply #3 on: January 12, 2017, 02:25:49 AM »
Hi
As Michael has said the WS5xxx are well and truly EOL, you can pick WS5100 up from well know selling site  for a little as $22, you could buy a cheap unit take the DOM out ( Disk On Module ) flash disk, " Note there are two sizes of DOM 128MB and 256 ) You can use Ghost to copy a DOM and then restore it to a new DOM
So if you have a 128MB DOM and you have a ghost image V 1.43.12-R1 or for the 256DOM V 1.42.0-52
and then just go through the upgrade process to V3, I was given some instructions by Symbol ( as they were then ) on using ghost to recover the DOM- I have just looked on our old unit and the license is on the back of the unit, the thing you may loose if the additional ports purchased but you should have received a certificate with the key on it or you may have a backup of the lic files
If I can find the full instructions I will post them up, It maybe that you can take a ghost image of your backup unit but if you power it off and info that has been passed over to the RS unit will be lost until the primary unit is back online
RH

Offline hnorbi

  • Rookie
  • **
  • Posts: 13
Re: WS5100 Failed
« Reply #4 on: January 12, 2017, 05:17:17 AM »
Hi
As Michael has said the WS5xxx are well and truly EOL, you can pick WS5100 up from well know selling site  for a little as $22, you could buy a cheap unit take the DOM out ( Disk On Module ) flash disk, " Note there are two sizes of DOM 128MB and 256 ) You can use Ghost to copy a DOM and then restore it to a new DOM
So if you have a 128MB DOM and you have a ghost image V 1.43.12-R1 or for the 256DOM V 1.42.0-52
and then just go through the upgrade process to V3, I was given some instructions by Symbol ( as they were then ) on using ghost to recover the DOM- I have just looked on our old unit and the license is on the back of the unit, the thing you may loose if the additional ports purchased but you should have received a certificate with the key on it or you may have a backup of the lic files
If I can find the full instructions I will post them up, It maybe that you can take a ghost image of your backup unit but if you power it off and info that has been passed over to the RS unit will be lost until the primary unit is back online
RH

Thanks!
The interesting think, I tried to fit the DOM an another ws5100 which no have licence, the system starts up correctly, I put back the original unit, and it started once. Only once :/

Norbert

Offline hnorbi

  • Rookie
  • **
  • Posts: 13
Re: WS5100 Failed
« Reply #5 on: January 23, 2017, 07:19:57 AM »
I replaced the DOM with an another ws5100, without licence.
The symptomps same. Sometimes can start, sometimes can not.

:(

I can transfer the licence? (I think because is very old, I can't)

Norbert