Jump to content

Leon

Administrators
  • Content Count

    1438
  • Joined

  • Last visited

  • Days Won

    52

Leon last won the day on June 26

Leon had the most liked content!

Community Reputation

94 Excellent

4 Followers

About Leon

  • Rank
    General Manager

Contact Methods

  • Website URL
    http://www.bollerup.org
  • ICQ
    32124999
  • Skype
    lbollerup

Profile Information

  • Gender
    Male
  • Location
    Sweden

Recent Profile Visitors

20083 profile views
  1. Orginal and creds goes to: Jeff Avery's blog Notes: Hes orginal blog post is being mirroed here (partly) here with the intend of keeping it online - a full webcopy have been made to the URL below, also, since the orginal links for the software needed isent online anymore - corrected links and mirroed copys of the software will be stored here. Links: Orginal post: http://blog.jeffavery.com/2010/04/25/dell-latitude-on-dell-latitude-on-flash/ Webcopy: http://leon.bollerup.org/mirrors/blog.jeffavery.com/2010/04/25/dell-latitude-on-dell-latitude-on-flash/ Software on Dells site: https://www.dell.com/support/home/se/sv/sedhs1/product-support/product/latitude-e4200/drivers Software: - Dell Latitude ON Software Application - Dell Latitude/Precision ON Flash Utility - Dell Latitude/Precision ON Flash Firmware Update - Dell Latitude/Precision ON Flash Application - Dell Latitude ON EX Application - Dell Latitude ON Reader Application --- In November of 2009 I purchased a Dell Latitude e4200 and I decided to add the Latitude ON module to the purchase. It’s an ARM processor based add-on that allows you to boot a small Linux OS (MontaVista Linux) independent of the operating system. I set it up, tried a few things, and realized I would not be doing much with it until I could figure out a way to customize it somewhat. I recently ran across a Dell forum talking about a “Latitude ON FLASH”. After a little digging I found it was a separate module add-on with a few more features than the ARM based module I already had. The price of the ARM was nearly 4 times as much so I was intrigued about more features for less so I decided to pick one up. It was a bit frustrating to install because the instructions that came with it basically said “install the module”…nice. Mainly I was trying to figure out which of these would be a better option and what the pros / cons of each was. I found little to no information out there that really said anything so I thought I’d put this together. The Latitude ON Original was an ARM processor based module completely self contained from the rest of the laptop. It can extend your battery substantially if you were simply looking to check mail and browse the web. The Latitude ON FLASH relies on the laptops processor so your battery life is decreased somewhat over the original but, with the cost savings, you could purchase the extended battery. Here is a side by side shot of both cards. The Latitude ON Original is on the left: Here you see the back cover removed (one screw…very nice) and the Latitude ON Original removed leaving the empty space and two antenna wires. Also the WWAN (Cellular Broadband) slot where the Latitude ON FLASH will go. Click on the image for a larger photo and markings for each slot: One of the reasons for this post was that the instructions were lacking to say the least. It was not clear as to whether you could run both cards simultaneously or only one at a time. The answer is you can run only one of these modules at a time. It may seem intuitive after the fact however, given the lact of documentation, I was unsure if they played off each other. The price was also part of this confusion. Given that the Latitude ON Original was a $199.00 option and the Latitude ON Flash is around $60.00 it seemed that the FLASH module was possibly a compliment to the more expensive module. This is not the case. When I first installed the Latitude ON FLASH module I removed the Latitude ON Original from the laptop. I then installed the FLASH module (photos further down this post) and booted into Windows. When I installed the “Dell Latitude ON Flash – User Configuration Application for Windows” and the associated Firmware (all itemized below). Windows had me create a password for the Latitude ON FLASH user (It will let you create one of two users. Either a user with the same name as your Windows user account or a user named “user”). It finished up with a statement that I had completed the install process and I could press the latitude ON button and boot into Latitude ON. When I tried to boot to Latitude ON I received an error that the Latitude ON module was not installed and to see my Administrator. I played this game, in and out of Windows, for quite some time. I removed and re-added the software and modules in various combinations. Trying both, one and then the other module. I contacted Dell support and, while they were extremely helpful, they really could not do much for me. When I say they were helpful I mean that they did not have me try several pointless things to waste my time or theirs. The technician finally gave up after about 15 minutes of searching and said that he was stumped and that there was little information available on these modules yet. He said he would do some further research and contact me back the following day. I thanked him for not asking me to re-image my laptop and decided to keep plugging. The resolution ended up being disparate BIOS settings between the two cards. I believe what would have made this much easier is if I had gone into the BIOS first and disabled the Latitude ON Original BEFORE removing it and installing the FLASH module. The Latitude ON Original has two options in the BIOS. There is an “Enable Latitude ON” and “Use Instant on mode” (both check boxes). The Latitude ON FLASH only has one option and it is “Enable Latitude ON”. I’m not sure how, or when, I finally realized this but I believe that having the “Use instant on mode” checked with the newer Latitude ON FLASH installed was causing the issue. Given that the “Use instant on mode” was checked the system was looking for the Latitude ON Original card and since it was not installed the error that the Latitude ON module was not installed and to see my Administrator was thrown. Once I unchecked both options in the BIOS (seen in this photo) I saved and rebooted the laptop. I went right back into the BIOS and the only option available was “the Enable Latitude ON option”. I checked that, saved and powered off the device. I pressed the latitude on button and went right into the new Latitude ON FLASH module. //Leon
  2. Hi Leon,  i want know if u have the files of LACIE 2BIG NETWORK V2. 

  3. Here is a new one: https://discord.gg/vVCpPWu
  4. Hi, Running OSXL have always been a mission we have been proud of - from the early days of D4x0 we could never have imagined that OSXL would grow to what it is today - a safe and nice place where hackintosh and macOS nerds can meet, have fun and play around. But running OSXL also have costs.. hosting.. the forum software.. mail service.. dns .. it cost.. and it never gets cheaper - so faar donations usually covers less than 5% of our operating cost. So.. what todo ? OSXL have always been against showing commercial ads our site - mostly because it slows down the site and ruin the user experience - personally .. i hate a slow website. So, we always explore new options (specially if its fun.. like the seedbox partnership) Anyway, today Brave browser launched - brave browser is (besides being a really nice web browser) - is a browser that allows its users to earn $BAT (a crypto currency) and donate those earned Bat(s) to websites they visit. We have enabled donations to the site - both automatic - but also by using the browsers build-in functionality. Wanna test brave browser? .. head over to: https://brave.com/osx926 (Btw, brave gives us 5 USD for each download, so you having fun testing a new browser, is also helping us and by that yourself) ... and may this be a hint of more fun stuff with cryptocurrencies coming your way //OSXLteam
  5. Morning everyone, Things are moving forward as planed and some cool things will come over the corse of this week,. IPboard upgrade: First of all - we are testing the latest 4.4.2 of IPboard over att http://dev.osxlatitude.com - so faar it seems a few theme issues will have to be fixed - but besides that it looks good.. so expect and upgrade later this week New server: OSXL will be moving to a new hosts - so faar we have been on shared hosting - usually sponsored - but have now decided to move to our own box - this will improve performance but also allow us to integrate features and new services better - the server move is expected to happen with the next two seeks. Discord: Join us on discord - IPboard and the forum is awesome .. a great solution.. but why not take the chance to hang out with the rest of us.. Joins us at: https://discord.gg/Wz7EU3
  6. Hi, After a recent upgrade we found that users now was forced to login using their "Username" and no longer could use their "E-mail" to login, this have created a great deal of support tickets and general confusion. We are truly sorry about that - to the Team's defense this was a chagne in the IPboard software - a fix is now implemented. In other news we are currently working on a new / better hosting solution since the sponsored hosting we currently are using will be going away. To this end we have bought our own box and are taking the chance to experiment with other web server software and newer PHP version - ultimately we would have liked to go with Litespeedtech's litespeed web server and asked if they were interested in sponsoring us (being the non-profit site we are) - they could at best offer us 25% rebate - Sadly. We are currently using Apache - but as everyone knows - its not known for its extreme performance. If you have experince with webhosting or feel like helping out - please contact me at lsb@osxlatitude.com //Leon PS. We also identified an issue with sparpost (the mail service we use) - that is fixed now and you should start to recieve mails from the site.
  7. Hi there, I got a bit of important news to share with you. As you know - OSXL and its services is privately funded by the team and via donations we get (keep em coming, the few that donates rocks!) - we dont have any ads and we dont bundle any malware - we like to keep the site clean to give you the best experince we can. But - running this site have its costs - its a fact we can't get around - so it got us thinking - how can we get some funding for the site without selling out of the core values that drives the site. God knows we have had plenty of companies that want to advertize, sell their products or outright buy OSXL - so the discussions started - if we were to offer 3rd. party products on the site - it should not be without requirements. 1. It should benefit the users 2. It should be of interest to the users 3. It should benefit the site 4. No crap, scam or bad deals. With that in mind - i am happy to present our first partner - i welcome RapidSeedbox to OSXL. "With RapidSeedbox, you do not have to worry about any logs, contracts or ISP’s. You will enjoy full privacy with us. Our Seedbox product is built with your security & anonymity in mind." Basiclly - here is the deal - If you order a Seedbox via RapidSeexbox using the link below you get 25% of the first month and OSXL gets a 10% kickback - so you save money, get the best seedbox the market can offer and you help fund OSXL in the process - seems like a win-win for everyone? Head over to: https://members.rapidseedbox.com/aff.php?aff=1430 and use the code "RAPID25-OSXL" Have fun //Leon
  8. Leon

    Laptop index

    Hi, Unlike macOS its quite easy to get your machine up and running with chromeOS - There is several methods and some work better than others - the easyist is by far "Cloudready" by Neverware - just head over to https://www.neverware.com/freedownload - download the installer and get rocking. Here i will try and put together a little index of machines that i personally have tested. Model Wifi Screen Touchpad USB Ext. screen Notes Dell Latitude E5410 Yes Yes Yes Yes Yes Machine runs alot better than with Windows
  9. Hi there, As some of you may or may not know - OSXL is currently looking into integrating a cryptocurrency - the reason behind this is many - but mostly to have fun - and to allow developers and people who help - to be rewarded for the hard work they do. Unlike other sites that generate their own currency we will most likely go with a coin/token that already is out there - and we are studying a few like: XRP, Kin, Bos, Rise and ETN Today my attention fel to a new: Initiative Q. They are running a campaign - if you head over and signup you will get a bunch of coins for free - so head over and signup and let me know what you think: Link: https://initiativeq.com/invite/HV_cnzp77 Also, if you have any experince with crypto - like development - drop me a message about joining our crypto team.
  10. Good morning guys,
    I have the problem reported by Leon that helped me with tips from your post.I have a Lacie 2 big network 2 that broke the two hdds at the same time. I followed the Leon postings, formatted new disks, loaded the files to the appropriate partitions, etc. However, when I start the equipment, the indicator lights on the discs flash red and then turn off. The equipment does not start. I have the impression that it is the UUI issue for new disc recognition. Does anyone have any tips on how to fix the problem so that the disks are recognized? Thanks in advance.

  11. Hi, One of my favorite sync software is ResilioSync (former torrentsync) - its unique because its a real "mesh" sync - whereas others are essentially extremely centralized - in line with as much other - i dont like centralized systems. In this post we are going to discuss how you can install resiliosync in crostini - and more important - how you can manage it. Installation Resiliosync can either be installed via a DEB package (which for most users maybe is the most easy way to go around it) since is not in the default debian package tree - however - if you choose to go with a package tree installation you will also get updates.. so thats what we are going for here. Instructions for this is on: https://help.resilio.com/hc/en-us/articles/206178924-Installing-Sync-package-on-Linux - but for the sake of the arguement - i'll post them here also. Start by opening up a crostini console and change to root, type: sudo su Lets add the rep. to the package tree, type: echo "deb http://linux-packages.resilio.com/resilio-sync/deb resilio-sync non-free" | sudo tee /etc/apt/sources.list.d/resilio-sync.list Add public key with the following command: wget -qO - https://linux-packages.resilio.com/resilio-sync/key.asc | sudo apt-key add - Update packages index, type: sudo apt-get update; Install sync, type: sudo apt-get install -y resilio-sync ResilioSync is now installed.. but we need to configure it and figure out howto access it. First its important to find the IP address of your crostini - to my knowledge this IP is static and wont change... type: ifconfig In this case - you can see that my crostini IP address is: 100.115.92.197 - remember this ip address for later The configuration for Sync is stored in: /etc/resilio-sync/ Listing the files in there: root@penguin:/etc/resilio-sync# ls -la total 12 drwxr-xr-x 1 root root 92 Sep 12 13:19 . drwxr-xr-x 1 root root 2402 Sep 12 13:19 .. -rw-r--r-- 1 root root 174 May 23 16:42 config.json -rwxrwxr-x 1 root root 951 May 23 16:40 init_user_config.sh -rw-r--r-- 1 root root 193 May 23 16:40 user_config.json config.json is the file we are looking for - i will use "nano" to edit it with - if you dont have nano, install it with "apt-get install -y nano" Now lets edit the file and have a look at it, type: nano /etc/resilio-sync/config.json The standard config.json file looks like this: { Now its time to update / and add a few items.. like device_name, storage_path, listen, login and password... have a look at this: NOTICE: the storage path is for settings - not where you will actually sync folders to.. that will be decided via the webinterface Make your changes and save your file using CTRL+O Remember to create the primary storagepath folder.. in my case i use /home/leon/synced (since i can access /home/leon from the chrome OS files app) - i also chmod the folder in order to make sure sync can access it - there is properly a better way todo this, but its just me who is going to access it - so security is less important. root@penguin:/etc/resilio-sync# mkdir /home/leon/synced/ root@penguin:/etc/resilio-sync# chmod -R 777 /home/leon/synced/ Now that we have configured sync, its time to restart the sync application and access the webinterface. We'll do it like this: root@penguin:/etc/resilio-sync# /etc/init.d/resilio-sync stop [ ok ] Stopping resilio-sync (via systemctl): resilio-sync.service. root@penguin:/etc/resilio-sync# /etc/init.d/resilio-sync start [ ok ] Starting resilio-sync (via systemctl): resilio-sync.service. Open a web browser an goto: http://YOUR_CROSTINI_IPADDR:8888/gui/ .. follow the guide to setup the last things - if everything went ok you should have something like this on your screen: Congratulations - you now have ResilioSync on your chromebook and you can access it via your files app. Let the sync begin //Leon Notes: Make sure Resiliosync starts automaticlly (when you start crostini): Type: $ systemctl enable resilio-sync $ service resilio-sync start
  12. Hi, In a earlier thread we discussed howto make a good container for running Ubuntu 16.x with the unity interface - and while unity is a pretty sweet interface - Elementary OS might just suit us macOS geeks a tad better - sadly, no such target exists in crouton today and the solutions found on github for adding it dosent seem stable .. or well.. buggy at best. So, how now the best solution seems to install a standard ubuntu with xfce4 and modify it to suit our needs. I can't take the credits for making this guide - but i did put together a crouton backup that you can download directly from OSXL. Download link: http://files.osxlatitude.com/leon/crouton/eos-20180828-1804.tar.gz Quick restore guide: 0. As always, you need to be in developer mode, have crouton on your machine at have created atleast one machine 1. Download the file into your downloads folder 2. Open a console CTRL+ALT+T, change to shell and nagivate to your download folder 4. Now restore the container with: sudo edit-chroot -f /media/removable/your_path_on_drive_to_backup_file -r chrootname_of_your_choice 5. After restore, test to run it with "sudo startxfce4" 6. If it dident work to run it, try upgrading it with XIWI (notice that need to have the XIWI plugin installed in chrome for that to work) ... type: sudo sh ~/Downloads/crouton -t xiwi -u -n chroot_name_that_you_used_before If you did everything right you should get something pretty like this... btw.. user is "lsb" and password is "123123" ------ If you rather wanna do the hard work urself - just follow this guide: http://bobsbitsandbytes.blogspot.com/2013/09/installing-pantheon-theme-on-chromebook.html Enjoy!
  13. Orginal: https://beebom.com/how-to-install-android-apps-from-apk-files-on-chromebook/ Android apps coming to Chromebooks might very well be the defining moment for Google’s Chrome OS platform. In our usage of Android apps on Chromebook, we have found Chromebook’s functionality to have multiplied innumerably. However, there’s one catch, that is, many apps on the Play Store aren’t compatible with the Chromebook. For instance, apps like WhatsApp, Instagram, Uber, Inbox by Gmail, Chromecast, PayPal and more are incompatible because of various reasons like the fact that Play Store treats the Chromebook as an Android 6.0 tablet, the lack of GPS on Chromebooks etc. Thankfully, you can always sideload Android apps through APK files but Chromebook natively does not support these files. The good news is, there’s a way to install APK files on Chromebook and that’s what we are about to tell you. So, without further ado, let’s get on with it, shall we? Note: To install APKs, you will have to enable “Unknown Sources” and the option is only available on Chromebooks with developer mode enabled. To do it, check out our detailed post on how to enable developer mode on Chromebook. The Play Store is available on the Chrome OS 53 update through the developer channel and it’s only available for Chromebook Flip, as of now. So, before you try to install any APK files, check out our post on how to get Play Store. If you have the aforementioned Chrome OS build, here are the steps to install APK files on Chromebook: 1. Firstly, you will need a file manager Android app from the Play Store. So, open up Play Store and install the file manager you want. We used Solid Explorer in our test. 2. Then, download the APK files of apps you want to install from APKMirror.com. Meanwhile, go to Chrome OS Settings and click on “App Settings” in the Android Apps section. 3. The Android like Settings page should open up. Here, go to Security and turn on “Unknown sources”. 4. Once the APK file is downloaded, open the file manager app and go to the Downloads folder. Here, open the APK file and you should see the usual app installation interface from Android. Press “Install“. 5. The app installation might take a little longer than usual but the good news is, all the APKs we tried to install, did install without any fuss. Once the app is installed, tap “Open” to start using the app. Note: While most of the apps install via the APK files route, not all of them work. For instance, Instagram works fine but apps like Uber, which require location services don’t work.
  14. Orginal: https://www.reddit.com/r/Crostini/wiki/howto/backup How to Backup Containers Performing routine backups is always a good practice, and containers are no exception. Currently, this process is not the most straightforward due to the locked down termina VM, so here's how you can protect your data in case you need to powerwash. Everything will assume working with the default penguin container when you enable Linux within Chrome OS settings. Backup We will use LXC/LXD's image management tools to create and export the image. Enter into the termina VM through crosh by pressing ctrl+alt+t in the Chrome browser. Then we must stop the container, publish it, export the image to a backup file, and put that file somewhere we can access it. The termina VM is extremely locked down and the only writable locations are /tmp and $LXD_CONF (/mnt/stateful/lxd_conf). Step 1: Stop Container An alternative way to stop container from the below instructions is to issue the command sudo shutdown -h now from within the container itself crosh> vsh termina (termina) chronos@localhost ~ $ lxc list +---------+---------+------+------+------------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +---------+---------+------+------+------------+-----------+ | penguin | RUNNING | | | PERSISTENT | 0 | +---------+---------+------+------+------------+-----------+ (termina) chronos@localhost ~ $ lxc stop penguin --force (termina) chronos@localhost ~ $ lxc list +---------+---------+------+------+------------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +---------+---------+------+------+------------+-----------+ | penguin | STOPPED | | | PERSISTENT | 0 | +---------+---------+------+------+------------+-----------+ Step 2: Publish Container (termina) chronos@localhost ~ $ lxc publish penguin --alias backup Container published with fingerprint: 8ff49b7f315b5253ec2c5a38c97567bb33d4bd16c957d903ace4d9d9b56e9ef9 Step 3: Export Image (termina) chronos@localhost ~ $ lxc image export backup $LXD_CONF/backup Image exported successfully! Step 4: Start Container (termina) chronos@localhost ~ $ lxc start penguin (termina) chronos@localhost ~ $ lxc list +---------+---------+------+------+------------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +---------+---------+------+------+------------+-----------+ | penguin | RUNNING | | | PERSISTENT | 0 | +---------+---------+------+------+------------+-----------+ Step 5: Push Backup File Into Container Because of the locked down nature of the termina VM, we can't easily get at the file we just created so we will move it into our container's home directory where it will appear within the Chrome OS Files App. Note: you have to substitute "YOURUSERNAME" in the path below with the username in your penguin container. (termina) chronos@localhost ~ $ lxc file push $LXD_CONF/backup.tar.gz penguin/home/YOURUSERNAME/backup.tar.gz Alternate Step 5 Instead of simply pushing the file to the VM, we can mount the $LXD_CONF directory in our penguin container. This makes it much easier to use in the long run, saves on storage, and avoids the no space left on device error. (termina) chronos@localhost ~ $ lxc config device add penguin lxd-conf disk source=$LXD_CONF path=/mnt/lxd_conf This creates a directory inside the container at /mnt/lxd_config that contains all of our images. Use the mv command inside penguin to move the backup to your user directory and finally use ChromeOs's files app to move the backup somewhere safe! USERNAME@penguin ~ $ sudo mv /mnt/lxd_conf/FILENAME.tar.gz /home/USERNAME/FILENAME.tar.gz Copy the file out of your Linux Files in the ChromeOS File App and you are done! Step 6: Access your Backup File from Files App You can now open your Files App in Chrome OS, browse to Linux Files and access your backup file. Restore This section is in need of updating and isn't up to date with the above backup section. Feel free to take a moment and improve on it This is essentially the reverse of the backup steps. Once your archive is inside some "helper" container, we can pull it into the "/tmp" directory on the termina VM using the following: lxc file pull helper/tmp/backup.tar.gz /tmp We then import the image: lxc image import /tmp/backup.tar.gz --alias backup Finally we can create a new container using this image instead of the default Google image: lxc init backup penguin Issues With 4+ GB Images (or Anything Other Files) and Getting Them into Termina This sub-section was updated on 7/24/18 and is tested working on a Pixelbook running the Dev Channel Version 69.0.3473.0, in case this breaks later There are some odd issues with the way lxd works which end up making it difficult to import large files into Termina. Images can, however, quickly surpass this size, presenting obvious issues. Luckily, there is a process to get around this. First, you will need to use the split command to break apart your file into pieces smaller than 4 GB. To be safe, I will tell it to make 3 GB files. USERNAME@penguin ~ $ split -b 3GB backup.tar.gz backupSplit.tar.gz. This command will produce as many 3 GB files as needed to break apart all of backup.tar.gz into parts. (6GB = 2 files) The parts will have names backupSplit.tar.gz.aa backupSplit.tar.gz.ab backupSplit.tar.gz.ac ... backupSplit.tar.gz.zz. Then, use any method (see Alternate Step 5 above for my personal favorite method) to get the new 3GB files into termina. Once they are all there, we will use the cat command to recombine them. <useless nerd stuff> This command, short for catinate, is really interesting. It basically prints out the raw contents of any file in Linux, even those such as tar files that we wouldn't normally consider to have any raw content. This works because what split is doing is actually cutting the raw data at that point. These two tools, originally meant to work with text files and generally do totally different things, work together really well in this use case! Anyway, we can then use the linux commands > and >>, called append, to take the raw command line output output of catand add it to a file, as we'll see in a second. > just stores the would-be command line output to the file specified after the command while >> specifically appends the output to the end of the specified output. </useless nerd stuff> Method 1 We can do the recombination in a few ways. If it's just a few files, we can do it this way: (termina) chronos@localhost ~ $ cat backupSplit.tar.gz.aa > backupRecompiled.tar.gz (termina) chronos@localhost ~ $ cat backupSplit.tar.gz.ab >> backupRecompiled.tar.gz (termina) chronos@localhost ~ $ cat backupSplit.tar.gz.ac >> backupRecompiled.tar.gz This takes the raw content of the first file backupSplit.tar.gz.aa and puts it in backupRecompiled.tar.gz. It then appends the contents of backupSplit.tar.gz.ab and backupSplit.tar.gz.acto the end of that file. Method 2 If for some reason you have a stupidly huge backup that produces more than ~5 parts, you will want to do this in a better way. This better way is to use something of which I forgot the name (someone please correct me!), but basically acts as a for loop in this case. See below: (termina) chronos@localhost ~ $ cat backupSplit.tar.gz.?? > backupRecompiled.tar.gz This uses the question mark wildcards (??) to have the cat command run on all of the files starting with backupSplit.tar.gz. and ending with any two characters. I am listing both Methods 1 and 2 here is because 1) Method 1 is a better explanation of how these commands work and 2) Method 1 worked better for me (Method 2 should work and is the more elegant solution, but I guess it didn't feel like it on my system ¯\_(ツ)_/¯) After you have your full, recombined image in termina, proceed back up the section on restoring and start with lxc image import. Good luck with your data recovery!
×
×
  • Create New...