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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Local Upgrade leads to Non Bootable drive 1

Status
Not open for further replies.

JimHilton

IS-IT--Management
Jun 20, 2009
346
CA
Hey all, my Mitel VAR came onsite for an unrelated problem, but gave me the software for V5.x.x.x.

I have no intention installing this on the work system, but thought it would be ok to install on my home can.

Well things did not goes as planned, I can no longer boot off the drive in the SX200-ICP.

I used "local" for the upgrade. Here are the errors I am getting:

auto-booting...


boot device : ata=auto
unit number : 0
processor number : 0
file name : /Kts8250.vx
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g) : 192.168.1.1
user (u) : ftp
ftp password (pw) : @
flags (f) : 0x0
other (o) : motfcc


Disk Configuration Started.
Creating block device for controller 0 drive 0... done.
Creating CBIO device for controller 0 drive 0... done.
Attaching to partition table for 1 partitions on controller 0 drive 0... done.
Creating Cache Layer for partition 0 (/ata00) on controller 0 drive 0... done.
Creating Dos FS device for partition 0 (/ata00) on controller 0 drive 0... done.
Disk Configuration Complete.
Loading /ata00/Kts8250.vx...n/a

Error auto-loading file: errno = 0x380003.
Can't load boot file!!

here is the boot parameters on start up:

[VxWorks Boot]: p

boot device : ata=auto
unit number : 0
processor number : 0
file name : /Kts8250.vx
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g) : 192.168.1.1
user (u) : ftp
ftp password (pw) : @
flags (f) : 0x0
other (o) : motfcc

The controller just blinks with all alarm lights blinking. If you need more info just ask and i'll try to get you the relevant reports

Thanks!!

Jim
 
I haven't touched a SX200 in years, but FWIW:

- The filename looks odd to me, you sure there shouldn't be a /sysro in front of it? or perhaps no leading '/'?

- You can change the boot device to motfcc and change the host address to an ftp server with the load and try to boot that way. Then you can at least look at the drive on the system and see why it can't find the load.
 
How old is the controller you're using? 5.0.x. needs 512 meg of memory

NO GOOD DEED GOES UNPUNISHED!
 
Hi, not sure of the year, so in attempts to get it running I loaded 4.0.1.11 onto a flash drive.

I power down the controller, pop in the flash drive and now i get:

auto-booting...


boot device : ata=auto
unit number : 0
processor number : 0
file name : /Kts8250.vx
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g) : 192.168.1.1
user (u) : ftp
ftp password (pw) : @
flags (f) : 0x0
other (o) : motfcc


Disk Configuration Started.
Creating block device for controller 0 drive 1... done.
Creating CBIO device for controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x0f7ffe40 appears invalid.
done.
Creating CBIO device for controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x0f7ffe40 appears invalid.
done.
Attaching to partition table for 1 partitions on controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x00000000 appears invalid.
ERROR: In usrAtaConfigExtended() failed to attach to partition table for controller 0 drive 1.
Disk Configuration Started.
Creating block device for controller 0 drive 0... done.
Creating CBIO device for controller 0 drive 0... done.
Attaching to partition table for 1 partitions on controller 0 drive 0... done.
Creating Cache Layer for partition 0 (/ata00) on controller 0 drive 0... done.
Creating Dos FS device for partition 0 (/ata00) on controller 0 drive 0... done.
Disk Configuration Complete.
Loading /ata00/Kts8250.vx...n/a

Error auto-loading file: errno = 0x380003.
Can't load boot file!!

I'm thinking maybe i've got a bum flash card so will get one tomorrow.

Thanks!

Jim
 
Hi Irwin, ok i've setup an ftp and controller connects to it, but now its getting an actual script error:

Attached TCP/IP interface to motfcc0.
Attaching network interface lo0... done.
Loading... 5945472
Starting at 0x10000...

Last reset cause was (0x3) EXTERNAL_HARD_RESET


