![]() |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
OK, so what exactly was the problem, and how did you fix it? I am thinking it sounds like what I have seen on some cards. It just fails, and until you reboot and run again it will continue to fail. It has something to do with the repartitioning. Some card handle it fine it seems, and some it seems need to be rebooted in order to be useable after a repartition. Glad to hear you eventually had success. I updated original post IF YOU COMPLETE THE INSTALL AND THE CLONE WONT BOOT, OR IF THE INSTALL FAILS. BOOT/REBOOT BACK TO FLASH AND RUN IT A SECOND TIME (LET IT UPDATE) THIS SHOULD FIX IT. SOME CARDS SEEM TO NEED TO BE REBOOTED BEFORE BEING USEFULL AFTER PARTITIONING If you look at the log output below you can see what is happening. Even though the script called it to reread the partition table, apparently it read the old one, and it did not create the needed devices we just created (/dev/mmcblk1pX) Rebooting and allowing the system to reread the card, it now will have the devices when it boots. Its possible that just removing the card, and then re-inserting it may work also, but I have not tested. LOG OUTPUT mke2fs 1.37 (21-Mar-2005) Could not stat /dev/mmcblk1p2 --- No such file or directory The device apparently does not exist; did you specify it correctly? mkswap: can't open '/dev/mmcblk1p3': No such file or directory swapon: can't stat '/dev/mmcblk1p3': No such file or directory mkdir: cannot create directory '/device': File exists mkdir: cannot create directory '/flash': File exists insmod: cannot insert '/mnt/initfs/lib/modules/2.6.21-omap1/mbcache.ko': File exists (-1): File exists insmod: cannot insert '/mnt/initfs/lib/modules/2.6.21-omap1/ext2.ko': File exists (-1): File exists mount: mounting /dev/mmcblk1p2 on /device failed ERROR SD CARD IS IN USE - SAVE DEB TO FLASH AND RE-RUN ERROR |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
I did not fix it actually.
I ran it, it failed, rebooted, "updated" it and this time it worked. And yes, it HAS to do with repartitioning. And dunno if you CAN do something about it. The very same issue appears if I repartition a card in the tablet from a Linux machine via USB. The tablet coninues to see the old partition map. About your test I am sorry I can't try it. Just finished re-configuring almost everything. The 'real' problem is if one wants to clone the FS to the internal 2Gb card of the N810. Did you try a "sync" after the re-partitioning in your scripts ? |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
The original script install-tools.deb worked fine on the internal 810. But I did have to reboot and re-run. I do call it to reread, it just must not be working on some cards. |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
is it possible use firesystem with EXT3
|
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
I know EXT2/EXT3 just like fat32/ntfs
|
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
|
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
And I am pretty sure using this is way faster that doing it manually, even for me. I dont see any way, I can fix this. OK OK, I dont see anyway, I am going to fix that. I could create a two deb process with a reboot between them, but I am lazy and this is working good :D |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
I would have to change some scripting, but its possible to do. But I honestly am not sure you would want to do this? I have not looked into the performance implications on using ext3 over ext2 on such a low power device. Its possible performance could be hurt by using ext3? I am sure Fanoush or someone will jump in here clarify this? |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
Quote:
Quote:
Spend you time in better ways. Thanks! :) |
Re: Clone OS to SD Deb!! Boot from SD made EASY!!
OK, I did not use this .deb (I wanted some things rather more complicated; I'll post what all I did do later...), but I have a suggestion: If you open the cover for whichever SD you're working with, ITOS will refrain from trying to mount it. But the device remains accessible, so I think this should work well with the .deb. I think this might eliminate some of the reboot needs around here... Comments, PB?
(And if I was anyone considering using this trick, I would definitely wait for further input; I think what I just said makes sense, and it seemed to work, but you really should wait for someone who knows the stuff to at least say they don't think it'll break things...) |
All times are GMT. The time now is 00:36. |
vBulletin® Version 3.8.8