SF-800 Replacing CF card

[charuvila26@gmail.com]

Two of our iSMS server (SF-800) is not functioning due to faulty CF card. I tried with new CF card, but I found that some files need to be downloaded from FTP site. unfortunately FTP site is not configured in iSMS server; Need advise

[Bryon Davis]

Normally you can just install the new blank flash and on boot up the SF800 will create any files and folders it needs.

What files are you trying to get on to the SF800?

[Bryon Davis]

You may be able to use tftp to download files.

Downloading Files to and from the iSMS
First setup a tftp server. I used Solarwinds TFTP Server on a Windows PC.
If you want to download a file to the iSMS, put the file in the TFTP Server’s root directory.

Download a Binary File
1. Telnet to the iSMS on port 2222 and login with admin credentials.
2. At the # prompt enter “cd /var/config” (without the quotes).
3. Enter “tftp 192.168.2.11”. Replace the IP address with the IP address of your tftp server.
4. At the “tftp>” prompt enter “mode binary”.
5. At the “tftp>” prompt enter “get filename”. Replace “filename” with the name of the file you want to download.
6. Verify that the get command was successful and enter “quit”.
7. The file should now be in the /var/config folder. If you get a permission error message when running the file then enter the command “chmod +x filename”. This will change the permissions on the file to be an executable.

Uploading a Binary File: Use put command instead of get.

[charuvila26@gmail.com]

I tried with new CF card, log says CF card is invalid, I checked the underlying script in /lib/CF-Update, it contains the ftp link and some tar file

[Bryon Davis]

You can replace it with an equivalent compact flash of 1gig or larger. We recommend industrial grade. It must also support PIO mode.
If you insert a blank compact flash in the SF800, it will automatically format and copy the needed files. It shouldn’t need to use FTP to create these files.
It will be at default afterwards (192.168.2.1, username=admin, password=admin).

[charuvila26@gmail.com]

Thank you Mr. Davis
I think I tried with a simple CF card, I guess it doesn’t support PIO mode. I will try with industrial grade one

[charuvila26@gmail.com]

I tried with new CF card Trancend CF 1GB Industrial (CF100I) it has PIO support.
log says invalid CF card

see next post for full log

• This reply was modified 5 years, 5 months ago by charuvila26@gmail.com.

[charuvila26@gmail.com]

see next post

[charuvila26@gmail.com]

Full log after inserting new 1GB Industrial grade CF card with PIO
——————————————————————–
+Uncompressing Linux………………………………………………… done, booting the kernel.

Linux version 2.4.27-uc1 (rcrogers@ubudev) (gcc version 3.3.6) #85 Thu Nov 18 10:41:28 CST 2010

CPU: XScale-IXP4xx/IXC11xx revision 2

Machine: Intel IXP425 Monte Jade Demonstration Platform

Warning: bad configuration page, trying to continue

alloc_bootmem_low

memtable_init

On node 0 totalpages: 65536

zone(0): 16384 pages.

zone(1): 49152 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0,115200 root=/dev/mtdblock3 ro mem=256M@0x00000000

Calibrating delay loop… 266.24 BogoMIPS

Memory: 256MB = 256MB total

Memory: 257376KB available (1381K code, 286K data, 232K init)

Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)

Inode cache hash table entries: 16384 (order: 5, 131072 bytes)

Mount cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)

Page-cache hash table entries: 65536 (order: 6, 262144 bytes)

POSIX conformance testing by UNIFIX

PCI: reset bus…

PCI Autoconfig: Found Bus 0, Device 13, Function 0

PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000

PCI: bus0: Fast back to back transfers enabled

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

Journalled Block Device driver loaded

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled

ttyS00 at 0xff000003 (irq = 15) is a XScale UART

ttyS01 at 0xff001003 (irq = 13) is a XScale UART

ledman: Copyright (C) SnapGear, 2000-2003.

DS1302: Copyright (C) 2001, Greg Ungerer (gerg@snapgear.com)

