forum.excito.org

Posted: **18 Apr 2012, 16:12**

Hi there

i wanted to upgrade my bubba|two version 2.05 to the 2.4.1 and followed the instructions given on http://forum.excito.net/viewtopic.php?f=1&t=3758 resp. http://wiki.excito.org/wiki/index.php/R ... ubba2_/_B3

steps done:
1. set the following bubba.cfg config:

Code: Select all

FORMAT = 0
PARTITION = 0

2. shut down bubba, unplugged the power.
3. plugged the usb stick in one of the usb slots. held the powr button while plugging in the power.
3. bubba led blinked a while with 2 Hz and then with 4 Hz.
4. after a few minutes it rebooted and since then keeps blinking with 1 Hz for hours/days.

cant' acess the bubba over telnet nor ssh. device doesn't get even an IP adress from my router.

i bought now an external hdd case and installed the 1TB disk into to try to boot over the external sata on my Windows computer. my bios has a boot menu and it recognized the hdd. but booting from it failed. it does actually nothing. no errors or messages shown.

windows disk managment recognizes 3 partitons. it was of corses not able to recognize more.
though i installed the program Ext2Fsd and it showed me the 3 partitions: swap (smallest size) ext3 (middle size), raw (biggest size). the only partition i was able to mount with the program was the ext3. the mount was automatically labeled "bubba root". i could access (read only) the files. well on that parttion my data was not present. giving it the middle sized partition and its naming it was clear. i think my data is on the RAW labeled partition.

Defintion of RAW on Wikipedia: In computing, specifically Unix-like operating systems, a raw device is a special kind of block device file that allows accessing a storage device such as a hard drive directly, bypassing the operating system's caches and buffers (although the hardware caches might still be used).

though i'm hoping my data is still save. because the forums about windows users dealing with raw partitions indicates that the file system has gone corrupt for example.

actually i have no clue what is going on.

any idea what i may try further?
is bubba configured to have a RAW partition?
did i damage the file system table or mbr?
for worst case szenario: can i rescue data from a raw parttion?

Posted: **19 Apr 2012, 06:04**

Hi

Did I understand you correctly that you tried to boot you normal pc from your bubba disk? That want fly at all since the hardware is totally different. They use different processor architecture for example.

Windows are very bad at reading partition created by other things than windows so the raw you see only means that Windows does not recognise the partition. Booting a live Linux cd like ubunut would most likely work much better. The partition that you data is on which is called the /home partition is not a normal ext3 partition but uses some thing called lvm and I guess that is what make Windows confused.

Most likely are your data intact. The question is why it does not boot. Maybe some files where corrupt on the USB stick.

Posted: **19 Apr 2012, 06:31**

thx for reply

gives me some hope

well, i'll then dowanload a knoppix or ubuntu live cd iso and boot my pc with and hope i can then access the raw partition over it. news will follow!

Posted: **25 Apr 2012, 12:44**

well, booted up with Knoppix LiveCD. It recognzied all my win7 drives and the bubba_root. but not the raw or swap one. well i googled bit about mounting a raw partition under linux and found i'd have to access the raw system the way it was created with. dunno how excito has created the raw parttion resp. is using the lvm thing.

Posted: **26 Apr 2012, 17:15**

HAd similar problems. I got my data out of the hdd with this windows program. http://www.chrysocome.net/explore2fs
Sorry if i tell something that has already been told, have not read through the whole thread.

Posted: **26 Apr 2012, 18:20**

thx for reply. but it only shows the ext3 partition bubba_root.

i really need to know how the lvm works on bubba.
even that i got my data on the hdd where bubba|two is installed too. i configured LVM with a Bubbba|Storage hdd. though i think the data handling is different than without lvm (?)

Update 1:
Ok, i found following manual how to mount lvm partitions:
http://linuxers.org/howto/how-mount-lin ... ions-linux

now steps i did over knoppix live cd:

