Cannot open package error 22

• 1. 
  Install Junos OS from USB

  

  Hello guys,

  Any help would be greatly appriciated 🙂

  I am trying to install/boot the Junos on my SRX300 using USB. (Just for learning purpose)

  Let’s sayI have tried to upgrade th Junos using the ‘request system software add’ method and it was unsuccessful. Now I can’t get to the CLI. 

  If I want to install / boot the SRX from the USB, how do I do that? I copied the Junos image into pen drive and went to ‘loader’ prompt. 

  loader> install file :///junos-srxsme-15.1X49-D120.3-domestic.tgz
  Target device selected for installation: internal media
  cannot open package (error 22)

  But it does not work. 😞 

  Note — SRX currently running at junos-srxsme-15.1X49-D120.3-domestic.tgz. 

  Thanks

• 2. 
  RE: Install Junos OS from USB

  

• 3. 
  RE: Install Junos OS from USB

  

  Thanks 🙂

  I have read most them already but could not figure out the issue. 

  Suresh

• 4. 
  RE: Install Junos OS from USB

  

  What issue are you facing?

• 5. 
  RE: Install Junos OS from USB

  

  I am trying to install Junos from USB via Boot loader. (See the first post)

  Because the previous upgrade was unsuccessful using the normal ‘request system software add ‘ command. After the reboot SRX is unstable and unable to go to the CLI. Even If I go to the CLI it is too slow and ‘Status alarm is amber’

  My alternate partition has the older Junos which is stable but I am also unablr to boot from the back up partition. (Not sure how to do it)

  My friend suggested to Install the Junos from USB via Boot  loader. But I am unable to do so.

  Thanks

• 6. 
  RE: Install Junos OS from USB

  Best Answer

  

• 7. 
  RE: Install Junos OS from USB

  

  Hi mate,

  Thanks for getting back to me.

  This is the command I entered on the loader:

  loader> install file :///junos-srxsme-15.1X49-D120.3-domestic.tgz
  Target device selected for installation: internal media 
  cannot open package (error 22)

  But it doesn’t install.

  Thanks

  Suresh

• 8. 
  RE: Install Junos OS from USB

  

• 9. 
  RE: Install Junos OS from USB

  

FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 26704 free (16 frags, 3336 blocks, 0.0% fragmentation)
Can't stat /dev/da0s3e: No such file or directory
Can't stat /dev/da0s3e: No such file or directory
mount: /dev/da0s3e : No such file or directory
/var: file system mount failed, startup aborted
JWARNING: system watchdog timer still running,
use '/sbin/watchdog -off' to disable
Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh:
 

# bsdlabel /dev/da0s3
bsdlabel: /dev/da0s3: no valid label found
 

 Firmware Version:01.00.00
 
USB:   scanning bus for devices... 4 USB Device(s) found
 
       scanning bus for storage devices... 2 Storage Device(s) found

** /dev/da1s1f

** Last Mounted on /var

** Phase 1 — Check Blocks and Sizes

** Phase 2 — Check Pathnames

UNALLOCATED I=7 OWNER=39 MODE=0

SIZE=0 MTIME=Aug 10 13:32 2015

NAME=/lost+found

REMOVE? yeumass1: BBB reset failed, IOERROR

s

** Phase 3 — Check Connectivity

UNREF DIR I=329730 OWNER=0 MODE=40755

SIZE=512 MTIME=Juumass1: BBB bulk-in clear stall failed, IOERROR

l 17 17:31 2014

RECONNECT? yes

NO lost+found DIRECTORY

CREATE? yes

DIR I=329730 CONNECTED. PARENT WAS I=7

UNREF DIR I=329729 OWNER=0 MODE=40755

SIZE=512 MTIME=Jul 17 17:18 2014

RECONNECT? yes

DIR I=329729 CONNECTED. PARENT WAS I=7

UNREF DIR I=329728 OWNER=0 MODE=40555

SIZE=512 MTIME=Jul 17 17:14 2014

RECONNECT? yes

DIR I=329728 CONNECTED. PARENT WAS I=7

UNREF DIR I=94208 OWNER=0 MODE=40755

SIZE=512 MTIME=May 3 07:30 2016

RECONNECT? yes

DIR I=94208 CONNECTED. PARENT WAS I=7

UNREF DIR I=306176 OWNER=0 MODE=40755

SIZE=512 MTIME=Sep 8 03:31 2015

RECONNECT? yes

DIR I=306176 CONNECTED. PARENT WAS I=7

UNREF DIR I=306178 OWNER=0 MODE=40775

SIZE=512 MTIME=Apr 9 15:52 2015

RECONNECT? yes

DIR I=306178 CONNECTED. PARENT WAS I=7

UNREF DIR I=306177 OWNER=0 MODE=40775

SIZE=512 MTIME=Jul 17 17:18 2014

RECONNECT? yes

CANNOT WRITE BLK: 4894816

CONTINUE? yes

umass1: BBB bulk-out clear stall failed, TIMEOUT

THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 4894816, 4894817, 4894818, 4894819,

CANNOT READ BLK: 4894820

CONTINUE? yes

WARNING: The installation will erase the contents of your disks.

Do you wish to continue (y/n)?

y

Setting ospackage=jboot-ppc-13.3R8.7.tgz, configpackage=

Setting packlist=jbundle-ppc-13.3R8.7-domestic.tgz

Packages mounted from the install media

Partitioning da0 …

bsdlabel: /dev/da0s1: No such file or directory

Could not read old disklabel for da0s1, creating new label.

fdisk: invalid fdisk partition table found

fdisk: read_s0: Unknown error: 0

ERROR: unable to determine size of da0

You are now in a debugging subshell (you may not see a prompt)…

#

• Применить ограничения страницы

• Добавлено Технический писатель, редактировано Технический писатель окт 18, 2021

Как правильно устанавливать стороннее ПО

Стороннее ПО можно устанавливать только в корневую файловую систему*, но не в контейнер, так как при обновлении во всех контейнерах перезатираются все каталоги, кроме:

• /var/
• /etc/
• /cfg/
• /mnt/

yum

Тем не менее, иногда возникает потребность в установке утилит отсутствующих в стандартной поставке. Перечень пакетов, установка которых (вместе с зависимостями из официальных репозиториев CentOS) не приведёт к плачевным последствиям:

• wget
• usbutils
• iperf
• vnstat
• parted
• util-linux
• hdparm
• smartmontools
• mc
• iftop
• nethogs
• vnstat
• bwm-ng
• atop
• atopsar
• htop
• jq
• yum-utils
• hpssacli
• xsos

При необходимости установить что-либо отсутствующее в списке, обратитесь в техподдержку.

Проблемы при установке пакетов

error: cannot open Packages database in /var/lib/rpm

Перестройте базу индексов rpm:

mv /var/lib/rpm/__db* /tmp
rpm --rebuilddb

После чего очистите кеш и историю:

yum clean dbcache
yum history new

[Errno 14] PYCURL ERROR 22 — «The requested URL returned error: 404»

Известны две возможные причины этой ошибки:

• Файл недоступен на сервере.
  В случае, yum install завершился ошибкой:

  "[Errno 256] No more mirrors to try"

  вероятней всего причина другая:

• Не обновляется кеш.

Решением второй проблемы может стать временно отключение кеша yum в конфиге /etc/yum.conf. Добавьте в файл следующую строку:

После установки ПО лучше эту строку убрать.