Sponsored Content
Full Discussion: Problem with bosboot
Operating Systems AIX Problem with bosboot Post 302924718 by bobochacha29 on Wednesday 12th of November 2014 04:47:43 AM
Old 11-12-2014
Thanks guys. Maybe there was something wrong with the altinst_rootvg. I removed it and recreated it. Then I booted the hdisk7 from SMS ( no bosboot or bootlist commands anymore ) and it worked.
This User Gave Thanks to bobochacha29 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bosboot problem please help!

each time I try to do a bosboot or a mksysb the cpu says that he doesn't find /unix... I don't understand cause the kernel is here on the computer and at this exact place with the right name. I tried to force with -k /unix but it doesn't do anything. He doesn't find it and it is here... Do you... (6 Replies)
Discussion started by: jericho
6 Replies

2. AIX

bosboot: Boot image is 22995 512 byte blocks.

My mksysb scripts gives the following text on standard error: bosboot: Boot image is 22995 512 byte blocks. How come on a Aix 5200-07 aix-system. I thought this message meant that the tape (/dev/rmt0) is not bootable, but I read about a limit of 12 MB and 22995 block is less than 12 MB ... (0 Replies)
Discussion started by: frankwiel
0 Replies

3. AIX

installp -C error: 'bosboot verification failed'

Hi, I'm a noob with AIX, can anybody help me solve this issue I'm stuck with on an 5.3 box. bash# installp -C 0503-409 installp: bosboot verification starting... 0503-497 installp: An error occurred during bosboot verification processing. Thanks. (4 Replies)
Discussion started by: thebytegrill
4 Replies

4. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

5. AIX

bosboot issue

bosboot -ad hdisk0 give the following error .. malloc failed 0301-177 A previous bosdebug command has changed characteristics of this boot image. Use bosdebug -L to display what these changes are. 0301-106 /usr/lib/boot/bin/mkboot_chrp: The malloc call failed for size: 216174592 ... (1 Reply)
Discussion started by: b_manu78
1 Replies

6. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

7. AIX

Cannot uninstall powerpath - bosboot issues

Hi Guys, I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one. I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors: ... (4 Replies)
Discussion started by: zxmaus
4 Replies

8. IP Networking

Problem with forwarding emails (SPF problem)

Hi, This is rather a question from a "user" than from a sys admin, but I think this forum is apropriate for the question. I have an adress with automatic email forwarding and for some senders (two hietherto), emails are bouncing. This has really created a lot of problems those two time so I... (0 Replies)
Discussion started by: carwe
0 Replies

9. AIX

bosboot issue

Hi i wanted to know for what reasons, bosboot fails with the error below.? # /usr/sbin/bosboot.dp -a -p /usr/lib/boot/chrp.disk.proto -d /dev/ipldevice dd: 0511-053 The write failed. : There is a request to a device or address that does not exist. 65893+1 records in. 1029+1 records out. ... (1 Reply)
Discussion started by: gnakul
1 Replies

10. UNIX for Dummies Questions & Answers

sed Or Grep Problem OR Terminal Problem?

I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore. Here is what 's happening: * I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
GSMSMSSTORE(8)						      System Manager's Manual						    GSMSMSSTORE(8)

NAME
gsmsmsstore - SMS store manipulation program SYNOPSIS
gsmsmsstore [ -a ] [ --add ] [ -b baudrate ] [ --baudrate baudrate ] [ -c ] [ --copy ] [ -C service centre address ] [ --sca service centre address ] [ -d destination device or file ] [ --destination destination device or file ] [ -h ] [ --help ] [ -I init string ] [ --init init string ] [ -k ] [ --backup ] [ -l ] [ --list ] [ -s source device or file ] [ --source source device or file ] [ -t SMS store name ] [ --store SMS store name ] [ -v ] [ --version ] [ -V ] [ --verbose ] [ -x ] [ --delete ] [ -X ] [ --xonxoff ] { indices } [ phonenumber text ] DESCRIPTION
gsmsmsstore can store or retrieve SMS messages entries residing in a GSM mobile phone's SMS store to or from a file, add SMS messages to a store, or list the store's contents. Additionally, it is possible to add SMS submit messages to a store. gsmsmsstore reads entries from the source which can be a mobile phone (if a serial device file is given) or a file (if a file name is given). The source is never modified. gsmsmsstore writes SMS messages to a destination file or device in the case of --copy, --backup, and --add. The --list option does not change any file but just lists the contents to standard output. The --backup and --copy options require both source and destination files or devices. The --list option requires a source. The --add and --delete options require a destination file or device. If "-" is given as the parameter for the --source or --destination options, the SMS store is read from standard input and/or written to standard output, respectively. SMS message files are not human-readable. Error messages are printed to the standard error output. If the program terminates on error the error code 1 is returned. OPTIONS
-a, --add Adds an SMS submit message with recipient address phonenumber and text text to the destination. -b baudrate, --baudrate baudrate The baud rate to use. The default baudrate is 38400. -c, --copy This causes the contents of the source to be copied to the destination. After this operation the destination has exactly the same contents as the source. If indices are given on the command line only those SMS messages denoted by the indices are copied to the destination. -C service centre address, --sca service centre address Sets the service centre address to use for all SUBMIT SMSs (may not work with some phones). -d destination, --destination destination The destination device or file. -h, --help Prints an option summary. -I init string, --init init string Initialization string to send to the TA (default: "E0"). Note that the sequence "ATZ" is sent first. -k, --backup This causes those entries to be added from the source to the destination that are not already present in the destination. If indices are given on the command line only those SMS messages denoted by the indices are backed up (ie. added) to the destination. -l, --list Prints out the entire contents of the source in human-readable form. -s source, --source source The source device or file. -t SMS store name, --store SMS store name The name of the SMS store to read from or write to. This information is only used for device sources and destinations. A commonly available message store is "SM" (SIM card). -v, --version Prints the program version. -V, --verbose Prints out a detailed progress report. -x, --delete Delete the SMS messages as denoted by the indices from the destination. -X, --xonxoff Uses software handshaking (XON/XOFF) for accessing the device. EXAMPLES
The following command lists all entries in the mobile phone connected to /dev/mobilephone to the standard output: gsmsmsstore -b 19200 -s /dev/mobilephone -t SM -l The following adds entries 4, 7, and 10 from the device /dev/mobilephone to the file smsstore: gsmsmsstore -s /dev/mobilephone -d /home/fred/smsstore -t SM -b 4 7 10 AUTHOR
Peter Hofmann <software@pxh.de> BUGS
Report bugs to software@pxh.de. Include a complete, self-contained example that will allow the bug to be reproduced, and say which version of gsmsmsstore you are using. COPYRIGHT
Copyright (C) 1999 Peter Hofmann gsmsmsstore is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as pub- lished by the Free Software Foundation; either version 2, or (at your option) any later version. gsmsmsstore is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABIL- ITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with gsmsmsstore; see the file COPYING. If not, write to the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. SEE ALSO
gsminfo(7), gsmctl(1), gsmpb(1), gsmsendsms(1), gsmsmsd(8). gsmsmsstore v1.10 Sat Jun 16 22:10:00 UTC 2012 GSMSMSSTORE(8)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy