Hy!
Copied a running SD-card of JeOS for raspi 3 with enlightenment desktop with Win32diskimager. On booting the raspi hangs while trying to mount some partition (can see on display, after loading kernel) without timeout and never finishes.
Mounted the card on another machine and found that eg
/dev/disk
is missing completely. How can that happen with a bit-by-bit copy?
Is there any way to make the copy bootable with reasonable effort?
Many thanks in advance!
That is virtual only exits when hardware is attached.
OK, so how to make this beast boot? 
No Idea. If you moved a running system from a working machine to another check that /etc/fstab is pointing to the new hardware not the old
Hi
What’s the release date of the image? Don’t have a serial connection available? If it’s last years image, you need to edit grub, press ‘e’ and on the linux line change CMA=384M to CMA=300M, if using a serial connection as well, change S0 to S1 for the tty…
I looked with
sudo blkid
and apparently the IDs match to the one of the original card and fstab refers to
/dev/disk/by-id:
/dev/disk/by-id/mmc-USDU1_0x1301b345-part2 / ext4 noatime,nobarrier 1 1
/dev/disk/by-id/mmc-USDU1_0x1301b345-part1 /boot/efi vfat defaults 0 0
/dev/disk/by-id/mmc-USDU1_0x1301b345-part3 swap swap defaults 0 0
This is what I get in the console after the edit by malcomlewis (had to add some info on the naming of the devices not shown correctly in the console, but on the screen, from which I took some photos…):
Booting a command list
Loading Linux 4.14.1-1-default ...
Loading initial ramdisk ...
4.994511] kvm [1]: Invalid trigger for IRQ4, assuming level low
6.848625] OF: /soc/usb@7e980000: could not get #phy-cells for /phy
TIME ] Timed out waiting for device dev-disk-by\x2did-mmc\x2dUSDU1_0x1301b345\x2dpart3.device.
[DEPEND] Dependency failed for Resume from /dev/disk-by-id/mmc
OK ] Reached target Local File Systems (Pre).
OK ] Reached target Local File Systems.
OK ] Reached target System Initialization.
OK ] Reached target Basic System.
* ] A start job is running for dev-disk-by\x2did-mmc\x2dUSDU1_0x1301b345\x2dpart2.device (4min 12s / no limit)
So apparently the naming of the devices is not correct? Would it help to change the naming in the “linux” line of grub? But which are the correct one’s?
Maybe faster to start over with the old TW JeOS image from October 2017 and add Enlightenment desktop…
This is what the linux line in grub says:
linux /boot/Image-4.14.1-1-default root=UUID=e1c89131-e6c3-4ad6-85fa-5fb4fab04c0e root=/dev/disk/by-id/mmc-USDU1_0x1301b345-part2 disk=/dev/disk/by-id/mmc-USDU1_0x1301b345 resume=/dev/disk/by-id/mmc-USDU1_0x1301b345-part3 quiet splash=silent plymouth.enable=0 swiotlb=512,force cma=384M console=tty0 console=ttyS0,115200n8 quiet
and these are the actual disk UUIDs I get for this card:
sudo blkid
...
/dev/sdd1: SEC_TYPE="msdos" LABEL="EFI" UUID="2835-4042" TYPE="vfat" PARTUUID="a7d16a20-01"
/dev/sdd2: LABEL="ROOT" UUID="e1c89131-e6c3-4ad6-85fa-5fb4fab04c0e" TYPE="ext4" PARTUUID="a7d16a20-02"
/dev/sdd3: UUID="e2caaf94-c5ba-403c-a323-991a0e466f5b" TYPE="swap" PARTUUID="a7d16a20-03"
So apparently the info in grub is identical to the UUID of the root partition, or? Why no boot?
Hi
OK so this system has already booted? What is the image date?
As I wrote: the original install is doing fine, only the Windisk32 copy of the SD-card will not boot
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.06.10-Build2.7.raw.xz
…with Enlightenment desktop, you remember? 
https://forums.opensuse.org/showthread.php/527460-TW-JeOS-on-raspi-3-want-a-light-weight-desktop
Here are the UUIDs of the original install, up and running on a Raspi 3
sudo blkid
[sudo] password for root:
/dev/mmcblk0: PTUUID="a7d16a20" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="EFI" UUID="2835-4042" TYPE="vfat" PARTUUID="a7d16a20-01"
/dev/mmcblk0p2: LABEL="ROOT" UUID="e1c89131-e6c3-4ad6-85fa-5fb4fab04c0e" TYPE="ext4" PARTUUID="a7d16a20-02"
/dev/mmcblk0p3: UUID="e2caaf94-c5ba-403c-a323-991a0e466f5b" TYPE="swap" PARTUUID="a7d16a20-03"
This the non-booting copy:
sudo blkid ...
/dev/sdd1: SEC_TYPE="msdos" LABEL="EFI" UUID="2835-4042" TYPE="vfat" PARTUUID="a7d16a20-01"
/dev/sdd2: LABEL="ROOT" UUID="e1c89131-e6c3-4ad6-85fa-5fb4fab04c0e" TYPE="ext4" PARTUUID="a7d16a20-02"
/dev/sdd3: UUID="e2caaf94-c5ba-403c-a323-991a0e466f5b" TYPE="swap" PARTUUID="a7d16a20-03"
They are identical. So what is not copied over or has to be changed, based on the SD-card to make this boot?
A few days ago, I posted that nothing good comes from using any Windows utilities in the burning of an image.
Recommend you only follow the instructions for burning the image on the Raspi download page only.
If you don’t want to burn an original image but want to copy, then that’s something I haven’t tried but I’d still recommend using something like dd instead of a Windows utility.
IMO and based on my own Windows utility experiences,
TSU
Hi tsu!
I used Win32diskimager for years, sometimes it’s the only option that works, Raspbian, BSD, whatever. Could you be a little more specific regarding your concerns. The win32diskimager worked flawlessly for me many, many times. Just a “Don’t do” will not change my opinion.
With dd and block sized it can be a real pain to copy an SD-card…
Win32diskimager may work for other uses, and even for some other Rpi images (IIRC it’s even recommended for at least one of the other RPi images… maybe Fedora?).
But, I’ve never found it works on an openSUSE RPi image.
In fact, it’s the reason for my research and successful solution for burning an openSUSE on a Windows machine by running openSUSE as a virtualized Guest, writing to the sdcard mounted as a raw file system/physical device
https://en.opensuse.org/User:Tsu2/Guest_write_to_device
TSU
…hmm, sounds like “many ghost drivers these days!”… Why is opensuse so special that Win32diskimager can’t handle it? Maybe then the story is set the right way? 
I was only under the impression that only Windows is an OS not to copy, not to move easily from one machine to another.
On Wed 31 Jan 2018 05:56:01 PM CST, suse rasputin wrote:
…hmm, sounds like “many ghost drivers these days!”… Why is opensuse
so special that Win32diskimager can’t handle it? Maybe then the story is
set the right way?
I was only under the impression that only Windows is an OS not to copy,
not to move easily from one machine to another.
Because it’s one of the few 64bit (aarch64) images around… notice the
32 in you app… that maybe the issue…?
As per the HCL, dd is the way to go
HCL… https://en.opensuse.org/HCL:Raspberry_Pi3
Worked everytime from me, but don’t use windows for these sorts of
tasks.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.104-39-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Sorry, but 32bit? 64bit? For a bit-wise copy program?
Is it possible at all to clone a FULLY INSTALLED TW for Raspberry from one SD-card to a second SD-card, so that both are bootable in the end? Has anybody done that?
On Wed 31 Jan 2018 08:06:01 PM CST, suse rasputin wrote:
Sorry, but 32bit? 64bit? For a bit-wise copy program?
Is it possible at all to clone a FULLY INSTALLED TW for Raspberry from
one SD-card to a second SD-card, so that both are bootable in the end?
Has anybody done that?
Hi
Who knows what funky stuff windows software does…?
I would swap back to dev id rather than uuid in both grub and
fstab, reboot make sure it’s all ok and then copy (dd) it over and
should be fine…
Since your running TW, boot from USB…? That’s what I use these days…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.3|GNOME 3.20.2|4.4.104-39-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi again!
Thanks for the suggestion, do you have any link with what to do exactly to “swap back to dev id rather than uuid in both grub and fstab”?
Then I could try…
I did a fresh install of TW JeOS for raspi 33, but that’s apparently unstable after updating to latest version (before drawing in the enlightenment pattern):
https://forums.opensuse.org/showthread.php/529432-JeOS-after-zypper-dup-errors-in-console
and I don’t want the wifi driver included in TW after updating.
I copied the intact TW JeOS with enlightenment desktop again to the SD-card, this time using dd. Exactly the same mount problems on boot as given above…