snapdog: HW/SW watchdog timer for SnapGear/Others

RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize

PPP generic driver version 2.4.2

PPP MPPE compression module registered

Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4

ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

cfi_cmdset_0001: Erase suspend on write enabled

Using buffer write method

Creating 6 MTD partitions on “IXP425 Flash”:

0x00000000-0x01000000 : “MTSI-Flash0”

0x00000000-0x00040000 : “RedBoot”

0x00040000-0x00140000 : “zImage”

0x00140000-0x00fc0000 : “ramdisk”

0x00fc0000-0x00fc1000 : “RedBoot config”

0x00fe0000-0x01000000 : “FIS directory”

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 2048 buckets, 16Kbytes

TCP: Hash tables configured (established 16384 bind 32768)

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

lec.c: Nov 18 2010 10:43:20 initialized

mtsCFModule initialize IDE …

mtsCFModule CF is ready …

Partition check:

cf0a: cf0a1

mtsCFinit_module LOADED SUCCESSFULLY

cramfs: wrong magic

VFS: Mounted root (romfs filesystem) readonly.

Freeing init memory: 232K

init started: BusyBox v1.00 (2010.01.22-17:08+0000) multi-call binary
Using /lib/modules/2.4.27-uc1/kernel/ixp425/ixp400/ixp400.o
Module init.

Using /lib/modules/2.4.27-uc1/kernel/ixp425/net/ixp425_eth.o
ixp425_eth:

Initializing IXP425 NPE Ethernet driver software v. 9.0k

ixp425_eth: Initialising Queue Manager…

valid PHY ID

physcan

ixp425_eth: Found PHY 0 at 1

ixp425_eth: Configuring PHY 0

ixp425_eth: eth0 is using the PHY at address 1

Set eth0 to MAC address 00:08:00:85:05:9c
Model of last device: UKNOWN
/etc/mknod_upci: /var/config/Model: No such file or directory
isi_init: resetlatchcs3 is initialized. value = d1d45000 BUS BASE = 53000000

Multi-Tech ISIUPCI 1/2/4/8 port serial driver version 2.03 (2008-05-22) with SHARE_IRQ SERIAL_PCI enabled

e2label: not an ext2 filesystem
CF device is invalid
/etc/rc: cannot create temp file for here document: No such file or directory
mke2fs 1.25 (20-Sep-2001)
Filesystem label=mts
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
123904 inodes, 986112 blocks
49305 blocks (4%) reserved for the super user
First data block=1
121 block groups
8192 blocks per group, 8192 fragments per group
1024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409, 663553

Writing inode tables: 0/121 1/121 2/121 3/121 4/121 5/121 6/121 7/121 8/121 9/121 10/121 11/121 12/121 13/121 14/121 15/121 16/121 17/121 18/121 19/121 20/121 21/121 22/121 23/121 24/121 25/121 26/121 27/121 28/121 29/121 30/121 31/121 32/121 33/121 34/121 35/121 36/121 37/121 38/121 39/121 40/121 41/121 42/121 43/121 44/121 45/121 46/121 47/121 48/121 49/121 50/121 51/121 52/121 53/121 54/121 55/121 56/121 57/121 58/121 59/121 60/121 61/121 62/121 63/121 64/121 65/121 66/121 67/121 68/121 69/121 70/121 71/121 72/121 73/121 74/121 75/121 76/121 77/121 78/121 79/121 80/121 81/121 82/121 83/121 84/121 85/121 86/121 87/121 88/121 89/121 90/121 91/121 92/121 93/121 94/121 95/121 96/121 97/121 98/121 99/121100/121101/121102/121103/121104/121105/121106/121107/121108/121109/121110/121111/121112/121113/121114/121115/121116/121117/121118/121119/121120/121done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: mtsWriteSectorW Waiting_RDY_Alt fail 0x8f0 (2288)

mtsWriteSectorW Waiting_RDY_Alt fail 0xc811 (51217)

mtsWriteSectorW Waiting_RDY_Alt fail 0x10811 (67601)

