- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: Scripting Toolkit (stk) 10.40 bootstrap.sh end...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-03-2016 06:27 AM - last edited on тАО06-29-2021 04:55 AM by Ramya_Heera
тАО05-03-2016 06:27 AM - last edited on тАО06-29-2021 04:55 AM by Ramya_Heera
Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
I am looking for support for the HPE Scripting Toolkit 10.40. I am booting a BL460c Gen8 server and can pxe boot the kernel and the built-in bootstrap.sh does run . However, it ends however with the messages:
*****include file not found*****
bash: cannot set terminal process group (-1) inappropriate ioctl for device
bash: no job control in this shell
I am trying to use nfs to mount the scripts folder. Once the bootstrap.sh stops, the folder is not mounted but I can mount it manually from the command line. I suspect I may have some options set incorrectly in the pxelinux.cfg but I have ran out of ideas and am fairly new to Linux. Any direction would be most appreciated.
Thanks,
Billiant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2016 08:47 PM
тАО05-18-2016 08:47 PM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
Versions 10.20 an 10.30 were indeed missing some NFS components, it was fixed in version 10.40. You need to add network=1 to the boot line options in 10.40 for NFS to work properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2016 01:19 PM
тАО06-01-2016 01:19 PM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
I do have network=1 in the pxe boot options. NFS does work as I am able to pxeboot over the network and I can mount a folder on the booted server but must do it manually, that is by typing the mount command.
Here are the options I currently have set.:
label toolkit1
kernel vmlinuz
append initrd=initrd.img root=/dev/ram0 rw ramdisk_size=769344 network=1 ide=nodma ide=noraid pnpbios=off numa=off media=net sstk_mount=10.0.0.1:/sstk1040 sstk_mount_type=nfs sstk_mount_options=rw,nolock sstk_conf=toolkit.conf sstk_script=/scripts/deploy.sh hostname=kepler BOOTDEVICEMP=/mnt/main
Thanks,
Billiant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2016 07:57 AM - edited тАО07-05-2016 08:02 AM
тАО07-05-2016 07:57 AM - edited тАО07-05-2016 08:02 AM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
I am bad at English.
Please understand me.
Toolkit 10.40 is running the init file instead of bootstrap.sh.
Anyway the two files there is a typo. (bootstrap.sh, init)
grep ssstk_mount /proc/cmdline <--- This is a part.
Not a ssstk_mount
Right sstk_mount
Even if difficult, but modifying the files directly.
Put the following values the grub.cfg(uefi mode) or default(legacy mode) file options.
ssstk_mount_test="Hummmm" <---- contain only "ssstk_mount"
Good hope well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2016 07:39 AM
тАО07-11-2016 07:39 AM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
The toolkit bootstrap looks for 'sstk_mount' which is specified on the boot line, make sure your boot line has sstk and not ssstk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2016 11:36 PM
тАО07-31-2016 11:36 PM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
I'm having a same issue.
Do you have workaround ?
Same setup is running fine with 8.70 not sure what have changed for 10.40 but NFS share not able to mount and getting include file not found issue.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2016 04:04 AM
тАО08-01-2016 04:04 AM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
do you have 'network=1' listed as a boot line option?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2016 02:07 PM
тАО08-11-2016 02:07 PM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
the initrd.img from 10.10 also works better, at least it doesn't end with no job control in this shell message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2016 02:34 PM
тАО08-11-2016 02:34 PM
Re: Scripting Toolkit (stk) 10.40 bootstrap.sh ends with error
I've been using HTTP for some time now so I hadn't noticved any of the NFS issues. For now, here is a workaround if you want to write data out to an NFS mount. This workaround uses PXE and HTTP to boot into the toolkit, then you just have to manuall add your NFS mount from within a script.