Code: Select all

knoppix@Microknoppix:~$ su
root@Microknoppix:/home/knoppix# mount /dev/sdd2 /mnt
mount: unknown filesystem type 'LVM2_member'
root@Microknoppix:/home/knoppix# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfa5af693

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       60802   488385528+  42  SFS

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28bb3755

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      121602   976767041    7  HPFS/NTFS

Disk /dev/sdd: 1000.2 GB, 1000203804160 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8c30341f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1        1217     9775521   83  Linux
/dev/sdd2            1218      121457   965827800   8e  Linux LVM
/dev/sdd3          121458      121601     1156680   82  Linux swap / Solaris

Disk /dev/sdb: 82.0 GB, 81961123328 bytes
224 heads, 19 sectors/track, 37612 cylinders
Units = cylinders of 4256 * 512 = 2179072 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x07640764

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          49      102400    7  HPFS/NTFS
root@Microknoppix:/home/knoppix# mount /dev/sdd2 /mnt
mount: unknown filesystem type 'LVM2_member'
root@Microknoppix:/home/knoppix# apt-get install lvm2
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut       
Statusinformationen werden eingelesen... Fertig
lvm2 ist schon die neueste Version.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@Microknoppix:/home/knoppix# pvs
  PV         VG    Fmt  Attr PSize   PFree
  /dev/sdd2  bubba lvm2 a-   921,08g    0 
root@Microknoppix:/home/knoppix# lvdisplay /dev/bubba
  --- Logical volume ---
  LV Name                /dev/bubba/storage
  VG Name                bubba
  LV UUID                TlYu8Y-JahI-lnNT-Y8Tk-w8TE-CEn7-WD8Ytc
  LV Write Access        read/write
  LV Status              NOT available
  LV Size                921,08 GiB
  Current LE             235797
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
   
root@Microknoppix:/home/knoppix# mount /dev/bubba/storage /mnt
mount: special device /dev/bubba/storage does not exist
root@Microknoppix:/home/knoppix# cd ..
root@Microknoppix:/home# cd ..
root@Microknoppix:/# cd ..
root@Microknoppix:/# mount /dev/bubba/storage /mnt
mount: special device /dev/bubba/storage does not exist
root@Microknoppix:/#

well it finds the parttion but i cant mount it

Update 2:
went it through again and saw LV Status Not Available. Though found now the command to activate the lvm partitions:

Code: Select all

root@Microknoppix:/# vgchange -a y
  1 logical volume(s) in volume group "bubba" now active
root@Microknoppix:/# mount /dev/bubba/storage /mnt
mount: you must specify the filesystem type
root@Microknoppix:/#

specifing a file system?! dont find how to do it with mount -? and what should it be? ext3?

Posted: **27 Apr 2012, 15:55**

Read up on how lvm works. You cannot mount a lvm volume, only a partition on the lvm volume! Often kpartx will create mountpoints for these partitions for you. read up a bit about that too. Sorry that i cannot be more soecific but i have a real bad keyoard here....

Posted: **29 Apr 2012, 12:11**

i used the usb stick on a new harddisk. it installed bubba properly. though:
- usb stick works fine
- bubba|two platine isn't damaged.

it has to be something with the harddisk. but i can't figure out if the following are damaged:
- mbr
- grub loader
- file system table

Posted: **30 Apr 2012, 03:04**

