[gr4vity]

Hi,

I had installed MLD for Raspberry Pi on an old 2GB SDcard in order to test it.

Everything works fine including creating, deleting or restoring a snapshot.

I decided to create an img for that SDcard then write it on an 8GB USB memory card.

The RPi can boot normally although i mentioned it was not possible without an SDcard which has bootcode.bin

Hi Roland,

I think not all USB mass storage devices will work.
At 1st it didn't for for me however i did the following to make it work

Format a microSD card as FAT32 and copy bootcode.bin from MLD boot directory to it.
Insert the microSD card into the card slot.

Now boot the pi, bootcode.bin will be loaded from the microSD card then it will continue booting from the USB-stick.

@Claus, are you able to boot MLD without any microSD card present in the pi?

Best Regards.

That isn't correct, MLD can boot from USB without any any SDcard prestent in the Pi.

Now i have a problem, when i create a snapshot, it takes bit longer than usual with errors like some files already exists then i noticed @root is also present as you can see in the screenshot.



I can't even delete that snapshot.
Anyone has experienced that issue?

Best Regards

[clausmuus]

Do you realy copy an image on the new device? An image of the whole device? Not only a copy of the file system?
Please post the output of "mount"

[gr4vity]

Hi Claus,

Yes, i created an image of the 2GB SDcard then wrote it on the 8GB USB stick.
After that i used gparted to expand the system partition then created another partition for media files.

Here is mount output

Code: [Select]

MLD> mount
/dev/sda2 on / type btrfs (rw,relatime,noacl,space_cache,subvolid=260,subvol=/@root)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmp on /tmp type tmpfs (rw,relatime)
run on /run type tmpfs (rw,relatime)
dev on /dev type devtmpfs (rw,relatime,size=341520k,nr_inodes=85380,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
log on /var/log type tmpfs (rw,relatime)
/dev/sda3 on /media/usb-sda3 type ext4 (rw,relatime)
/dev/sda2 on /mnt/mmcblk0p2 type btrfs (rw,relatime,noacl,space_cache,subvolid=257,subvol=/@data)
/dev/sda2 on /data type btrfs (rw,relatime,noacl,space_cache,subvolid=257,subvol=/@data)
/dev/sda2 on /var/cache type btrfs (rw,relatime,noacl,space_cache,subvolid=256,subvol=/@cache)
/dev/sda1 on /boot type vfat (rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)


[clausmuus]

I have no idea about the reason.

[gr4vity]

Okay, what about mount output?
Does it look fine?
I can do it one more time, could you please mention the steps you would do in such situation?
How will you copy the contents of the SDcard to the USB card?

Best Regards.

[baltic]

Show the /etc/fstab, please.
There must be something wrong, because sda2 is mounted as a root-, data-, .... Partition.

[clausmuus]

The mount output looks file. (sda2 has some volumes, witch are mountet to several places)
I think the problem is the resizing of the filesystem.

But you can use the MLD backup system to copy the MLD to the new device. You will found it in the setup.

[baltic]

Ach ja, btrfs..... 
Das vergesse ich immer mal wieder, werde ich auf meine alten Tage wohl nicht mehr so richtig vergegenwärtigt bekommen. 

[gr4vity]

Hello,

@baltic, here is /etc/fstab

Code: [Select]

proc        /proc           proc      defaults            0 0
sys         /sys            sysfs     defaults            0 0
run         /run            tmpfs     defaults            0 0
tmp         /tmp            tmpfs     defaults            0 0
dev         /dev            devtmpfs  defaults            0 0
devpts      /dev/pts        devpts    mode=0620,gid=5     0 0
/dev/dvd    /media/dvd      auto      ro,noauto           0 0
/dev/cdrom  /media/cdrom    auto      ro,noauto           0 0
UUID=0115bda4-bad2-44cd-8a1d-b1d280b991f1  /  auto  defaults  0 1
UUID=0115bda4-bad2-44cd-8a1d-b1d280b991f1  /mnt/mmcblk0p2  btrfs  subvol=@data  0 0
/mnt/mmcblk0p2  /data  none  bind  0 0
UUID=0115bda4-bad2-44cd-8a1d-b1d280b991f1  /var/cache  btrfs  subvol=@cache  0 0
UUID=7AE2-1D70  /boot  auto  defaults  0 2

@Claus, i want to clone everything from the SDcard including system kernel, installed applications, old snapshots, all folders ... etc
Using backup will do that?

I tried to create another snapshot, please check the following screenshot ... perhaps you can figure out what's wrong.



Best Regards.

[baltic]

Yeah, fstab looks fine.

I think, resizing he btrfs-partition by gparted corrupts the system. btrfs uses its own special tools for this, so take some time for reading about this.
But first, I would give Claus' suggestion a chance. It should do, what you need.

[gr4vity]

Yes, me too think the problem is caused after expanding the system partition using gparted.

Although everything works fine, the RPi boots and all applications are working normally.
The only problem i have is @root is created inside snapshots.   
I will wait for Claus suggestion.

[clausmuus]

...
But you can use the MLD backup system to copy the MLD to the new device. You will found it in the setup.

[gr4vity]

...
But you can use the MLD backup system to copy the MLD to the new device. You will found it in the setup.

Do you mean this option?



I just want to make sure that it will work, i don't want to do mistakes. 
I never tried it before, will this clone everything from the SDcard?

[clausmuus]

Yes, I mean that option. It's possible, that the hard drive configuration must be updated after the installation. Every other configuration will be copied from the running system.

[gr4vity]

Hi Claus,
It worked fine, i had to update system UUID in  /etc/fstab in order to boot .. thank you.
Is that what you meant by "the hard drive configuration must be updated after installation"?
Is there something else needs to be updated?
Because old snapshots from the SDcard are missing ... why?