Alix 2D13 - Have you upgrade to 2.3 ? Did it go okey?



  • Regarding the new update; https://blog.pfsense.org/?p=2008

    I'm running Alix 2D13; 2.2-RELEASE (i386), built on Thu Jan 22 14:04:25 CST 2015, FreeBSD 10.1-RELEASE-p4
    Uptime 435 Days 12 Hours 07 Minutes 44 Seconds

    Before I start to upgrade my "connection" with the world.. (I do not have a spare Alix box to test on) I want to ask if someone has done this before me ?
    I also run some custom scripts which checks if the connection is up/down, and reboots the device is necessary.. guessing they may stopp working after an upgrade.. (but ready for that :-))



  • I tested upgrades on an ALIX with no issue.



  • Hello
    I use an Alix 2d3, I shouldn't have upgraded, it became so slow I keep having 504 or timeout errors :/

    My bad, it may be written on the release note I didn't read, I'm looking for it now
    New web UI was a good surprise and then a less good one


  • Rebel Alliance Developer Netgate

    It's fine, better if you go to Diag > NanoBSD and set it to be permanently read-write. Especially on older/slower CF cards.



  • I can't reach almost any page :( Only the home page manages to load

    I was searching for serial config too

    Will be great if I can change the setting you give and make it working

    thanks

    Edit: got the page and changed the setting ! :) I'll use it as is for now while saving money for a more powerful solution
    It became usable ! Thank you very much


  • Rebel Alliance Developer Netgate

    From the console or SSH shell, run:

    /etc/rc.conf_mount_rw

    Then back out to the menu and run option 16, and then try to login and go directly to that page.



  • Just upgraded my Alix 2D13 4GB at home from 2.2.6 to 2.3. It went well and performance is overall good once I enable the R/W on the CF card.
    No problems to report for now.



  • @jimp:

    It's fine, better if you go to Diag > NanoBSD and set it to be permanently read-write. Especially on older/slower CF cards.

    Is this a known issue?
    Since I set permanently read-write my ALIX board work fine again with 2.3.


  • Rebel Alliance Developer Netgate

    It's due to the slow speed of the CF and the number of times it gets switched to/from read-write.

    On 2.2 and 2.3 the OS more strictly writes changes out during such transitions, otherwise data loss can occur. The main side effect is lowered performance.

    There really isn't a requirement to do the ro/rw switch, the system will only write when necessary, it was just an extra safety measure. Packages might be less obedient but that's still not something that would be a constant worry, or the packages would have been broken on NanoBSD without the switch.


  • Rebel Alliance Developer Netgate

    That's something for a new thread.

    There is already a thread going for gateway monitoring issues with some suggestions, like editing and saving the gateway(s) to re-apply settings for dpinger that may not have worked since they were upgraded from apinger



  • Upgraded Alix 2D13 4GB from 2.2.6 to 2.3, outbound NAT stopped working, had to disable all the entries in Firewall NAT and Rules related to [not yet reinstalled] pfBlockerNG package. Reinstalling packages right now.



  • The upgrade went ok, the box is running and the firewall seems to continue to work as expected.

    As for the GUI… The update email promised a "new responsive look and feel to pfSense requiring a minimum of resizing or scrolling on  a wide range of devices". Turns out, the opposite is the case. People have already commented about the GUI being so slow as to be unusable on Alix, unless you mount the CF card R/W permanently. And second the fonts and UI elements have increased in size, making the pull-down menus go off the bottom of my screen. In general, the new UI makes really bad use of screen real-estate and requires more scrolling than the old for me.

    Last point, the check for available updates gets stuck on "Obtaining update status" forever...

    Bottom line: the box still works, but barely.



  • So I tried to make the card be mounted R/W permanently. Trying to save that setting, ironically gives me an "Unable to open /cf/conf/config.xml for writing in write_config() @ 2016-04-13" error. Looks like the GUI wants to write to the R/O card !?

    Here the full output, which I don't understand:

    Warning: copy(/cf/conf/backup/config-1460498200.xml): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 920 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4232 829600 4. copy() /etc/inc/config.lib.inc:920 Warning: filesize(): stat failed for /cf/conf/backup/config-1460498200.xml in /etc/inc/config.lib.inc on line 927 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4695 832788 4. filesize() /etc/inc/config.lib.inc:927 Warning: fopen(/cf/conf/backup/backup.cache): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 928 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4940 833004 4. fopen() /etc/inc/config.lib.inc:928 Warning: fwrite() expects parameter 1 to be resource, boolean given in /etc/inc/config.lib.inc on line 929 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4962 834004 4. fwrite() /etc/inc/config.lib.inc:929 Warning: fclose() expects parameter 1 to be resource, boolean given in /etc/inc/config.lib.inc on line 930 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 21.2117 829436 3. backup_config() /etc/inc/config.lib.inc:553 21.4987 832972 4. fclose() /etc/inc/config.lib.inc:930 Warning: fopen(/cf/conf/config.xml.10269): failed to open stream: Read-only file system in /etc/inc/config.lib.inc on line 495 Call Stack: 0.0003 122192 1. {main}() /usr/local/www/diag_nanobsd.php:0 21.2111 829100 2. write_config() /usr/local/www/diag_nanobsd.php:134 40.3610 882688 3. safe_write_file() /etc/inc/config.lib.inc:565 40.3611 882808 4. fopen() /etc/inc/config.lib.inc:495



  • Sorry to keep replying to myself. To get the "Checking for updates…" fixed, I was looking if I was missing pfSense-base as per this sticky post: https://forum.pfsense.org/index.php?topic=109690.0. Well, there is indeed not pfSense-base, but I do have "pfSense-base-nanobsd-2.3" installed. Should I still install pfSense-base as well?

    Thanks for any help!


  • Rebel Alliance Developer Netgate

    @JanW:

    Sorry to keep replying to myself. To get the "Checking for updates…" fixed, I was looking if I was missing pfSense-base as per this sticky post: https://forum.pfsense.org/index.php?topic=109690.0. Well, there is indeed not pfSense-base, but I do have "pfSense-base-nanobsd-2.3" installed. Should I still install pfSense-base as well?

    Thanks for any help!

    No, what you have is fine.

    Did you actually set it to be permanently RW? Or were you only speculating about that bit a couple posts up?



  • Well, each time I check that box and click on "save", I get this error I posted above.
    I also tried the option you mentioned above from the command line.

    The GUI does feel much more responsive now, so maybe it did somehow save the setting, but that checkbox does not remain checked.

    Here a more readable form of the error that keeps repeating:

    Crash report begins.  Anonymous machine information:

    i386
    10.3-RELEASE
    FreeBSD 10.3-RELEASE #5 05adf0a(RELENG_2_3_0): Mon Apr 11 19:14:12 CDT 2016    root@ce23-i386-builder:/builder/pfsense-230/tmp/obj/builder/pfsense-230/tmp/FreeBSD-src/sys/pfSense_wrap_vga

    Crash report details:

    PHP Errors:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  3. backup_config() /etc/inc/config.lib.inc:553
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  4. copy() /etc/inc/config.lib.inc:920
    [13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  3. backup_config() /etc/inc/config.lib.inc:553
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  4. filesize() /etc/inc/config.lib.inc:927
    [13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  3. backup_config() /etc/inc/config.lib.inc:553
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  4. fopen() /etc/inc/config.lib.inc:928
    [13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  3. backup_config() /etc/inc/config.lib.inc:553
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  4. fwrite() /etc/inc/config.lib.inc:929
    [13-Apr-2016 22:42:30 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  3. backup_config() /etc/inc/config.lib.inc:553
    [13-Apr-2016 22:42:30 Europe/Paris] PHP  4. fclose() /etc/inc/config.lib.inc:930
    [13-Apr-2016 22:42:48 Europe/Paris] PHP Stack trace:
    [13-Apr-2016 22:42:48 Europe/Paris] PHP  1. {main}() /usr/local/www/diag_nanobsd.php:0
    [13-Apr-2016 22:42:48 Europe/Paris] PHP  2. write_config() /usr/local/www/diag_nanobsd.php:134
    [13-Apr-2016 22:42:48 Europe/Paris] PHP  3. safe_write_file() /etc/inc/config.lib.inc:565
    [13-Apr-2016 22:42:48 Europe/Paris] PHP  4. fopen() /etc/inc/config.lib.inc:495



  • …turns out I seem get this error for any "save" button on any page. The requested settings are applied, but there seems to be a problem with writing to the configuration file.



  • So the card is still mounted R/O it seems. I did reboot after my first attempt to change that setting, to no avail. Should I maybe remove the "ro" option for /dev/ufs/cf in /etc/fstab?

    [2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: /etc/rc.conf_mount_rw
    [2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: touch config.xml
    touch: config.xml: Read-only file system
    [2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: mount
    /dev/ufs/pfsense1 on / (ufs, local, noatime, synchronous)
    devfs on /dev (devfs, local)
    /dev/ufs/cf on /cf (ufs, local, noatime, read-only, synchronous)
    /dev/md0 on /tmp (ufs, local)
    /dev/md1 on /var (ufs, local)
    devfs on /var/dhcpd/dev (devfs, local)
    [2.3-RELEASE][admin@pfsense.localdomain]/cf/conf: cat /etc/fstab
    /dev/ufs/pfsense1 / ufs ro,sync,noatime 1 1
    /dev/ufs/cf /cf ufs ro,sync,noatime 1 1



  • Like @jimp posted above, when the system has booted, use console menu option 8 to drop to a shell (or SSH in to a shell) and:

    /etc/rc.conf_mount_rw
    

    That will put the disk partitions into read-write.

    Then use the GUI to change to "permanent read-write".

    If you get errors when saving at that point, then maybe there is actually a problem with writing to your CF card.



  • @JanW:

    The upgrade went ok, the box is running and the firewall seems to continue to work as expected.

    As for the GUI… The update email promised a "new responsive look and feel to pfSense requiring a minimum of resizing or scrolling on  a wide range of devices". Turns out, the opposite is the case. People have already commented about the GUI being so slow as to be unusable on Alix, unless you mount the CF card R/W permanently. And second the fonts and UI elements have increased in size, making the pull-down menus go off the bottom of my screen. In general, the new UI makes really bad use of screen real-estate and requires more scrolling than the old for me.

    Last point, the check for available updates gets stuck on "Obtaining update status" forever...

    Bottom line: the box still works, but barely.

    Exactly the same problem here. GUI very slow, check for available updates gets stuck on "Obtaining update status" forever and no access to page "System -> Update"

    I am on this https://www.applianceshop.eu/opnsense-a10-dual-core-rack-edition.html box except with Intel(R) Atom(TM) CPU Z510 @ 1.10GHz, 1GB ram and 4GB nanobsd.

    Also CF card R/W permanently problem?

    @jimp:

    From the console or SSH shell, run:

    /etc/rc.conf_mount_rw

    Then back out to the menu and run option 16, and then try to login and go directly to that page.

    I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.

    Did no have all these problems on 2.2.6.

    Erik



  • I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.

    If that is true then you have much bigger problems. Every install has that file.



  • Hello all !

    Running this ALIX based pfsense appliance, I upgraded to 2.3 yesterday ( nanoBDS 4g )

    Everything works fine so far  8)

    The only drawback I noticed is that the GUI is ( sometimes ) a bit slow to respond ( but the overall lifting was much needed and is really good )


  • Rebel Alliance Developer Netgate

    For those who are seeing "Device busy" or similar and unable to force the disk read-write, try the following (preferably from the console):

    umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf

    Not something we'd normally recommend but somehow it seems that just the /cf slice is getting wedged for some people at the OS level.

    Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.



  • @phil.davis:

    I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.

    If that is true then you have much bigger problems. Every install has that file.

    I did a search for the file on my system:

    admin@nas-server:/$ sudo find / -name rc.conf_mount_rw
    admin@nas-server:/$

    Nothing was found.

    Firewall seems to work normally except for the issues stated in my earlier reply.

    What could I do to correct this?

    Erik



  • @ehoitinga:

    @phil.davis:

    I was not able to try the solution offered by jimp as stated above because the file /etc/rc.conf_mount_rw does not exist on my box.

    If that is true then you have much bigger problems. Every install has that file.

    I did a search for the file on my system:

    admin@nas-server:/$ sudo find / -name rc.conf_mount_rw
    admin@nas-server:/$

    Nothing was found.

    Firewall seems to work normally except for the issues stated in my earlier reply.

    What could I do to correct this?

    Erik

    Hmmm, interesting. In "Diagnostic -> NanoBSD" I have set the Read/Write status to rw and I have set the set the permanent RW flag and did a save. I did not got the errors like JanW did.

    When I go to the dashboard I see that the NanoBSD Boot Slice = pfsense1 / ada0s2(rw). Also the system now tells me that I am on the latest version in stead of staying forever in "Obtaining update status". I can also go to page "System -> Update" now.

    Also the gui seems to be a bit faster.

    Problem solved or should I still worry about the missing rc.conf_mount_rw ?

    [Edit 140416 13:30 CET] I also send an e-mail to the manufacturer (https://www.applianceshop.eu/?___store=en) of my appliance to see if they ran in to this problem also. Keep you posted with the results.

    Erik



  • 2.3 upgrade from 2.2.6 is such a nightmare.

    The proxy crash frequently and causing high disk I/O on Citrix Xen Server. Can not find any available package if using proxy under System - Advance -Misc (my connection stand behind another upstream proxy).

    have to reverse back to 2.2.6 and wait for another patch comming



  • @jimp:

    […]
    Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.

    I see a lot of comments saying that RW should be set instead of the default ( RO ) for NanoBSD : why is that ?  ???

    My current boot slice is in RO but I haven't seen any problems so far


  • Rebel Alliance Developer Netgate

    @craymore:

    @jimp:

    […]
    Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.

    I see a lot of comments saying that RW should be set instead of the default ( RO ) for NanoBSD : why is that ?  ???

    My current boot slice is in RO but I haven't seen any problems so far

    Many CF/SD cards, especially slower ones, are dreadfully slow switching between RW and RO. When functions in the system attempt to switch it on and off a lot, that leads to huge slowdowns on such cards. Even fast cards can get sluggish. In the worst cases, when the card is moving from RW to RO, it blocks other functions.

    The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed or defaulted to RW soon.



  • The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon

    Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.


  • Rebel Alliance Developer Netgate

    @phil.davis:

    The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon

    Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.

    Part of this is that the OS used to play fast & loose with filesystem actions. They completed quick but were NO-OPs and didn't properly sync all data in a safe way. I wrote volumes about that back when we first took out the dangerous patches. I suspect FreeBSD 10.3 might be even safer in how it handles remounting, leading to another slow-down, but I have not yet run an in-depth analysis as I did before. Part of the issue is from pkg needing read/write access to its databases and it can't keep them in RAM disks.



  • just want to share my experience

    upgraded from 2.2.6 to 2.3 on ALIX.2D3 4 hours ago. ran into the same issue with web interface slowness and dashboard stuck on obtaining update status as well. CPU was 100% used.

    change to permanent read/write and disable automatic dashboard auto-update fixed the issue. CPU usage back down to around 4%.

    compared to 2.2.6, web interface seems a bit slower on a low power system like ALIX.2D3.

    other than that, OpenVPN tunnel, Zabbix Agent LTS are working as expected after the upgrade. Zabbix reported host information change and Zabbix agent version changed after the pfSense upgrade.

    going to try upgrading RCC-VE 2440 box later tonight.



  • For what it's worth, I had a very smooth transition from 2.2 -> 2.3. The new UI looks beautiful, and I appreciate the huge amount of new improvements that the team's worked on. Thanks to those who got this out!



  • Hello,
    I did the upgrade yesterday on my home Alix, everything stopped to work, pfSense did not boot anymore.

    The only way I had to restore pfSense was choosing 1 (pfSense 2.2.6) as boot option during the start-up. If I keep the serial console cable connected and I boot with 2.3, the console gets full of garbage chars right after the boot selection.

    Also, all the VPNs were disabled after the boot, both IPSec and PPTP, and the dashboard was completely empty.

    The upgrade was made using the Auto Upgrade feature. I will try again after having disabled pfBlockerNG (looks like has issues to update the database), in the while I leave you this feedback.

    If someone has some information about the console issue after the boot will be appreciated.

    Thanks,
    Michele



  • @mdima:

    The only way I had to restore pfSense was choosing 1 (pfSense 2.2.6) as boot option during the start-up. If I keep the serial console cable connected and I boot with 2.3, the console gets full of garbage chars right after the boot selection.

    Also, all the VPNs were disabled after the boot, both IPSec and PPTP, and the dashboard was completely empty.

    What garbage on the console specifically? Sounds like you had it at a wrong baud rate.

    PPTP is gone, so that is disabled. But the IPsec config doesn't get touched during upgrade. The dashboard being blank also indicates some kind of issue. Trying upgrade again after first uninstalling all packages is a good idea.



  • @cmb:

    What garbage on the console specifically? Sounds like you had it at a wrong baud rate.

    true, even if the Alix sends at 9600bps during the POST, and the console is configured in pfSense at 9600bps.

    I am upgrading now, I will update this thread ASAP! ;)

    Thanks,
    Michele



  • Ok, after I set the serial speed to 111500 I was able to see the console.
    During the 2.3 boot it hangs at:
    Generating RRD graphs…

    Fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address	= 0x0
    fault code		= supervisor read, page not present
    instruction pointer	= 0x20:0xc12a67ea
    stack pointer	        = 0x28:0xd32de6d8
    frame pointer	        = 0x28:0xd32de6e0
    code segment		= base 0x0, limit 0xfffff, type 0x1b
    			= DPL 0, pres 1, def32 1, gran 1
    processor eflags	= interrupt enabled, resume, IOPL = 0
    current process		= 38891 (ping)
    [ thread pid 38891 tid 100068 ]
    Stopped at      bcopy+0x1a:     repe movsl      (%esi),%es:(%edi)
    

    then it goes in boot loop.

    The only way to recover was setting back the serial at 9600bps and booting with 2.2.6.

    I can give the full dump from the console if necessary.

    Thanks,
    Michele



  • It didn't work even after a full RRD clear through the web interface then rebooting, it continue stopping at "Generating RRD graphs".

    For now I can only boot on 2.2.6.

    Thanks,
    Michele



  • Upgrade is done and I'm trying to Duplicate boot slice  in Diagnostics / NanoBSD.
    Clicking on Duplicate and after some time getting an empty page and the following in the log:

    
    Apr 15 09:52:20 	gw.lan 		nginx: 2016/04/15 09:52:20 [error] 43594#0: *16 upstream timed out (60: Operation timed out) while reading upstream, client: 192.168.5.61, server: , request: "POST /diag_nanobsd.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "gw.lan", referrer: "http://gw.lan/diag_nanobsd.php" 
    

    I have already tried to do it twice. How I can make sure that duplication is [not] completed without reboot?



  • @AndrewZ:

    Upgrade is done and I'm trying to Duplicate boot slice  in Diagnostics / NanoBSD.
    Clicking on Duplicate and after some time getting an empty page and the following in the log:

    
    Apr 15 09:52:20 	gw.lan 		nginx: 2016/04/15 09:52:20 [error] 43594#0: *16 upstream timed out (60: Operation timed out) while reading upstream, client: 192.168.5.61, server: , request: "POST /diag_nanobsd.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "gw.lan", referrer: "http://gw.lan/diag_nanobsd.php" 
    

    I have already tried to do it twice. How I can make sure that duplication is [not] completed without reboot?

    Same problem here. Tried to duplicate the slice and the webinterface timed out. But i saw a running "dd" process even after i closed and
    reopened the webinterface so i think the duplication went ok. But i am not sure.



  • @jimp:

    For those who are seeing "Device busy" or similar and unable to force the disk read-write, try the following (preferably from the console):

    umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf

    Not something we'd normally recommend but somehow it seems that just the /cf slice is getting wedged for some people at the OS level.

    Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.

    That worked - thanks a lot!!

    And it seems to also have fixed the endless "Obtaining update status…". Looks like I'm all set.  8)


Log in to reply