mount -? should show you how to specify file system type but it is very brief so it might be hard to understand. man mount will give you more information. Any way you specif the file type with the flag -t <type> and it this case the type should be ext3 so
[coderoot@Microknoppix:/# mount -t ext3 /dev/bubba/storage /mnt][/code]
should do the trick.

Posted: **30 Apr 2012, 03:21**

ryz wrote:mount -? should show you how to specify file system type but it is very brief so it might be hard to understand. man mount will give you more information. Any way you specif the file type with the flag -t <type> and it this case the type should be ext3 so
Code: Select all
root@Microknoppix:/# mount -t ext3 /dev/bubba/storage /mnt
should do the trick.

well. not really. didn't copy the output but i did following:

Code: Select all

mkdir /mnt/mydata
mount -t ext3 /dev/bubba/storage /mnt/mydata

the output was something like that the filesystem type was invalid or wrong.

i had this once. for some unknown reasons leaving my bubba shut down - without powr cable plugged in - for two weeks (was on holidays in sweden ^^) and booting it after return, the system came up after 1h30Min. But that doesn't work anymore.

well, being fact, that my bubba is blinking infinte at 1hz it never reaches to establish any network connection with my LAN connected over RJ45 port. my router doesn't list the device.

FYI: The Configuration on my Router for the Bubba is properly. As i mentioned: My Bubba with a completely new HDD installed works properly. And it gets the same IP Adreess as before.

though it must be something initial - before any service (network, lvm or something) is started - in my opinion. something with MBR or SWAP Parttion for example.

yes - i still hope the actual situation is due to corrupt swap and mbr.
but that would not anwser why i can't mount the lvm partition with filesystem type ext3.

an upgrade over usb stick with following bubba.cfg file configuration should rewrite mbr, swap and boot partition, leaving the lvm one intact

Code: Select all

FORMAT = 0
PARTITION = 0

If i format the SWAP Partition manually over Knoppix LiveCD - would that work with the bubba usb installation routine?
About the MBR: would the debian wiki recover procedure work with bubba installation as well?

what if the file system table of the lvm partition is damaged?
does bubba / debian edge have some automated repair functions on startup?
anyone already made experience with Super Grub Disc / Rescatux? - it states having a filesysem and grub fix function.

need some conformation before i maybe destroy more than fix something

Posted: **30 Apr 2012, 17:03**

MaverikCH wrote: well. not really. didn't copy the output but i did following:
Code: Select all
mkdir /mnt/mydata
mount -t ext3 /dev/bubba/storage /mnt/mydata
the output was something like that the filesystem type was invalid or wrong.

found something more: Parted Magic
booted now with the Live CD.
and here the exact output on mounting with the Type Syntax:

Code: Select all

root@PartedMagic:~# mount -t ext3 /dev/bubba/storage /mnt/mydata
mount: wrong fs type, bad option, bad superblock on /dev/mapper/bubba-storage,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

well here we go:

Code: Select all

root@PartedMagic:~# dmesg | tail
[  558.172485] kjournald starting.  Commit interval 5 seconds
[  558.172713] EXT3-fs (sdd1): using internal journal
[  558.172720] EXT3-fs (sdd1): mounted filesystem with ordered data mode
[ 1122.945537] EXT3-fs (dm-0): error: can't find ext3 filesystem on dev dm-0.

now what i see over GParted app:

: Partitions on my BubbaTwo; bubba2hdd_partsituation.png (166.07 KiB) Viewed 22823 times

Warning: Swaplabel: /dev/sdd3: not valid swap parititon

i got the option to format it as a linux-swap. done. no it looks proper:

: Proper Swap Partition showed on my BubbaTwo harddrive; bubba2hdd_properswap.png (57.04 KiB) Viewed 22821 times

oh and ...
bad news: i damaged the screws and bubba two case though back panel cant be fixed anymore.
good news: hdd and platine survived. and i got now the chancce to buy a b3

- hopefully excito has a without hdd option.

Update 1:
booted with usb stick bubba installation with bubba.cfg file still configured with

Code: Select all

Format=0
Partition=0

after that the swap partition had again the Exclamation mark. the set up hard drive which works, has it too. though it must be as such.
while booting up without case and blue led blinking at 1hz, i discovered a red led which shows disk activity.
after 1 Min - 2 Min the red led reacts no longer while blue led still blinks with 1hz. sometimes it flashes up for some seconds afterwards. within 5 min period.

the well functioning hard drive had more activity with the red led - actually always till the blue led light steady.

Update 2:
had a look on the rescatux live cd.
super grub: it doesn't recognizes any grub installation on the bubba hard drive. i thought bubba boots with GRUB?
rescatux: the restore GRUB utiltiy doesn't work onthe bubba hard drive. it fails restoring GRUB

Posted: **14 May 2012, 13:32**

Update 3:
well, i now compared the two harddisks once more

: HDD with new set up Bubba|Two. explore2fs recognizes the lvm partition.; ScreenShot001.jpg (62.68 KiB) Viewed 22706 times

: HDD Bubba|Two and my Data. explore2fs doesn't recognize the lvm partition.; ScreenShot002.jpg (55.21 KiB) Viewed 22706 times

went back to the error message received on mounting the lvm and googled once more.
found this command for setting up a file system for an LVM:

Code: Select all

mke2fs /dev/my_volume_group/my_logical_volume

but i'm not sure if this formats the partition?

also found on another forum that i should check the etc/fstab. here we go:

Code: Select all

/dev/sda1	/	ext3	noatime,defaults	0	1
/dev/mapper/bubba-storage	/home	ext3	defaults		0	2
/dev/sda3	none	swap	sw			0	0
usbfs		/proc/bus/usb	usbfs	defaults	0	0
/proc		/proc	proc	defaults		0       0

No difference in comparision with the working hdd.

on the same forum the guy solved his issue with same error and following command:

Code: Select all

fsck.ext3 /dev/VolGroup01/LogVol00

though in my case it should be as following?

Code: Select all

fsck.ext3 /dev/bubba/storage

i read

a fsck may take up to 16 hours for an 1TB harddisk
data may be recovered in lost + found folder

if i'm unlucky any recovered data will not be recognizable. ls would display such as following

:

Code: Select all

...lost+found # ls
#1064961 #3883098 #3883107 #3883114 #3883120 #3883125 #3883130 #3883135 #3883141
...

and if i got it right the parameter -n should only show what it would do and not effectively execute:

Code: Select all

fsck.ext3 -n /dev/bubba/storage

well i hope my issue has to do with the superblock gone corrupt or something.
if i'm lucky fsck will relocate a alternate backup superblock.

Posted: **20 May 2012, 16:29**

i managed to boot up the hdd by removintg following line in the fstab file:

Code: Select all

/dev/mapper/bubba-storage   /home   ext3   defaults      0   2

now i'm able to check things on the hdd directly using ssh (putty)

Code: Select all

root@joseserver:/# sfdisk -l

Disk /dev/sda: 121601 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sda1          0+   1216    1217-   9775521   83  Linux
/dev/sda2       1217  121456  120240  965827800   8e  Linux LVM
/dev/sda3     121457  121600     144    1156680   82  Linux swap / Solaris
/dev/sda4          0       -       0          0    0  Empty

Disk /dev/dm-0: 120239 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/dm-0: unrecognized partition table type
No partitions found

well, i don't know what the dm-0 disk is. the problematic lvm partition is on sda > sda2

Code: Select all


root@joseserver:/# pvs
  PV         VG    Fmt  Attr PSize   PFree
  /dev/sda2  bubba lvm2 --   921.08g    0

root@joseserver:/# lvs
  LV      VG    Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  storage bubba -wi-a- 921.08g

root@joseserver:/# lvdisplay
  --- Logical volume ---
  LV Name                /dev/bubba/storage
  VG Name                bubba
  LV UUID                TlYu8Y-JahI-lnNT-Y8Tk-w8TE-CEn7-WD8Ytc
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                921.08 GiB
  Current LE             235797
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

root@joseserver:/# mount -t ext3 /dev/bubba/storage /mnt/mydata
mount: wrong fs type, bad option, bad superblock on /dev/mapper/bubba-storage,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

done now the fsck.ext3 check
[code]
root@joseserver:/# fsck.ext3 -n /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
fsck.ext3: Superblock invalid, trying backup blocks...
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no

Bubba_home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan.  Ignore error? no

Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted

root@joseserver:/# dmesg | tail
EXT3-fs (sda1): using internal journal
nf_conntrack version 0.5.0 (3996 buckets, 15984 max)
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
PHY: mdio@e0024520:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
sshd (1836): /proc/1836/oom_adj is deprecated, please use /proc/1836/oom_score_adj instead.
eth1: no IPv6 routers present
EXT3-fs (dm-0): error: can't find ext3 filesystem on dev dm-0.
[/code]

when i fsck.ext3 the /dev/sda2 or /dev/bubba/storage while running a live cd i got folloiwng:

Code: Select all

Bad magic number in super-block while trying to open <device>
 <device>:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem ( and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
   e2fsck -b 8193 <device>

i newly found a command to show up alternate superblocks. it showed me a list of blocks while using the live cd but now i get following:

Code: Select all

root@joseserver:/# mke2fs -n -S /dev/sda2
mke2fs 1.41.12 (17-May-2010)
/dev/sda2 is apparently in use by the system; will not make a filesystem here!

the alternate superblock command on /dev/bubba/storage worked:

Code: Select all

root@joseserver:/# mke2fs -n -S /dev/bubba/storage
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
60366848 inodes, 241456128 blocks
12072806 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7369 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848

seems that fsck.ext3 and e2fsck lead to the same check:

Code: Select all

root@joseserver:/# fsck.ext3 -b 819200 /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Bubba_home contains a file system with errors, check forced.

Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes

Force rewrite<y>? no

Error reading block 241467395 (Invalid argument) while getting next inode from scan.  Ignore error<y>? no

Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted
root@joseserver:/# e2fsck -b 819200 /dev/bubba/storage
e2fsck 1.41.12 (17-May-2010)
The filesystem size (according to the superblock) is 485646336 blocks
The physical size of the device is 241456128 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no

Bubba_home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 241467394 (Invalid argument) while getting next inode from scan.  Ignore error<y>? no

Error while scanning inodes (120733696): Can't read next inode
e2fsck: aborted

i'm not sure to accept the rewrite question.

Posted: **21 May 2012, 12:43**

well, accepting the wrewrite serves nothing :/

Code: Select all

...
Error reading block 241598640 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Force rewrite<y>? yes
Error writing block 241598640 (Invalid argument) while getting next inode from scan. Ignore error<y>?
...

maybe the fsck.ext3 doenst work on Logical Volume: /dev/bubba/storage and should be used on the Physical Volume: /dev/sda2?

sda2 is in use of the system when i want to fsck.ext3 on it even it isn't listed as mounted:

Code: Select all

root@joseserver:/# fsck.ext3 /dev/sda2
e2fsck 1.41.12 (17-May-2010)
fsck.ext3: Device or resource busy while trying to open /dev/sda2
Filesystem mounted or opened exclusively by another program?

root@joseserver:/# mount -l
/dev/sda1 on / type ext3 (rw,noatime) [Bubba root]
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)

Posted: **22 May 2012, 16:43**

Good news! Managed to access the lvm partition

after this:

MaverikCH wrote:i managed to boot up the hdd by removintg following line in the fstab file:
Code: Select all
/dev/mapper/bubba-storage   /home   ext3   defaults      0   2

just done actually the following:

Code: Select all

mount -t ext3 /dev/mapper/bubba-storage   /home

and my data are back ^^ =)

: My Data; ScreenShot003.jpg (33.44 KiB) Viewed 22582 times

But, that doesn't anwser why my bubba installation doesn't boot up while the fstab has the upon quoted line set...

forum.excito.org

[Solved] bubba|two not booting up after v2.4.1 upgrade

[Solved] bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade

Re: bubba|two not booting up after v2.4.1 upgrade