It worked!
Thank you for helping me all the way.
Now that I can ssh into the b3, I can finally get on with the setup

Again thanks a lot
All the best
lognok
Code: Select all
echo "1" > /proc/sys/net/ipv4/ip_forward
It is a fresh install however if you already removed all the excito packages from your B3 I would recommend doing a manual upgrade of your B3 ( apt-get dist-upgrade ) that way you'll keep your data and configuration. I can help you with that and provide the steps.pompopom wrote:Maybe stupid question: but is it a "fresh install" that happens or 'just' an upgrade (preserving current present applications as mysql/owncloud/...)?
That is a very good idea and it should work.pompopom wrote:I'm planning on leaving my e-sata deconnected whilst performing the upgrade/manipulations, so I can easily revert back with just swapping the disks and having the raid rebuild. To simple or not?
If you wish to format and use the new image, the best path would be to boot the rescue system (remove the image param in install.ini) ; format and mount your raid device, untar the image on it, mount and edit the /etc/fstab to reflect the new root location, unmount and restart the b3. It should work and at least you should keep your RAID configuration. Never tested though, I don't have RAID anymore at home.pompopom wrote:As I suppose the Jessie images you provide are made for running on a 'clean' B3, without beforehand fiddling, I was wondering if I could use those just as any other user would do, or should I consider any special precautions (u-boot stuff etc)?
In that case no it is a custom-made RAID which allows the root partition to be included in a RAID array (see my post on the wiki ; applies to the B2 but easily ported for the B3)Gordon wrote:Please note that the RAID only applies to bubba-storage, i.e. everything under /home. It does not mirror your root partition, which includes /var where your MySQL databases are stored by default.
That's a very good idea too.Gordon wrote:Also, most SQL variants are absolute bitches when it comes to upgrading. You may find that the current release of MySQL (or MariaDB) will not accept your original data files. You should create a dump file before doing the upgrade and store it somewhere safe.
This would work too but since everything is on RAID arrays disconnecting a drive and keeping it for rescue purpose until finished would work too and takes less time.Gordon wrote:If you like to be able to revert completely, your best option is to boot a rescue USB (or LIVE edition) and rsync the content of / to some target on another partition or drive (use -a -x parameters, 'archive' and 'do not cross file system boundary').
I actually didn't remove any excito package. But I need to be honest I haven't used any of them since I installed Owncloud years ago. So I could indeed. hmmm, I saw in the tutorial on how to revert back to minimal linux that you also removed MySQL. Is that a tweaked excito version too?MouettE wrote: It is a fresh install however if you already removed all the excito packages from your B3 I would recommend doing a manual upgrade of your B3 ( apt-get dist-upgrade ) that way you'll keep your data and configuration. I can help you with that and provide the steps.
Check.MouettE wrote:That is a very good idea and it should work.pompopom wrote:I'm planning on leaving my e-sata deconnected whilst performing the upgrade/manipulations, so I can easily revert back with just swapping the disks and having the raid rebuild. To simple or not?
This is kinda why I always was in doubt to do a complete distro upgrade as I clearly recalled your warning from the full Raid wiki:MouettE wrote:If you wish to format and use the new image, the best path would be to boot the rescue system (remove the image param in install.ini) ; format and mount your raid device, untar the image on it, mount and edit the /etc/fstab to reflect the new root location, unmount and restart the b3. It should work and at least you should keep your RAID configuration. Never tested though, I don't have RAID anymore at home.pompopom wrote:As I suppose the Jessie images you provide are made for running on a 'clean' B3, without beforehand fiddling, I was wondering if I could use those just as any other user would do, or should I consider any special precautions (u-boot stuff etc)?
Let me know what you decide !
Charles
Can I conclude the workaroud exists? Or are the u-boot utils present in the rescue system nowadays?In addition, these modifications prevent you from using the usb rescue disk, because your system won't boot after a rescued installed software. The u-boot utils are not available in the rescue system, so you can't restore the modifications you've made to boot the raid array. I am currently working on a workaround, but as of today it doesn't work.
True, in an of-the-shelf B3 it is only the /home who is mirrored. But that's the whole point of my doubt in doing a "regular" upgrade to wheezy or later jessie as done/explained most of the time here on the forum => I've put my B3 in full raid, so I dunno how it would behaveGordon wrote:Please note that the RAID only applies to bubba-storage, i.e. everything under /home. It does not mirror your root partition, which includes /var where your MySQL databases are stored by default.
Also, most SQL variants are absolute bitches when it comes to upgrading. You may find that the current release of MySQL (or MariaDB) will not accept your original data files. You should create a dump file before doing the upgrade and store it somewhere safe.
If you like to be able to revert completely, your best option is to boot a rescue USB (or LIVE edition) and rsync the content of / to some target on another partition or drive (use -a -x parameters, 'archive' and 'do not cross file system boundary').
Correct.pompopom wrote:Your 3rd paragraph is in case I wouldn't have full raid? Or am I missing something?
Careful! In the original Excito system many of the core utilities you need for running and be able to access the box (such as sshd, but also the kernel) are only there because they are pulled in as dependencies of bubba-backend.pompopom wrote:I actually didn't remove any excito package. But I need to be honest I haven't used any of them since I installed Owncloud years ago. So I could indeed. hmmm, I saw in the tutorial on how to revert back to minimal linux that you also removed MySQL. Is that a tweaked excito version too?MouettE wrote: It is a fresh install however if you already removed all the excito packages from your B3 I would recommend doing a manual upgrade of your B3 ( apt-get dist-upgrade ) that way you'll keep your data and configuration. I can help you with that and provide the steps.
Not in the rescue system. It is on many Live USB editions though.pompopom wrote:Can I conclude the workaroud exists? Or are the u-boot utils present in the rescue system nowadays?
mysql is removed because it is not part of a minimal install. However you do not want a minimal install you only want to remove the excito packages which cannot be upgraded. It's up to you to know from the list of installed packages what is and what is not used.pompopom wrote:I actually didn't remove any excito package. But I need to be honest I haven't used any of them since I installed Owncloud years ago. So I could indeed. hmmm, I saw in the tutorial on how to revert back to minimal linux that you also removed MySQL. Is that a tweaked excito version too?
pompopom wrote:Can I conclude the workaroud exists? Or are the u-boot utils present in the rescue system nowadays?
The new rescue system includes u-boot-utils with the proper configuration.Gordon wrote:Not in the rescue system. It is on many Live USB editions though.