VxWorks

Copyright 1984-2002 Wind River Systems, Inc.

CPU: Mitel Embedded PPC82XX F200
Runtime Name: VxWorks
Runtime Version: 5.5.1
BSP version: 2.1/1
Created: Feb 2 2007, 13:32:30
WDB Comm Type: WDB_COMM_END
WDB: Ready.


Executing S10startup script

SSHwInit script command not found in the symbol table
Illegal command statement at line 7

Then she hard locks.

And just in case, here is the inet config:

boot device : motfcc
unit number : 0
processor number : 0
host name : mitel.thests.com
file name : kts8250.vx
inet on ethernet (e) : 10.0.99.3:ffffff00
host inet (h) : 10.0.99.102
gateway inet (g) : 10.0.99.1
user (u) : anonymous
ftp password (pw) : guest@
flags (f) : 0x0

To Nytalkin, confirmed, it only has 256 megs of RAM

Thanks!


 
Sounds like the script that's installed on the system doesn't match the image that you booted with.

What version of the image are you using to boot with?

I don't have the scripts in front of me for 4.0.1.1, but SSHwInit() should be in at least 4.0.4.9
 
I assume by image you mean version? The install disk is v4.0.1.11 and I am attempting to do a "Initial compact flash card instalation".

I've given up all hope of trying to upgrade the thing so i just want its original software back on it. But this is where I run into the script problem.

Its almost like some stuff is still left on the HD. I've googled to see how to format it, but it appears that is a bad thing to do.

Thanks
 
Do you have the CD version of the software? Try a clean install from your PC.

NO GOOD DEED GOES UNPUNISHED!
 
make sure you format your flash card as FAT32.you can use the 256k flash if your not using 5300 series sets
 
Hi, yes, I have the CD (because its about you!) and run the installer to the flash drive.

The tech handbook says to use FAT, but I think your right that it seems to do more formatted with FAT32

I have now formatted with FAT32 and did not do a quick format.

I have a 512 flash card and no 53xx series sets.

I am really starting to think the card reader is not picking up the flash card.

