Project

General

Profile

Actions

Bug #2200

closed

Upgrade from 2.0-RC3 to 2.0.1 fails with "Something went wrong when trying to update the fstab entry"

Added by Henrik A about 12 years ago. Updated about 12 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
02/13/2012
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:
i386

Description

I tried upgrading from 2.0-RC3 to 2.0.1 on my nanobsd box, but it failed with "Something went wrong when trying to update the fstab entry. Aborting upgrade.".

Here's the log:

NanoBSD Firmware upgrade in progress...

Installing /root/latest.tgz.
SLICE         1
OLDSLICE      2
TOFLASH       ad2as1
COMPLETE_PATH ad2as1a
GLABEL_SLICE  pfsense0
Mon Feb 13 07:21:48 UTC 2012

total 6
dr-xr-xr-x   6 root  wheel         512B Feb 10 12:26 .
drwxr-xr-x  24 root  wheel         512B Feb 10 12:30 ..
crw-r-----   1 root  operator    0,  45 Feb 10 12:26 ad2
crw-r-----   1 root  operator    0,  46 Feb 10 12:26 ad2a
crw-------   1 root  operator    0,  28 Feb 10 12:26 ata
crw-------   1 root  wheel       0,  11 Feb 13 07:18 bpf
lrwxr-xr-x   1 root  wheel           3B Feb 10 12:26 bpf0 -> bpf
crw-------   1 root  tty         0,   5 Feb 13 07:21 console
crw-rw-rw-   1 root  wheel       0,  36 Feb 10 12:26 crypto
crw-rw-rw-   1 root  wheel       0,  10 Feb 10 12:26 ctty
crw-rw----   1 uucp  dialer      0,  32 Feb 10 12:26 cuau0
crw-rw----   1 uucp  dialer      0,  33 Feb 10 12:26 cuau0.init
crw-rw----   1 uucp  dialer      0,  34 Feb 10 12:26 cuau0.lock
crw-------   1 root  wheel       0,   4 Feb 10 12:26 devctl
cr--------   1 root  wheel       0,  43 Feb 10 12:26 devstat
dr-xr-xr-x   2 root  wheel         512B Feb 10 12:26 fd
crw-------   1 root  wheel       0,  13 Feb 10 12:26 fido
crw-r-----   1 root  operator    0,   3 Feb 10 12:26 geom.ctl
crw-------   1 root  wheel       0,  25 Feb 10 12:26 io
crw-------   1 root  wheel       0,   8 Feb 10 12:26 klog
crw-r-----   1 root  kmem        0,  15 Feb 10 12:26 kmem
crw-r-----   1 root  operator    0,  53 Feb 10 12:26 md0
crw-r-----   1 root  operator    0,  54 Feb 10 12:26 md1
crw-------   1 root  wheel       0,  40 Feb 10 12:26 mdctl
crw-r-----   1 root  kmem        0,  14 Feb 10 12:26 mem
crw-------   1 root  kmem        0,  16 Feb 10 12:26 nfslock
crw-rw-rw-   1 root  wheel       0,  23 Feb 13 07:21 null
crw-r--r--   1 root  wheel       0,  27 Feb 10 12:26 pci
crw-rw----   1 root  proxy       0,  37 Feb 10 12:26 pf
crw-------   1 root  wheel       0,  35 Feb 10 12:26 ppi0
crw-rw-rw-   1 root  wheel       0,   9 Feb 10 12:26 ptmx
crw-rw-rw-   1 root  wheel       0,   6 Feb 10 12:26 random
crw-------   1 root  wheel       0,  26 Feb 10 12:26 speaker
lrwxr-xr-x   1 root  wheel           4B Feb 10 12:26 stderr -> fd/2
lrwxr-xr-x   1 root  wheel           4B Feb 10 12:26 stdin -> fd/0
lrwxr-xr-x   1 root  wheel           4B Feb 10 12:26 stdout -> fd/1
crw-------   1 root  wheel       0,  29 Feb 10 12:26 ttyu0
crw-------   1 root  wheel       0,  30 Feb 10 12:26 ttyu0.init
crw-------   1 root  wheel       0,  31 Feb 10 12:26 ttyu0.lock
dr-xr-xr-x   2 root  wheel         512B Feb 10 12:26 ufs
dr-xr-xr-x   2 root  wheel         512B Feb 10 12:26 ufsid
lrwxr-xr-x   1 root  wheel           9B Feb 10 12:26 ugen0.1 -> usb/0.1.0
lrwxr-xr-x   1 root  wheel           6B Feb 10 12:26 urandom -> random
dr-xr-xr-x   2 root  wheel         512B Feb 10 12:26 usb
crw-r--r--   1 root  operator    0,  38 Feb 10 12:26 usbctl
crw-------   1 root  operator    0,  39 Feb 10 12:26 xpt0
crw-rw-rw-   1 root  wheel       0,  24 Feb 10 12:26 zero

