Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UC Module Failure to Boot 1

tektipperuser

IS-IT--Management
Feb 26, 2025
2
Hello everyone,

We have a UC Module running VM Pro with the IP500 V2 Control Unit. Power went off over the weekend and the VM server has failed to come back online. Connecting a keyboard/monitor to the module I can see the server trying to boot up, but it fails with these errors:

Code:
mount: wrong fs type, bad option, bad superblock on /dev/sda2
missing codepage or helper program, or other error

Code:
Kernel panic - not syncing : Attempted to kill init!
Pid: 1, comm: init Not Tainted 2.6.32-279.22.1.e16.i686 #1
Call trace:
? panic 0x68/0x11c
? do_exit+0x747/0x750
? do_group_exit+0x3c/0xca0
? sys_exit_group+0x11/0x20
? syscall_call+0x7/0xb

I have been dropped into this system with very little context and almost no documentation, so any help would be appreciated. I'm not sure if we even have the config backed up anywhere if the module has to be replaced.
 
It looks like the drive is going bad, you could try reformatting it and reloading it, or you can take out the sata drive and try to get the information off of it if you need it for that client.

Now my rant: Avaya should never have sold these units. They are abysmal and spontaneously fail with a simple restart, much less a system without a UPS that loses power. I have thrown all of the UC modules away at all of my clients and put them on HyperV application servers, and do daily backups to our application server at our office. I never want to see one of them again. Trash.
 
Does it save V1 or V2 on the front of the module as V1s were prone to failure. I think Avaya would have swapped at one time.

Once I had a quick go at replacing the drive itself but could not seem to get it to work and just built an application server in a VM.
 
Does it save V1 or V2 on the front of the module as V1s were prone to failure. I think Avaya would have swapped at one time.

Once I had a quick go at replacing the drive itself but could not seem to get it to work and just built an application server in a VM.

Thanks! On the front I just see UC Module 700501442. Looks like I need to take it out to see per the PCN.
 
Hello,

Hard drive is sure dead.
If it's a V1 as says the Part number ( the one with SATA drive )
You can try to simply replace the hard drive it by an other one and reinstall the UC Module software.
The SATA SSD is a 32 Mb .

I have a customer which even had run its UC Module with a 80Gb mechanical drive, slow, but functional.
 
Yes that is a V1 as they did not know there would be a V2.

I recall the drive is a half slim SATA DOM 32gb MO-297. Something else might work but there's not much space.
 

Part and Inventory Search

Sponsor

Back
Top