This is the output I get with AND without the flash card in the machine: (NOTE: I've wiped the drive as per another thread).

Press <SPACE><SPACE><SPACE> to stop auto-boot AFTER countdown starts...
<7><6><5><4><3><2><1><0>
auto-booting...


boot device : ata=auto
unit number : 0
processor number : 0
file name : /Kts8250.vx
inet on ethernet (e) : 192.168.1.2:ffffff00
gateway inet (g) : 192.168.1.1
user (u) : ftp
ftp password (pw) : @
flags (f) : 0x0
other (o) : motfcc


Disk Configuration Started.
Creating block device for controller 0 drive 1... done.
Creating CBIO device for controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x0f7ffe40 appears invalid.
done.
Creating CBIO device for controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x0f7ffe40 appears invalid.
done.
Attaching to partition table for 1 partitions on controller 0 drive 1... 0xf30e670 (tBoot): cbioWrapBlkDev: BLK_DEV pointer 0x00000000 appears invalid.
ERROR: In usrAtaConfigExtended() failed to attach to partition table for controller 0 drive 1.
Disk Configuration Started.
Creating block device for controller 0 drive 0... done.
Creating CBIO device for controller 0 drive 0... done.
Attaching to partition table for 1 partitions on controller 0 drive 0... done.
Creating Cache Layer for partition 0 (/ata00) on controller 0 drive 0... done.
Creating Dos FS device for partition 0 (/ata00) on controller 0 drive 0... done.
Disk Configuration Complete.
Loading /ata00/Kts8250.vx...usrFdiskPartLib warning: disk partition table is not initialized
usrFdiskPartLib warning: use usrFdiskPartCreate( 0xf7ffd60, 1) to initialize the disk as a single partition
0xf30e670 (tBoot): dosFsLib.c : Malformed boot sector. Offset n/a
0, value 69.
Error auto-loadin g file: errno = 0x
0xc0006f30e670 (tBoot.
): dosFsLib.c : Problem finding volume data, trying to use the next block as boot block.
Can't lo0xad boot file!!
f30e670 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 80.
0xf30e670 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions are properly handled.
 
You may be too far gone for this info, but yes, I meant the version software load when I said 'image'. You were booting a 4.1 load but the scripts still on the machine were from the 5.0 install. The scripts call functions within the image that is booted, if it can't find them, it coughs like it did. If you still have the 5.1 installed on the system, do the same thing (remote boot via ftp) but have it point to the 5.0 version, not the 4.1.
 
Hi Irwin, your right, gone too far. V5 has the same disk issues. The 200 is now a brick.

But this fellow was able to get his 40 gb maxtor to work and it wsan't a "mitel drive".

I wonder if fdisking it is the answer?

I also read somewhere in th world of google there is some utility to do the formatting but I can't find the reference too it.

Jim

 
When I worked on the 200 I remember that the disk formatting was tricky, only a certain reader would work. Also, since the reader would only see one partition, you couldn't access the db or vmail partitions.

Whenever I see a company specify a particular drive, it's simply because that's what they use and have tested. It's not saying another one won't work, they just haven't tested it and don't want to get caught going down a worm-hole with other drives that 'may' not work.
 
Hi actually when i meant a "non mitel drive" it was a maxtor 40 GB but not mitelified.

Sadly, when i nuked the disk, I did see the partitions, 1 was a spare, sysro, db and vm

The 2 first ones were FAT and the last 2 were FAT32. This does tend to boggles one mind tho, you'd think the install software would know the drive is not ready and prep it on its own *grumble*

You've probably already seen this but just incase, here is the link to the thread.

 
before trying to send the software to the flashcard empty the FTPROOT directory on your pc. there may be files stuck in there from the 5.0 with the same name as one needed to "go back"

NO GOOD DEED GOES UNPUNISHED!
 
Hi Ny, yes, each time I've tried to install the software, I totally clean out the folder.

I believe the issue now is because i've nuked the original drive the install simply will not install as it complains about partitions etc.

The method I've been using to ftp the stuff is:

Run \software\setup.exe
choose initial setup
send it to c:\temp (that is where the ftp server points to).
get on the controller
hit the space bar and get into vxworks.
check the inet settings using p
then hit @
The controller is able to connect to the nic and logs in, but it barfs when it trys to install as the drive has been wiped.

I have one last thing I'm going to try (Unless someone else has that mystery utility to create the partitions). I am going to attempt to do a disk recovery and hope that I can get back what ever file it needs to allow the install.

Thanks for your help!!
 
try substituting the kts file with boot_install last gasp so to speak

NO GOOD DEED GOES UNPUNISHED!
 
Hey Ny, Gave it a shot, but i think that file is unique to the 3300. I checked in all the tar/gz file and could not find it.

Interestingly, if you take a hex editor to Kts8250.vx you can see there are references to various formatting stats. I just couldn't figure out what the switches were.

Thanks!
 
have done this numerous times. it is a 200, not a 3300 and that makes it much easier.
take a flash card and run the installer and choose inital installation and install it on the flash drive. I tend to choose no database when I do that to simply get it up and running.
insert the flash drive in the 200, after it turns green, reboot and it will format the internal drive (flash or HDD) and install the call control.
this will change the IP address to 192.168.1.2 and the installer password to 1000.
log in and manipulate form 47 accordingly and then restore your database.
I did see one hard drive that would run V4 but not 5. didn't play with it long enough to determine why. once the customer was back in service we quit.
 
Hi Ross, ok your a glimmer of light, but just so that I am sure of the exact procedure, what should my boot config be? Should I hit the space bar 3 times or let it go past that.

There is also a possibility that the flash reader is NFG.

The drive is a Maxtor 40 GB with no partitions defined.

Please advise.

Thanks!!

Jim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top