-rw-r--r--  1 root  wheel    64M Feb 13 07:21 /root/latest.tgz

MD5 (/root/latest.tgz) = eee752e522922aae157b333a478b0a1a

/dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)

last pid: 63227;  load averages:  0.48,  0.19,  0.11  up 2+18:55:29    07:21:51
40 processes:  1 running, 39 sleeping

Mem: 37M Active, 87M Inact, 28M Wired, 1216K Cache, 33M Buf, 77M Free
Swap: 

  PID USERNAME  THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
63266 root        1  76   20  3656K  1424K wait     3:02  0.00% sh
43424 nobody      1  44    0  5556K  2604K select   1:30  0.00% dnsmasq
42367 dhcpd       1  44    0  8436K  5452K select   0:34  0.00% dhcpd
24791 root        1  44    0  6588K  4880K kqread   0:15  0.00% lighttpd
26900 root        1  76    0 33408K 17276K accept   0:09  0.00% php
11566 root        1  44    0  5912K  2712K bpf      0:08  0.00% tcpdump
 2534 root        1  44    0  3352K  1312K select   0:05  0.00% miniupnpd
11027 root        1  44    0  3448K  1456K select   0:04  0.00% syslogd
29067 _ntp        1  44    0  3316K  1344K select   0:03  0.00% ntpd
11857 root        1  44    0  3316K   928K piperd   0:01  0.00% logger
26802 root        1  76    0 34432K 20148K accept   0:01  0.00% php
50093 root        1  64   20  5988K  3896K select   0:01  0.00% racoon
 3002 root        1  44    0  3404K  1404K nanslp   0:01  0.00% cron
14700 _bgpd       1  44    0  3316K  1796K select   0:01  0.00% bgpd
29118 root        1  72    0  3316K  1040K nanslp   0:01  0.00% minicron
26200 root        1  76    0 34432K 16528K accept   0:01  0.00% php
43100 root        1  44    0  3316K  1644K kqread   0:01  0.00% dhcpleases
41517 root        1  64   20  3316K  1348K select   0:00  0.00% apinger

NanoBSD upgrade starting

dd if=/dev/zero of=/dev/ad2as1 bs=1m count=1
dd: /dev/ad2as1: Operation not supported

/usr/bin/gzip -dc /root/latest.tgz | /bin/dd of=/dev/ad2as1 obs=64k
dd: /dev/ad2as1: Operation not supported
After upgrade fdisk/bsdlabel

/sbin/fsck_ufs -y /dev/ad2as1a
Can't stat /dev/ad2as1a: No such file or directory
Can't stat /dev/ad2as1a: No such file or directory

/sbin/tunefs -L pfsense0 /dev/ad2as1a
tunefs: /dev/ad2as1a: could not find special device

File list:

Warning: file_get_contents(/conf/file_upgrade_log.txt): failed to open stream: No such file or directory in /usr/local/www/diag_nanobsd.php on line 236

Misc log:

Warning: file_get_contents(/conf/firmware_update_misc.log): failed to open stream: No such file or directory in /usr/local/www/diag_nanobsd.php on line 238

fdisk/bsdlabel log:

Before upgrade fdisk/bsdlabel
******* Working on device /dev/ad2a *******
parameters extracted from in-core disklabel are:
cylinders=914 heads=16 sectors/track=63 (1008 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=914 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 921249 (449 Meg), flag 80 (active)
    beg: cyl 0/ head 1/ sector 1;
    end: cyl 913/ head 15/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
---------------------------------------------------------------

******* Working on device /dev/ad2a *******
parameters extracted from in-core disklabel are:
cylinders=914 heads=16 sectors/track=63 (1008 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=914 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 921249 (449 Meg), flag 80 (active)
    beg: cyl 0/ head 1/ sector 1;
    end: cyl 913/ head 15/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
---------------------------------------------------------------
Actions #1

Updated by Jim Pingle about 12 years ago

  • Status changed from New to Rejected

This is not a general problem/bug, but something specific to your setup or what you're doing. Please post in the forum for help diagnosing your issue.

Actions #2

Updated by Henrik A about 12 years ago

I disagree with the Rejected status.

I installed this system as described in the installation guide, using dd to write the image to a CF card. Somehow the upgrade procedure isn't able to detect that.

(Also see http://forum.pfsense.org/index.php/topic,46176.0.html for more info)

Actions #3

Updated by Stefan Hellmann about 12 years ago

I've exactly the same problem.

Actions #4

Updated by Jim Pingle about 12 years ago

Please post to the forum for support. This is a rejected ticket that was not a bug, but something that happened to the user's CF image.

Actions

Also available in: Atom PDF