mtsWriteSectorW Waiting_RDY_Alt fail 0x14803 (83971)

Waiting_DRQ_Alt timed out STATUS 0xd0

mtsWriteSectorW fail 0x14903 (84227)

mtsWriteSectorW Waiting_RDY_Alt fail 0xa0f (2575)

Waiting_DRQ_Alt timed out STATUS 0xd0

mtsWriteSectorW fail 0xb11 (2833)

mtsWriteSectorW Waiting_RDY_Alt fail 0x4a0f (18959)

mtsWriteSectorW Waiting_RDY_Alt fail 0x8803 (34819)

Waiting_DRQ_Alt timed out STATUS 0xd0

mtsWriteSectorW fail 0xc803 (51203)

mtsWriteSectorW Waiting_RDY_Alt fail 0x10802 (67586)

done

This filesystem will be automatically checked every 24 mounts or
180.00 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.25 (20-Sep-2001)
mts: clean, 11/123904 files, 24020/986112 blocks
kjournald starting. Commit interval 5 seconds

EXT3 FS 2.4-0.9.19, 19 August 2002 on cf0(252,1), internal journal

EXT3-fs: mounted filesystem with ordered data mode.

cat: /usr/local/built: No such file or directory
ftpupdate is not configured
EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16385

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16386

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16392

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16393

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16394

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16395

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16396

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16397

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16398

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16399

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16400

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16401

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16402

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16403

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16404

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16405

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16406

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16407

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16408

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16409

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16410

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16411

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16412

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16413

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16414

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16415

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16416

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16417

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16418

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16419

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16420

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16421

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16422

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16423

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16424

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16425

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16426

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16427

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16428

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16429

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16430

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16431

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16432

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16433

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16434

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16435

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16436

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16437

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16438

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16439

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16440

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16441

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16442

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16443

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16444

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16445

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16446

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16447

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16448

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16449

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16450

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16451

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16452

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16453

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16454

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16455

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16456

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16457

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16458

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16459

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16460

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16461

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16462

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16463

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16464

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16465

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16466

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16467

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16468

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16469

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16470

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16471

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16472

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16473

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16474

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16475

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16476

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16477

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16478

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16479

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16480

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16481

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16482

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16483

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16484

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16485

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16486

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16487

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16488

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16489

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16490

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16491

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16492

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16493

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16494

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16495

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16496

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16497

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16498

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16499

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16500

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16501

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16502

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16503

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16504

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16505

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16506

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16507

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16508

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16509

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16510

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16511

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16512

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16513

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16514

mtsWriteSectorW Waiting_RDY_Alt fail 0x803 (2051)

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16515

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16516

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16517

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16518

EXT3-fs error (device cf0(252,1)): ext3_new_block: Allocating block in system zone – block = 16519

Tue Jan 1 00:00:00 UTC 2008
semget success
snapdog: user servicing enabled (short=60,long=300).

# can’t find service “discard,discard”
can’t find service “discard,discard”
can’t find service “telnet,2222”
can’t find service “telnet-dialout,5000”
can’t find service “telnet-dialout,5001”
can’t find service “telnet-dialout,5002”
can’t find service “telnet-dialout,5003”
can’t find service “telnet-dialout,5004”
can’t find service “telnet-dialout,5005”
can’t find service “telnet-dialout,5006”
can’t find service “telnet-dialout,5007”
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
SQL error: (null)
debug: smsserver.c: 1261: main: sql_sockfd:7, inboxsql_sockfd:8, lb_handler_fd:9, lb_fd:10, gui_handler_fd:11, readfd:12
debug: smsserver.c: spawn_txrx_for_each_modem
debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1a], pid:140
mtsWriteSectorW Waiting_RDY_Alt fail 0x2c912 (182546)

mtsWriteSectorW Waiting_RDY_Alt fail 0x28912 (166162)

mtsWriteSectorW Waiting_RDY_Alt fail 0x9e5 (2533)

