zonegrise Posted January 9, 2016 Posted January 9, 2016 Hi, Is nand-sata-install script still included in Armbian_4.5_Cubox-i_Debian_jessie_3.14.54.raw ? Thanks
Igor Posted January 10, 2016 Posted January 10, 2016 Yes, it should be ... if not, than they came with apt-get update / upgrade. They are now in standard system dir and not in root dir (which you might find in some outdated docs) so you just type: nand-sata-install 1
AS82 Posted March 16, 2016 Posted March 16, 2016 After moving system from SD to HDD which data/folder have to be left on SD?
Igor Posted March 17, 2016 Posted March 17, 2016 After moving system from SD to HDD which data/folder have to be left on SD? /boot 1
Bernie_O Posted March 17, 2016 Posted March 17, 2016 Would it even be possible to unmount SD, when system (on HDD) has finished booting?
Igor Posted March 17, 2016 Posted March 17, 2016 Yes, you can umount and even eject the card if you like ...
Bernie_O Posted March 17, 2016 Posted March 17, 2016 Thank you very much for the answer and for armbian in general :-) 1
Bernie_O Posted July 4, 2016 Posted July 4, 2016 For the record: it is not a good idea to have the SD-card unmounted, when doing an armbian-upgrade. Because during an armbian-upgrade there need to be files written in the folder /boot on the SD-card.
sussex1 Posted July 19, 2016 Posted July 19, 2016 The SATA disk root was moved to with the nand-sata-install script appears to have problems. Is there a way to revert to the original root on the SD card? EDIT Nevermind I just found the answer on Sunxi (change the root mount point in boot.cmd then "sudo mkimage -C none -A arm -T script -d boot.cmd boot.scr")
sysitos Posted July 19, 2016 Posted July 19, 2016 After moving the system from uSD to emmc on OPi+2E and rebooting, I don't have any access to the uSD card anymore. "fdisk -l" and "blkid -c /dev/null" doesn't show anything. Nothing in journal and syslog. Reinserting and reformation (on other PC) doesn't help. Any clues? Thanks.
alexxiao Posted July 31, 2016 Posted July 31, 2016 After moving the system from uSD to emmc on OPi+2E and rebooting, I don't have any access to the uSD card anymore. "fdisk -l" and "blkid -c /dev/null" doesn't show anything. Nothing in journal and syslog. Reinserting and reformation (on other PC) doesn't help. Any clues? Thanks. I am experiencing the same. Use image: Armbian_5.14_Orangepiplus_Debian_jessie_3.4.112_desktop. Could you please let me know if you found anything? Cheers
Igor Posted July 31, 2016 Posted July 31, 2016 It's a known issue but haven't got chance to look. Possible solution: http://forum.armbian.com/index.php/topic/1702-orange-pi-plus-2e-where-is-16ghz-and-sd
alexxiao Posted July 31, 2016 Posted July 31, 2016 It's a known issue but haven't got chance to look. Possible solution: http://forum.armbian.com/index.php/topic/1702-orange-pi-plus-2e-where-is-16ghz-and-sd Thanks a lot Igor, the solution works
berkovsky Posted February 12, 2017 Posted February 12, 2017 Hi! Thank u for work! If I manually updated the kernel to 4.4 +Can I use nand-sata-install system for transfer to the built-in nand memory?
berkovsky Posted February 12, 2017 Posted February 12, 2017 Device Drivers ---> <*> Memory Technology Device (MTD) support ---> <*> OpenFirmware partitioning information support <*> NAND Device Support ---> <*> Support for NAND on Allwinner SoCs But dont see nand ( 4.4.44 kernel
Igor Posted February 12, 2017 Posted February 12, 2017 This is completly off topic since it started for Cubox and you are asking about NAND on Allwinner. I assume you want to use it on Cubietruck ? Well, it's not reliable so it's disabled in DTB https://github.com/igorpecovnik/lib/blob/master/patch/kernel/sunxi-next/add-nand-to-cubietruck.patch.disabled For Allwinner A20 better upgrade to 4.9.9 ... there is no benefit of using kernel 4.4.x
Igor Posted February 12, 2017 Posted February 12, 2017 Excuse me! This banana pi m1 There is no NAND chip on M1 (unless you have some weird version). 1
Da Alchemist Posted April 6, 2017 Posted April 6, 2017 I have just build a new Image for my orange pi pc +2e (xenial desktop legacy kernel) and found the nand-sata-install script broken ek@orangepiplus2e:~$ sudo nand-sata-install [sudo] Passwort für ek: ls: Zugriff auf '/dev/nand*' nicht möglich: Datei oder Verzeichnis nicht gefunden in fact i wanted to test the armbian-config
Igor Posted April 7, 2017 Posted April 7, 2017 18 hours ago, Da Alchemist said: ls: Zugriff auf '/dev/nand*' nicht möglich: Datei oder Verzeichnis nicht gefunden This is not a problem but dirty "NAND availability check" ... BTW: for armbian-config testing you only need to switch to beta repository and issue apt-get update / upgrade. 1
tkaiser Posted April 7, 2017 Posted April 7, 2017 BTW: Tried nand-sata-install on a full OMV install and it failed horribly (as expected). Running this script with a lot of services running, having tons of files and databases open can not work. As long as we can't execute this from initrd or something like that it should be recommended to do a 'systemctl set-default $simple-target', reboot, run nand-sata-install, reboot and adjust target back. I would also believe adding /var/log to exclude.txt now that log2ram is active might be a good idea?
zador.blood.stained Posted April 7, 2017 Posted April 7, 2017 41 minutes ago, tkaiser said: As long as we can't execute this from initrd or something like that it should be recommended to do a 'systemctl set-default $simple-target', reboot, run nand-sata-install, reboot and adjust target back. Or we should check if we can use systemctl isolate? Quote isolate NAME Start the unit specified on the command line and its dependencies and stop all others. If a unit name with no extension is given, an extension of ".target" will be assumed. This is similar to changing the runlevel in a traditional init system. The isolate command will immediately stop processes that are not enabled in the new unit, possibly including the graphical environment or terminal you are currently using. Note that this is allowed only on units where AllowIsolate= is enabled. See systemd.unit(5) for details. 42 minutes ago, tkaiser said: I would also believe adding /var/log to exclude.txt now that log2ram is active might be a good idea? Yes, but we need to make sure that the directory /var/log is created on the target 1
tkaiser Posted April 7, 2017 Posted April 7, 2017 1 hour ago, zador.blood.stained said: Or we should check if we can use systemctl isolate? This looks interesting! So if I understood correctly we would bundle a 'nand-sata-install-helper' unit that will be called from within the script with 'systemctl isolate' to ensure that as much as services/units stopped before continuing? If so, I doubt I'm able to do this (still systemd noobie) but would suggest that we improve logging of nand-sata-install anyway: Move log away from /tmp/nand-sata-install.log to /var/log and always use append here (so we can add the contents to 'armbianmonitor -u' output to be able to diagnose problems users are running into) Add output from 'lsof / | awk 'NR==1 || $4~/[0-9][uw]/'' twice to this log: before and after so that it's at least documented which files were in a probably inconsistent state while syncing files
arox Posted April 7, 2017 Posted April 7, 2017 Well, if I understand your point, it means that we cannot make "consistent" online backup anyway ? (Loss of data is annoying, but inconsistency is far more problematic). And if I cannot make backups of my small $15 board without manual heavy procedure, what the use to install it on nand ?
tkaiser Posted April 7, 2017 Posted April 7, 2017 3 hours ago, arox said: Well, if I understand your point, it means that we cannot make "consistent" online backup anyway ? This is not backup but cloning to transfer the installation to another media. The problems are almost the same: open files might be saved in an incosistent state and cause trouble later. That's why we already have 2 rsync runs in nand-sata-install to catch these errors a bit but Zador's suggestion above looks promising: stopping as much daemons (that might have file handles for writing) as possible and then start the routine. The aforementioned check can be used to verify whether such problematic files still exist: lsof / | awk 'NR==1 || $4~/[0-9][uw]/' Of course it would be better to have something like Windows' shadow copy service and applications using this API since then we could really 'freeze' the installation before transferring it to somewhere else. But we're on linux here and can not even rely on filesystem snapshots so we have to deal with that crappy situation as best as possible. BTW: others do stuff similar, please compare with -a and -o options here for example: https://www.linux-tips-and-tricks.de/en/backup
Igor Posted April 8, 2017 Posted April 8, 2017 @Da Alchemist Should be o.k. now: https://github.com/igorpecovnik/lib/commit/71d89e856da2d56fa56822885a30149f7d2ee420 1
tkaiser Posted April 8, 2017 Posted April 8, 2017 With latest commits nand-sata-install should also be much more reliable when running on a system with typical services installed. See at the end of http://sprunge.us/FGOD Requires the following of course the next few weeks: wget -O- "https://raw.githubusercontent.com/igorpecovnik/lib/master/scripts/nand-sata-install/usr/lib/nand-sata-install/nand-sata-install.sh" >/usr/sbin/nand-sata-install
Antony Abi Rached Posted October 23, 2018 Posted October 23, 2018 Hello everyone, I am trying to run the nand-sand-install script in order to boot from SD card and have my filesystem on an SSD card. I am using this stretch armbian image with nanopi neocore : https://www.armbian.com/nanopi-neo/ What I did is the following : 1) I updated and upgraded the image after booting. 2) I deleted all the partitions that I have on my SSD disk. 3) I created an new partition on the SSD disk. 4) I didn't mount the disk. 5) I used armbian-config to run the nand-sata-install script. 6) The partition is detected and the files are transfered to the SSD disk. 7) After the script is done, I choosed to reboot. 8) After the reboot, I cannot access the nanopi. What I should do? My goal is to boot from SD and have my system on the SSD card. So normally I should keep only /boot on SD card and everything else should be on the SSD disk. Thanks in advance for the help.
Recommended Posts