SG-1000 problems. Will not work. Brand new unit.



  • Just got the unit and have yet to configure.  Unit was unplugged before shutting down which may be the cause but not sure.  odd that the unit is running a Beta version! 2.4 Beta?

    Unit will not allow login.  Below is what happens when connecting via console.

    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.03.30 15:29:13 =~=~=~=~=~=~=~=~=~=~=~=

    U-Boot SPL 2016.03 (Dec 28 2016 - 11:09:45)
    Trying to boot from MMC
    Card did not respond to voltage select!
    *** Warning - MMC init failed, using default environment

    reading u-boot.img
    reading u-boot.img

    U-Boot 2016.03 (Dec 28 2016 - 11:09:45 -0600)

    Watchdog enabled

    I2C:  ready

    DRAM:  512 MiB

    MMC:  OMAP SD/MMC: 0, OMAP SD/MMC: 1

    Card did not respond to voltage select!

    ** Bad device mmc 0 **

    Using default environment

    Net:  <ethaddr>not set. Validating first E-fuse MAC

    cpsw, usb_ether

    starting USB…

    USB0:  Port not available.

    ** Bad device usb 0 **

    Card did not respond to voltage select!

    ** Bad device mmc 0 **

    Hit any key to stop autoboot:  2  1  0

    Booting from: mmc 1 ubldr.bin

    reading ubldr.bin

    217364 bytes read in 19 ms (10.9 MiB/s)

    Starting application at 0x88000000 ...

    Consoles: U-Boot console

    Compatible U-Boot API signature found @0x9ef3ab58

    FreeBSD/armv6 U-Boot loader, Revision 1.2

    (root@buildbot2.netgate.com, Thu Jan 12 12:12:50 CST 2017)

    DRAM: 512MB

    Card did not respond to voltage select!

    Card did not respond to voltage select!

    Card did not respond to voltage select!

    Discarding further error messages

    Number of U-Boot devices: 3

    U-Boot env: loaderdev='mmc 1'

    Found U-Boot device: disk

    Checking unit=1 slice= <auto>partition=<auto>... good.

    Booting from disk1s2a:

    |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\console comconsole is invalid!

    console vidconsole is invalid!

    no valid consoles!

    Available consoles:

    uboot

    |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-/boot/kernel/kernel data=0x11dd5e4+0x52a1c \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\syms=[0x4+0xad710|/-\|+0x4+0xc705f/-\|/-\]

    Hit [Enter] to boot immediately, or any other key for command prompt.

    Booting [/boot/kernel/kernel] in 2 seconds…
    Booting [/boot/kernel/kernel] in 1 second…
    Booting [/boot/kernel/kernel]…

    |/-\|/-\|/-\|/-\|/-/boot/dtb/ufw.dtb size=0x79dd

    Loaded DTB from file 'ufw.dtb'.

    \|/-\Kernel entry at 0x0x88200100...

    Kernel args: (null)

    Copyright (c) 1992-2016 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 11.0-RELEASE-p6 #0 65e7874e6fa(RELENG_2_4): Thu Jan 12 12:15:23 CST 2017
        root@buildbot2.netgate.com:/xbuilder/pfsense-crossbuild/work/obj-ufw-armv6/arm.armv6/builder/factory/tmp/FreeBSD-src/sys/pfSense-uFW arm
    FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0)
    WARNING: too long kenv string, ignoring uboot.Fatboot=env exists loaderdev || env set loaderdev ${fatdev}; env exists UserFatboot && run UserFatboot; env exists trynetboot && env exists Netboot && run Netboot; echo Booting from: ${fatdev} ${bootfile}; fatload ${fatdev} ${loadaddr} ${bootfile} && go ${loadaddr};
    CPU: Cortex A8-r3 rev 2 (Cortex-A core)
    Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext
    WB enabled LABT branch prediction disabled
    LoUU:2 LoC:3 LoUIS:1
    Cache level 1:
    32KB/64B 4-way data cache WT WB Read-Alloc
    32KB/64B 4-way instruction cache Read-Alloc
    Cache level 2:
    256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc
    real memory  = 536870912 (512 MB)
    avail memory = 503078912 (479 MB)
    Texas Instruments AM335x Processor, Revision ES1.2
    ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_bss_fw, 0xc031a2e4, 0) error 1
    ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc031a394, 0) error 1
    ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
    ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc031a444, 0) error 1
    iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (iwi_bss_fw, 0xc032415c, 0) error 1
    iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc032420c, 0) error 1
    iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
    iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc03242bc, 0) error 1
    wlan: mac acl policy registered
    random: entropy device external interface
    ofwbus0: <open firmware="" device="" tree="">simplebus0: <flattened device="" tree="" simple="" bus="">on ofwbus0
    simplebus1: <flattened device="" tree="" simple="" bus="">on simplebus0
    simplebus2: <flattened device="" tree="" simple="" bus="">mem 0x210000-0x211fff on simplebus1
    ti_scm0: <ti control="" module="">mem 0-0x7ff on simplebus2
    aintc0: <ti aintc="" interrupt="" controller="">mem 0x48200000-0x48200fff on simplebus0
    aintc0: Revision 5.0
    cpulist0: <open firmware="" cpu="" group="">on ofwbus0
    cpu0: <open firmware="" cpu="">on cpulist0
    pmu0: <performance monitoring="" unit="">on ofwbus0
    am335x_prcm0: <am335x power="" and="" clock="" management="">mem 0x200000-0x203fff on simplebus1
    am335x_prcm0: Clocks: System 24.0 MHz, CPU 550 MHz
    ti_pinmux0: <ti pinmux="" module="">mem 0x800-0xa37 on simplebus2
    am335x_scm0: <am335x control="" module="" extension="">on ti_scm0
    gpio0: <ti am335x="" general="" purpose="" i="" o="" (gpio)="">mem 0x44e07000-0x44e07fff on simplebus0
    gpiobus0: <ofw gpio="" bus="">on gpio0
    gpioc0: <gpio controller="">on gpio0
    gpio1: <ti am335x="" general="" purpose="" i="" o="" (gpio)="">mem 0x4804c000-0x4804cfff on simplebus0
    gpiobus1: <ofw gpio="" bus="">on gpio1
    gpioc1: <gpio controller="">on gpio1
    gpio2: <ti am335x="" general="" purpose="" i="" o="" (gpio)="">mem 0x481ac000-0x481acfff on simplebus0
    gpiobus2: <ofw gpio="" bus="">on gpio2
    gpioc2: <gpio controller="">on gpio2
    gpio3: <ti am335x="" general="" purpose="" i="" o="" (gpio)="">mem 0x481ae000-0x481aefff on simplebus0
    gpiobus3: <ofw gpio="" bus="">on gpio3
    gpioc3: <gpio controller="">on gpio3
    uart0: <ti uart="" (16550="" compatible)="">mem 0x44e09000-0x44e0afff on simplebus0
    uart0: console (115384,n,8,1)
    iichb0: <ti i2c="" controller="">mem 0x44e0b000-0x44e0bfff on simplebus0
    iichb0: I2C revision 4.0 FIFO size: 32 bytes
    iicbus0: <ofw i2c="" bus="">on iichb0
    iic0: <i2c generic="" i="" o="">on iicbus0
    icee0: <at24c02>at addr 0xa0 on iicbus0
    iichb1: <ti i2c="" controller="">mem 0x4802a000-0x4802afff on simplebus0
    iichb1: I2C revision 4.0 FIFO size: 32 bytes
    iicbus1: <ofw i2c="" bus="">on iichb1
    iic1: <i2c generic="" i="" o="">on iicbus1
    sdhci_ti0: <ti mmchs="" (sdhci="" 2.0)="">mem 0x48060000-0x48060fff on simplebus0
    mmc0: <mmc sd="" bus="">on sdhci_ti0
    sdhci_ti1: <ti mmchs="" (sdhci="" 2.0)="">mem 0x481d8000-0x481d8fff on simplebus0
    mmc1: <mmc sd="" bus="">on sdhci_ti1
    ti_wdt0: <ti watchdog="" timer="">mem 0x44e35000-0x44e35fff on simplebus0
    ti_mbox0: <ti system="" mailbox="">mem 0x480c8000-0x480c81ff on simplebus0
    ti_mbox0: revision 4.0
    am335x_dmtimer0: <am335x dmtimer2="">mem 0x48040000-0x480403ff on simplebus0
    Event timer "DMTimer2" frequency 24000000 Hz quality 500
    am335x_dmtimer1: <am335x dmtimer3="">mem 0x48042000-0x480423ff on simplebus0
    Timecounter "DMTimer3" frequency 24000000 Hz quality 500
    usbss0: <ti am33xx="" integrated="" usb="" otg="" controller="">mem 0x47400000-0x47400fff on simplebus0
    usbss0: TI AM335X USBSS v0.0.13
    musbotg0: <ti am33xx="" integrated="" usb="" otg="" controller="">mem 0x47401400-0x474017ff,0x47401000-0x474011ff on usbss0
    usbus0: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM
    usbus0 on musbotg0
    musbotg1: <ti am33xx="" integrated="" usb="" otg="" controller="">mem 0x47401c00-0x47401fff,0x47401800-0x474019ff on usbss0
    usbus1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM
    usbus1 on musbotg1
    cpswss0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a1007ff,0x4a101200-0x4a1012ff on simplebus0
    cpswss0: CPSW SS Version 1.12 (0)
    cpswss0: Initial queue size TX=128 RX=384
    cpsw0: <ethernet switch="" port="">on cpswss0
    miibus0: <mii bus="">on cpsw0
    micphy0: <micrel 10="" 100="" 1000="" ksz9031="" phy="">PHY 1 on miibus0
    micphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
    cpsw0: Ethernet address: ec:11:27🇩🇪1e:e6
    cpsw1: <ethernet switch="" port="">on cpswss0
    miibus1: <mii bus="">on cpsw1
    micphy1: <micrel 10="" 100="" 1000="" ksz9031="" phy="">PHY 2 on miibus1
    micphy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
    cpsw1: Ethernet address: ec:11:27🇩🇪1e:e8
    etherswitch0: <switch controller="">on cpswss0
    ti_adc0: <ti adc="" controller="">mem 0x44e0d000-0x44e0dfff disabled on simplebus0
    ti_adc0: scheme: 0x1 func: 0x730 rtl: 0 rev: 0.1 custom rev: 0
    cryptosoft0: <software crypto="">Timecounters tick every 10.000 msec
    usbus0: 480Mbps High Speed USB v2.0
    usbus1: 480Mbps High Speed USB v2.0
    mmc0: No compatible cards found on bus
    ugen0.1: <mentor graphics="">at usbus0
    uhub0: <mentor 1="" 9="" graphics="" otg="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus0
    ugen1.1: <mentor graphics="">at usbus1
    uhub1: <mentor 1="" 9="" graphics="" otg="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus1
    uhub1: 1 port with 1 removable, self powered
    uhub0: 1 port with 1 removable, self powered
    mmcsd0: 4GB <mmchc 112="" 2000="" m62704="" 0.1="" sn="" 368aceb4="" mfg="" 06="" by="" 0x0000="">at mmc1 48.0MHz/8bit/65535-block
    Trying to mount root from ufs:/dev/ufsid/5877c8cdceaf14b9 [rw,noatime]…
    WARNING: / was not properly dismounted
    warning: no time-of-day clock registered, system time will not be set accurately
    Configuring crash dumps...
    No suitable dump device was found.
    ** SU+J Recovering /dev/ufsid/5877c8cdceaf14b9
    ** Reading 7503872 byte journal from inode 4.
    ** Building recovery table.
    ** Resolving unreferenced inode list.
    ** Processing journal entries.
    ** 18 journal records in 2560 bytes for 22.50% utilization
    ** Freed 0 inodes (0 dirs) 0 blocks, and 2 frags.

    ***** FILE SYSTEM MARKED CLEAN *****
    Filesystems are clean, continuing...
    Mounting filesystems...
    random: unblocking device.

    ___
    / f
    / p _
    / Sense
    _

        _
    _/

    Welcome to pfSense 2.4.0-BETA...

    Dump device does not exist.  Savecore not run.
    ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.24/mach/CORE
    Soft Float compatibility ldconfig path:
    done.
    panic: ufs_dirbad: /: bad dir ino 58890 at offset 512: mangled entry
    Uptime: 27s
    Automatic reboot in 15 seconds - press a key on the console to abort</mmchc></mentor></mentor></mentor></mentor></software></ti></switch></micrel></mii></ethernet></micrel></mii></ethernet></ti></ti></ti></am335x></am335x></ti></ti></mmc></ti></mmc></ti></i2c></ofw></ti></at24c02></i2c></ofw></ti></ti></gpio></ofw></ti></gpio></ofw></ti></gpio></ofw></ti></gpio></ofw></ti></am335x></ti></am335x></performance></open></open></ti></ti></flattened></flattened></flattened></open></auto></auto></ethaddr>


  • Banned

    panic: ufs_dirbad

    Looks like UFS corruption due to a hard shutdown. This is not unheard of.

    Fortunately, there is a fix! ZFS install! Just reinstall with 2.4.0 BETA and select ZFS install.
    ZFS is an exceptionally resilient file system. You won't get corruption from a power outage with ZFS.



  • contact netgate support


  • Rebel Alliance Netgate Administrator

    Kapara has contacted support, we resolved the issue.


  • Galactic Empire Netgate Administrator

    The reason for the problem (file corruption) was communicated in the ticket I opened for you as soon as you reported the problem.  It appears you have removed power before properly shutting it down. The reason that it runs 2.4-BETA has also been explained.

    Continue to work with my team to resolve the issue.


  • Banned

    The joys of UFS…



  • Thanks for creating the ticket.  I am concerned though if something can get corrupted so easily this could be a real problem when deploying these to many locations far away!  I am looking at deploying these in places that I would have to fly several hours if not more to fix if they fail.  Is pfsense going to do something so that they are more resilient to power failures?

    All other platforms I use do not get corrupted from power failues.  Cisco ASA, Switches,  Juniper Firewall, Ubiquiti Router and Unifi AP's.



  • Read up - ZFS is your solution. Currently it requires a fresh install of 2.4.0 Beta.

    Alternatively, connect it to a UPS like all decent hardware should be ;)


  • Banned

    This isn't a pfSense problem, it's an anything that uses UFS problem.

    @kapara:

    Is pfsense going to do something so that they are more resilient to power failures?

    They did, they implemented ZFS in 2.4

    ZFS install is included in the Auto configuration guide. Just install to ZFS and you will never have this problem again.



  • Yes I get the UPS option but this unit will be mounted in a box up in the air in a greenhouse so mounrting a battery also causes some serious design issues unless there is a small battery which can be attached which can fit in the palm of my hand.  Lik an inline battery that matches the voltage.  Like for a raid card.

    Support mentioned that ZFS would not be recommended for this unit because of the resources required by ZFS and the SG-1000 cannot handle that.

    Open to more suggestions!



  • ZFS is a much more robust file system but it is not immune to corruption from power loss. If you need that guarantee get a UPS.



  • Something like this would be perfect!  http://www.mini-box.com/OpenUPS2


  • Banned

    @Jailer:

    not immune to corruption from power loss

    Technically correct, but you are highly unlikely to have this happen with ZFS.

    What's really great about ZFS though are all of the tools that it includes.

    In addition to tools to recover from data corruption, you can automate on site or off site backups of your entire pool pretty easily.

    If you back up your pool, then you can only lose whatever happened between the time corruption took place and your last backup.



  • @pfBasic:

    Technically correct, but you are highly unlikely to have this happen with ZFS.

    Until you corrupt the metadata and then you're screwed. But luckily for pfSense this isn't an issue since reinstalling and restoring the config is trivial as long as you have a current config backed up.



  • @Jailer:

    reinstalling and restoring the config is trivial as long as you have a current config backed up.

    This is quite true, and everyone should back up their config regularly IMO.

    Correct me if I'm wrong, but isn't one of the perks of having official pfSense hardware that it includes a subscription that makes automated periodic config backup easy?



  • @whosmatt:

    Correct me if I'm wrong, but isn't one of the perks of having official pfSense hardware that it includes a subscription that makes automated periodic config backup easy?

    I believe you are correct. I save a copy of my config to my desktop any time I make any changes.



  • @Jailer:

    I believe you are correct. I save a copy of my config to my desktop any time I make any changes.

    Always good practice.  I take it a step further and use a simple cron job with scp to copy /conf nightly.  But the auto config backup included in the Gold subscription (I verified, and it does come, for a year anyway, with any official hardware purchase from the store) makes it trivial.  Definite bonus, and since OP has the hardware newly purchased, one to take advantage of.


Log in to reply