mtsWriteSectorW Waiting_RDY_Alt fail 0x1093f (67903)

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1b], pid:140
/bin/txrx /dev/ttyMU1a 170
debug: txrx.c: main: starting on /dev/ttyMU1a
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
In – getserialfd /dev/ttyMU1a /dev/ttyMU1a

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1c], pid:140
/bin/txrx /dev/ttyMU1b 171
debug: txrx.c: main: starting on /dev/ttyMU1b
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
In – getserialfd /dev/ttyMU1b /dev/ttyMU1b

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1d], pid:140
/bin/txrx /dev/ttyMU1c 172
debug: txrx.c: main: starting on /dev/ttyMU1c
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
In – getserialfd /dev/ttyMU1c /dev/ttyMU1c

ISIUPCI_MODEM_RESET: chan from app = 0

Action Value is 1

chan = 0, resetlatch_cs3 = fffffffe, jiffies = 1685

CS3 Latch is used

Action Value is 0

chan=0, clear resetlatch_cs3=ffffffff, jiffies=5772

CS3 Latch is used

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1e], pid:140
/bin/txrx /dev/ttyMU1d 173
debug: txrx.c: main: starting on /dev/ttyMU1d
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
ISIUPCI_MODEM_RESET: chan from app = 1

Action Value is 1

chan = 1, resetlatch_cs3 = fffffffd, jiffies = 16e6

CS3 Latch is used

In – getserialfd /dev/ttyMU1d /dev/ttyMU1d

Action Value is 0

chan=1, clear resetlatch_cs3=ffffffff, jiffies=5865

CS3 Latch is used

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1f], pid:140
/bin/txrx /dev/ttyMU1e 174
debug: txrx.c: main: starting on /dev/ttyMU1e
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
In – getserialfd /dev/ttyMU1e /dev/ttyMU1e

ISIUPCI_MODEM_RESET: chan from app = 2

Action Value is 1

chan = 2, resetlatch_cs3 = fffffffb, jiffies = 174c

CS3 Latch is used

Action Value is 0

chan=2, clear resetlatch_cs3=ffffffff, jiffies=5974

CS3 Latch is used

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1g], pid:140
/bin/txrx /dev/ttyMU1f 177
debug: txrx.c: main: starting on /dev/ttyMU1f
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
ISIUPCI_MODEM_RESET: chan from app = 3

Action Value is 1

chan = 3, resetlatch_cs3 = fffffff7, jiffies = 17b2

CS3 Latch is used

In – getserialfd /dev/ttyMU1f /dev/ttyMU1f

Action Value is 0

chan=3, clear resetlatch_cs3=ffffffff, jiffies=6070

CS3 Latch is used

debug: smsserver.c: 345: spawn_txrx_for_each_modem: txrxbinary:[/bin/txrx], buff:[/dev/ttyMU1h], pid:140
/bin/txrx /dev/ttyMU1g 182
debug: txrx.c: main: starting on /dev/ttyMU1g
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/va ISIUPCI_MODEM_RESET: chan from app = 4

r/run/UNIXSOCKET]
Action Value is 1

chan = 4, resetlatch_cs3 = ffffffef, jiffies = 1815

CS3 Latch is used

In – getserialfd /dev/ttyMU1g /dev/ttyMU1g

Action Value is 0

chan=4, clear resetlatch_cs3=ffffffff, jiffies=6168

CS3 Latch is used

debug: smsserver.c: 1277: main: Before txrx_mon
debug: smsserver.c: start_waiting_on_select
/bin/txrx /dev/ttyMU1h 183
debug: txrx.c: main: starting on /dev/ttyMU1h
debug: txrx.c: start_unix_domain: cliAddr_domain.sun_path:[/var/run/UNIXSOCKET]
In – getserialfd /dev/ttyMU1h /dev/ttyMU1h

ISIUPCI_MODEM_RESET: chan from app = 5

Action Value is 1

chan = 5, resetlatch_cs3 = ffffffdf, jiffies = 187e

