pfSense Gold Subscription

Author Topic: Read-only file system on Alix 32-bit nanoBSD  (Read 4964 times)

0 Members and 1 Guest are viewing this topic.

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Read-only file system on Alix 32-bit nanoBSD
« on: June 06, 2015, 09:36:56 pm »
I upgraded using http://snapshots.pfsense.org/FreeBSD_releng/10.1/i386/pfSense_RELENG_2_2/updates/pfSense-2.2.3-DEVELOPMENT-2g-i386-nanobsd-upgrade-20150604-1932.img.gz
The system has things mounted read-only too early, sample console output:
Code: [Select]
Root mount waiting for: usbus1 usbus0
uhub1: 4 ports with 4 removable, self powered
Root mount waiting for: usbus1
uhub0: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0 [ro,sync,noatime]...
Configuring crash dumps...
/dev/ufs/pfsense0: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufs/pfsense0: clean, 1473891 free (1539 frags, 184044 blocks, 0.1% fragmentation)
/dev/ufs/cf: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufs/cf: clean, 94237 free (45 frags, 11774 blocks, 0.0% fragmentation)
Filesystems are clean, continuing...
Mounting filesystems...
rm: /conf: Read-only file system
ln: /conf/conf: Read-only file system
Setting up memory disks... done.
Disabling APM on /dev/ad0
(pass0:ata0:0:0:0): SETFEATURES. ACB: ef 85 00 00 00 40 00 00 00 00 00 00
(pass0:ata0:0:0:0): CAM status: ATA Status Error
(pass0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT )
(pass0:ata0:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00
Failed to configure APM: No such file or directory
pwd_mkdb: /etc//pwd.db.tmp: Read-only file system

     ___
 ___/ f \
/ p \___/ Sense
\___/   \
    \___/

Welcome to pfSense 2.2.3-DEVELOPMENT  ...

mkdir: /root/var: Read-only file system
mkdir: /root/var: Read-only file system
mkdir: /var/db/pbi: No such file or directory
cp: /var/db/pbi/keys: No such file or directory
Creating symlinks...rm: /conf: is a directory
ln: /conf/conf: Read-only file system
rm: /etc/newsyslog.conf: Read-only file system
rm: /etc/syslog.conf: Read-only file system
ln: /etc/syslog.conf: File exists
rm: /etc/hosts: Read-only file system
ln: /etc/hosts: File exists
ln: /etc/resolv.conf: Read-only file system
ln: /etc/resolvconf.conf: Read-only file system
rm: /etc/dhclient.conf: Read-only file system
.warning: failed to load external entity "/conf/config.xml"
..ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
done.
cap_mkdb: /etc/login.conf.db: Read-only file system
>>> Under 512 megabytes of ram detected.  Not enabling APC.
The console (and everything) stops at this point.
After pressing "enter" a couple of time at the console:
Code: [Select]
Jun  7 08:16:15 php-fpm[300]: /ecl.php: No config.xml found, attempting last known config restore.
Jun  7 08:16:15 php-fpm[300]: /ecl.php: New alert found: No config.xml found, attempting last known config restore.
Jun  7 08:16:15 php-fpm[300]: /ecl.php: No config.xml found, attempting last known config restore.
Jun  7 08:16:15 php-fpm[300]: /ecl.php: New alert found: No config.xml found, attempting last known config restore.
Jun  7 08:16:17 php-fpm[300]: /ecl.php: pfSense is restoring the configuration /cf/conf/backup/config-1431583643.xml
Jun  7 08:16:17 php-fpm[300]: /ecl.php: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1431583643.xml

Warning: fopen(/conf/config.xml): failed to open stream: No such file or directory in /etc/inc/xmlparse.inc on line 183
Jun  7 08:16:17 php-fpm[300]: /ecl.php: Error: could not open XML input
Jun  7 08:16:18 php-fpm[300]: /ecl.php: pfSense is restoring the configuration /cf/conf/backup/config-1431583643.xml
Jun  7 08:16:18 php-fpm[300]: /ecl.php: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1431583643.xml
External config loader 1.0 is now starting...
Launching the init system...rm: /cf/conf/backup/backup.cache: Read-only file system
 done.
Initializing...................... done.
Starting device manager (devd)...done.
Loading configuration....XML configuration file not found.  pfSense cannoWaiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 done
All buffers synced.
Uptime: 16m12s

The operating system has halted.
Please press any key to reboot.
I guess this is some side-issue related to changing the file system to "sync"?
I am glad this is nanoBSD - very easy to go back to the previous 2.2.2-RELEASE slice :)
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11914
  • Karma: +468/-15
    • View Profile
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #1 on: June 07, 2015, 03:25:00 pm »
Confirmed the same behaviour with: pfSense-2.2.3-DEVELOPMENT-4g-amd64-nanobsd-upgrade-20150607-0659.img.gz
Coming from an earlier 2.2.3 snapshot, May 18th.

Steve

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #2 on: June 08, 2015, 01:36:53 am »
+1, nanobsd unusable.
Do NOT PM for help!

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #3 on: June 08, 2015, 01:39:21 am »
pfSense-2.2.3-DEVELOPMENT-4g-amd64-nanobsd-upgrade-20150607-1531.img.gz

Same issue on an APU with the above nanoBSD upgrade image. Coming from 2.2.2-RELEASE.
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #4 on: June 08, 2015, 02:03:17 am »
Yeah whole nanobsd is broken, x86 or amd64 doesn't matter. Noted on the bug: https://redmine.pfsense.org/issues/4523#change-18702
Do NOT PM for help!

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #5 on: June 08, 2015, 07:39:18 pm »
To anyone reading this who has some control - when the problem of read-only file system is fixed, then the 32-bit builder also needs to run again. It has stopped producing images the last few days.
But there is no point restarting the builder until the RO problem is fixed :)
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline ermal

  • Hero Member
  • *****
  • Posts: 3832
  • Karma: +85/-5
    • View Profile
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #6 on: June 08, 2015, 07:58:36 pm »
The filesystem problem should be fixed.

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #7 on: June 08, 2015, 11:16:55 pm »
Currently the latest build pfSense-2.2.3-DEVELOPMENT-4g-amd64-nanobsd-upgrade-20150608-1911.img.gz still has this problem. I guess the builder will wake up again soon and make new images...
pfSense-2.2.3-DEVELOPMENT-4g-amd64-nanobsd-upgrade-20150609-0342.img.gz
works fine on APU. At the end of the boot it finished up read-only as required.
For the record, the mounted stuff is:

Code: [Select]
[2.2.3-DEVELOPMENT][root@Kalikot-rt-01.np.net.inf.org]/root: mount
/dev/ufs/pfsense1 on / (ufs, local, noatime, read-only, 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)

Now we just need a 32-bit build to happen - I can still only see 32-bit snapshots up to 5 June.
« Last Edit: June 09, 2015, 05:53:02 am by phil.davis »
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline ermal

  • Hero Member
  • *****
  • Posts: 3832
  • Karma: +85/-5
    • View Profile
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #8 on: June 10, 2015, 02:12:20 pm »
32 bit builds are fixed as well now.

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: Read-only file system on Alix 32-bit nanoBSD
« Reply #9 on: June 10, 2015, 07:31:22 pm »
32 bit builds are fixed as well now.
Confirmed good - I am now running on 32-bit Alix:
2.2.3-DEVELOPMENT (i386)
built on Wed Jun 10 10:48:12 CDT 2015
FreeBSD 10.1-RELEASE-p11
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/