SG1000 bricked twice now, ufs dir bad



  • Hi guys, I bricked my first SG1000 and tried everything short of going to Uni and learn Computer science. I just bought a new one which I then loaded the config one and after a reboot (possibly a cold one) the unit is now bricked. it constantly reboots. one I connected the serial port It says ufs dir bad and reboots every 2( seconds reboot. Honestly, whilst this is a great product it is not possible that you brick the box so easily by admittingly possibly removing power. This can happen in real life too. So I am frustrated now. Happy to someone to have a look at it with remote serial connection and fix it for me, happy to pay. Still frustrated though, cannot really recommend. :(


  • LAYER 8 Global Moderator

    "Still frustrated though"

    And did you call for support?



  • Mine refused to boot up as soon as I got it and plugged it in, it took a good two hours to get it to a "working" condition, and then it would freeze about every 48 hours or so.


  • LAYER 8 Global Moderator

    those sort of issue you should really call for support.  Maybe there is something wrong with the hardware, etc.



  • I would agree that they are more power sensitive than my other units.  None of my units running 2.2 or 2.3 have these issues.  Only my SG-1000.  I use mine primarily as a emergency replacement and or demo unit for basic features.



  • It's an ARM system and FreeBSD on ARM is still much more of "work in progress" than on the more established platforms. There are going to be teething problems like this until the kinks get sorted out by FreeBSD devs and the manufacturers of these devices.

    "ufs dir bad" suggests that the unit could be fixed by booting into single user mode (usually by selecting single user boot from the FreeBSD boot menu) and running 'fsck -y /dev/<rootfilesystem>' on the root filesystem.

    If it's the boot code spitting out the error and the boot never makes it to the /boot/loader menu then the only solution would be then somehow mount the eMMC card on another pfSense/FreeBSD system run the fsck there.</rootfilesystem>


  • Galactic Empire

    @kpa:

    It's an ARM system and FreeBSD on ARM is still much more of "work in progress" than on the more established platforms. There are going to be teething problems like this until the kinks get sorted out by FreeBSD devs and the manufacturers of these devices.

    "ufs dir bad" suggests that the unit could be fixed by booting into single user mode (usually by selecting single user boot from the FreeBSD boot menu) and running 'fsck -y /dev/<rootfilesystem>' on the root filesystem.

    If it's the boot code spitting out the error and the boot never makes it to the /boot/loader menu then the only solution would be then somehow mount the eMMC card on another pfSense/FreeBSD system run the fsck there.</rootfilesystem>

    It's a FreeBSD file system issue, happens across all platforms. FreeBSD on ARM is established, there's always room for improvement. If someone has power issues they should put UPS in place.


Log in to reply