CS3 Latch is used

Action Value is 0

chan=5, clear resetlatch_cs3=ffffffff, jiffies=6278

CS3 Latch is used

debug: smsserver.c: txrx_mon(signum:17), setting txrx_mon_flag = 1
ISIUPCI_MODEM_RESET: chan from app = 6

Action Value is 1

chan = 6, resetlatch_cs3 = ffffffbf, jiffies = 18e1

CS3 Latch is used

Action Value is 0

chan=6, clear resetlatch_cs3=ffffffff, jiffies=6378

CS3 Latch is used

ISIUPCI_MODEM_RESET: chan from app = 7

Action Value is 1

chan = 7, resetlatch_cs3 = ffffff7f, jiffies = 1945

CS3 Latch is used

Action Value is 0

chan=7, clear resetlatch_cs3=ffffffff, jiffies=6478

CS3 Latch is used

mtsWriteSectorW Waiting_RDY_Alt fail 0x30914 (198932)

mtsWriteSectorW Waiting_RDY_Alt fail 0x881f (34847)

mtsWriteSectorW Waiting_RDY_Alt fail 0x18803 (100355)

mtsWriteSectorW Waiting_RDY_Alt fail 0x20803 (133123)

mtsWriteSectorW Waiting_RDY_Alt fail 0x28803 (165891)

mtsWriteSectorW Waiting_RDY_Alt fail 0x2c803 (182275)

mtsWriteSectorW Waiting_RDY_Alt fail 0x30803 (198659)

mtsWriteSectorW Waiting_RDY_Alt fail 0x34803 (215043)

mtsWriteSectorW Waiting_RDY_Alt fail 0x80f (2063)

mtsWriteSectorW Waiting_RDY_Alt fail 0x480d (18445)

mtsWriteSectorW Waiting_RDY_Alt fail 0x880b (34827)

mtsWriteSectorW Waiting_RDY_Alt fail 0x18811 (100369)

mtsWriteSectorW Waiting_RDY_Alt fail 0x30811 (198673)

mtsWriteSectorW Waiting_RDY_Alt fail 0x803 (2051)

mtsWriteSectorW Waiting_RDY_Alt fail 0x10803 (67587)

mtsWriteSectorW Waiting_RDY_Alt fail 0x38911 (231697)

mtsWriteSectorW Waiting_RDY_Alt fail 0x8813 (34835)

mtsWriteSectorW Waiting_RDY_Alt fail 0x30811 (198673)

mtsWriteSectorW Waiting_RDY_Alt fail 0x803 (2051)

mtsWriteSectorW Waiting_RDY_Alt fail 0x1096b (67947)

journal_bmap: journal block not found at offset 268 on cf0(252,1)

Aborting journal on device cf0(252,1).

ext3_abort called.

EXT3-fs abort (device cf0(252,1)): ext3_journal_start: Detected aborted journal

Remounting filesystem read-only

EXT3-fs error (device cf0(252,1)) in start_transaction: Journal has aborted

/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fclose(/var/log/messages): Read-only file system
/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fopen(/var/log/messages): Read-only file system
Jan 1 00:01:29 kernel: Aborting journal on device cf0(252,1).

/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fopen(/var/log/messages): Read-only file system
Jan 1 00:01:29 kernel: ext3_abort called.

/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fopen(/var/log/messages): Read-only file system
Jan 1 00:01:29 kernel: EXT3-fs abort (device cf0(252,1)): ext3_journal_start: Detected aborted journal

/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fopen(/var/log/messages): Read-only file system
Jan 1 00:01:29 kernel: Remounting filesystem read-only

/home/rcrogers/disk3/1.47/multi/smsfinder/snapgear/user/busybox/sysklogd/syslogd-misc.c:log_message():fopen(/var/log/messages): Read-only file system
Jan 1 00:01:29 kernel: EXT3-fs error (device cf0(252,1)) in start_transaction: Journal has aborted

LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error
LD LOG file error

[Author]

Posts