Hello, The other day I (foolishly) decided that I'd upgrade my bash to pickup the SHellShock fixes.
I did a
apt-get update apt-get upgrade
and took all of the ( quite a few ) upgrade suggestions. (I'd done this before w/o problems).
Looks like that wasnt so smart.
Now my system gets stuck on "Checking root FS".
If I boot into telnet mode and go in there, I can see /sysroot/var/log/dpkg.log has tons of error messages about half-configured pacakges.
/sysroot/var/log # cat dpkg.log | grep half | sort -u | grep netgear 2014-09-27 03:57:40 status half-configured udev 0.125-7.netgear1 2014-09-27 03:57:40 status half-installed udev 0.125-7.netgear1 2014-09-27 03:57:48 status half-installed udev 0.125-7.netgear1 2014-09-27 03:59:01 status half-configured apache2 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:01 status half-installed apache2 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:02 status half-configured apache2-mpm-prefork 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:04 status half-configured apache2.2-common 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:04 status half-installed apache2-mpm-prefork 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:04 status half-installed apache2.2-common 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:06 status half-configured apache2.2-bin 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:06 status half-installed apache2.2-bin 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:06 status half-installed apache2.2-common 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:07 status half-configured apache2-utils 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:07 status half-installed apache2-utils 2.2.16-6+squeeze1.netgear1 2014-09-27 03:59:23 status half-configured nut-snmp 2.0.5-0.netgear12 2014-09-27 03:59:23 status half-installed nut-snmp 2.0.5-0.netgear12
and then my syslog has lots of complaints about:
Sep 27 03:57:20 envy init: Trying to re-exec init Sep 27 03:57:33 envy init: Trying to re-exec init Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'SYMLINK{unique}' in /lib/udev/rules.d/50-udev-default.rules:1 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'SYMLINK{unique}' in /lib/udev/rules.d/50-udev-default.rules:2 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:11 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:14 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:17 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:20 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:23 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:26 .... Sep 27 03:57:20 envy init: Trying to re-exec init Sep 27 03:57:33 envy init: Trying to re-exec init Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'SYMLINK{unique}' in /lib/udev/rules.d/50-udev-default.rules:1 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'SYMLINK{unique}' in /lib/udev/rules.d/50-udev-default.rules:2 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:11 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:14 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:17 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:20 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:23 Sep 27 03:57:48 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:26 ... Sep 27 03:59:23 envy udevd[838]: add_to_rules: unknown key 'TAG' in /lib/udev/rules.d/70-acl.rules:81 Sep 27 03:59:32 envy snmpd[4854]: iquerySecName has not been configured - internal queries will fail Sep 27 03:59:32 envy snmptrapd[4855]: Warning: no access control information configured. (Config search path: /etc/snmp:/usr/share/snmp:/usr/lib/snmp:/root/.snmp) This receiver will *NOT* accept any incoming notifications. Sep 27 03:59:32 envy snmptrapd[4856]: NET-SNMP version 5.4.3 Sep 27 03:59:32 envy snmpd[4854]: Turning on AgentX master support. Sep 27 03:59:32 envy snmpd[4854]: NET-SNMP version 5.4.3 Sep 27 03:59:47 envy snmptrapd[4856]: NET-SNMP version 5.4.3 AgentX subagent connected
Im wondering what I can do.
My ideas are
either get access to a boot level where I can run some dpgk commands to cleanup the bad apt-get upgrade
ask for help mounting the data partition and move all my media off, then do a reset
attach a monitor/keyboard so i can watch the console boot .. how does one do this on an NV+ v2? the only connector is the USB backup port..
go into telnet mode, hack the boot sequence to omit the "checking root FS" -- could not find this btw, lots of "print_lcd_line1" and "print_lcd_line2" statements, but the "Checking root FS" statement seems to come from somewhere before the normal rc.d init scripts.
We don't recommend doing an apt-get upgrade. It is safer to just update the packages you need to update.
We will have beta firmware available soon addressing ShellShock for the NV+ v2. Like OS6, RAIDiator 5.3.x is not vulnerable to ShellShock via CGI (web browser) as we don't use bash as a command interpreter for it. Nonetheless we will be updating bash on these systems.
