Forum - Xbian-copier not working....

Workaround working nicely Smile

Today I hope to get more done trying to get this to run from usb. I'll try what you suggested @nachteule.

(20th Jan, 2018 06:43 PM)Skywatch Wrote: [ -> ]Workaround working nicely

Today I hope to get more done trying to get this to run from usb. I'll try what you suggested @nachteule.

Crossing fingers ... Cool

I'm experiencing an unrelated problem with xbian-copier. Here's the log file:

Code:

Performing full device TRIM /dev/mapper/loop0p2 (4.65GiB) ...

Label:              xbian-copy

UUID:              [redacted]

Node size:          16384

Sector size:        4096

Filesystem size:    4.65GiB

Block group profiles:

  Data:             single            8.00MiB

  Metadata:         single            8.00MiB

  System:           single            4.00MiB

SSD detected:       no

Incompat features:  extref, skinny-metadata

Number of devices:  1

Devices:

   ID        SIZE  PATH

    1     4.65GiB  /dev/mapper/loop0p2

Cloning subvolumes data, home, modules, root, storage (@)

Create subvolume '/tmp/btrfs-dest/data'

Create a readonly snapshot of '/tmp/btrfs-source/data/@' in '/tmp/btrfs-source/data/@.ro'

Delete subvolume (no-commit): '/tmp/btrfs-source/data/@.ro'

Create a snapshot of '/tmp/btrfs-dest/data/@.ro' in '/tmp/btrfs-dest/data/@'

Delete subvolume (no-commit): '/tmp/btrfs-dest/data/@.ro'

Done copying subvolume data snapshot @

Done copying subvolume data

Create subvolume '/tmp/btrfs-dest/home'

Create a readonly snapshot of '/tmp/btrfs-source/home/@' in '/tmp/btrfs-source/home/@.ro'

Cloning home/@, 106301624 of 2657540624, 4% done

Cloning home/@, 132877031 of 2657540624, 5% done

Cloning home/@, 212603249 of 2657540624, 8% done

Cloning home/@, 239178656 of 2657540624, 9% done

Cloning home/@, 372055687 of 2657540624, 14% done

Cloning home/@, 478357312 of 2657540624, 18% done

Cloning home/@, 504932718 of 2657540624, 19% done

Cloning home/@, 664385156 of 2657540624, 25% done

Cloning home/@, 717535968 of 2657540624, 27% done

Cloning home/@, 850412999 of 2657540624, 32% done

Cloning home/@, 903563812 of 2657540624, 34% done

Cloning home/@, 983290030 of 2657540624, 37% done

Cloning home/@, 1116167062 of 2657540624, 42% done

Cloning home/@, 1222468687 of 2657540624, 46% done

Cloning home/@, 1275619499 of 2657540624, 48% done

Cloning home/@, 1355345718 of 2657540624, 51% done

Cloning home/@, 1381921124 of 2657540624, 52% done

Cloning home/@, 1435071936 of 2657540624, 54% done

Cloning home/@, 1541373561 of 2657540624, 58% done

Cloning home/@, 1567948968 of 2657540624, 59% done

Cloning home/@, 1647675186 of 2657540624, 62% done

Cloning home/@, 1674250593 of 2657540624, 63% done

Cloning home/@, 1753976811 of 2657540624, 66% done

Cloning home/@, 1780552218 of 2657540624, 67% done

Cloning home/@, 1913429249 of 2657540624, 72% done

Cloning home/@, 2046306280 of 2657540624, 77% done

Cloning home/@, 2126032499 of 2657540624, 80% done

/usr/sbin/btrfs-auto-snapshot: line 719: ((: ERROR: send ioctl failed with -5: Input/output error > 80 : syntax error in expression (error token is ": send ioctl failed with -5: Input/output error > 80 ")

Cloning home/@, 2179183311 of 2657540624, 82% done

/usr/sbin/btrfs-auto-snapshot: line 719: ((: ERROR: unexpected EOF in stream > 82 : syntax error in expression (error token is ": unexpected EOF in stream > 82 ")

Copying subvolume home snapshot @ failed

Removing broken image file xbian.img

Fail!

Any suggestions on a fix?

@elrock
Not really Sad

Input/Output error never sounds good.

Source fs already checked? (btrfs scrub)
Destination device ok?
Power fail issue?

(21st Jan, 2018 01:24 AM)Nachteule Wrote: [ -> ]@elrock
Not really

Input/Output error never sounds good.

Source fs already checked? (btrfs scrub)
Destination device ok?
Power fail issue?

What is the pathway for the source fs? I found nothing in /tmp.

The destination device is a 8gb thumb drive formatted as ext2. It gets power from the RPi. Could that be the source of the problem?

(21st Jan, 2018 04:23 AM)elrock Wrote: [ -> ]
(21st Jan, 2018 01:24 AM)Nachteule Wrote: [ -> ]@elrock
Not really

Input/Output error never sounds good.

Source fs already checked? (btrfs scrub)
Destination device ok?
Power fail issue?

What is the pathway for the source fs? I found nothing in /tmp.

Oc not, source is / fs, so run sudo btrfs scrub start / && sudo btrfs scrub status / to check if fs is ok

Quote:The destination device is a 8gb thumb drive formatted as ext2. It gets power from the RPi. Could that be the source of the problem?

Sure

(21st Jan, 2018 04:37 AM)Nachteule Wrote: [ -> ]Oc not, source is / fs, so run sudo btrfs scrub start / && sudo btrfs scrub status / to check if fs is ok

So I ran the btrfs scrub and it found "11 uncorrectable errors," so no go. Is it still safe to restore from a backup of the Home directory, at least? I made a backup and it didn't encounter any errors.

(23rd Jan, 2018 06:09 AM)elrock Wrote: [ -> ]
(21st Jan, 2018 04:37 AM)Nachteule Wrote: [ -> ]Oc not, source is / fs, so run sudo btrfs scrub start / && sudo btrfs scrub status / to check if fs is ok

So I ran the btrfs scrub and it found "11 uncorrectable errors," so no go. Is it still safe to restore from a backup of the Home directory, at least? I made a backup and it didn't encounter any errors.

Ok, so we know the reason why Xbian-copier does not work without an error.

It should be safe, but it's better to locate those 11 files. AFAIR when running a scrub, those broken files are logged and can be displayed via dmesg command

So I still have this issue on my pi2 installs.....

Here is what I have done......

Terminal

xbian@cinema2film /mnt $ df -h
Filesystem Size Used Avail Use% Mounted on
udev 256K 4.0K 252K 2% /dev
tmpfs 71M 1.3M 70M 2% /run
/dev/mmcblk0p2 15G 3.5G 11G 25% /
/dev/mmcblk0p2 15G 3.5G 11G 25% /lib/modules
/dev/mmcblk0p2 15G 3.5G 11G 25% /home
/dev/mmcblk0p1 68M 35M 34M 52% /boot
none 4.0K 0 4.0K 0% /sys/fs/cgroup
/dev/mmcblk0p2 15G 3.5G 11G 25% /xbmc-backup
/dev/sda5 15G 2.7G 13G 18% /mnt
xbian@cinema2film /mnt $ lsusb
Bus 001 Device 005: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 004: ID 0e8f:00fb GreenAsia Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
xbian@cinema2film /mnt $ sudo -i
root@cinema2film ~ # blkid -s UUID -o value /dev/sda5
e86f613c-8db0-4fc6-99d1-53d8e4ff0e3a
root@cinema2film ~ # ^C
root@cinema2film ~ # sudo nano /boot/cmdline.txt
root@cinema2film ~ # sudo reboot

If I put "root=/dev/sda5" the pi goes into a never ending reboot loop.
If I put "root=UUID=e86f613c-8db0-4fc6-99d1-53d8e4ff0e3a" I get "sd card resize" on the main screen and that too never ends. ( have waited for 30mins + and still no end).

Where have I gone wrong? It used to work fine from usb following the instructions on the main page, but now I can't get it to boot properly..... ???

(29th Apr, 2018 02:07 AM)Skywatch Wrote: [ -> ]If I put "root=/dev/sda5" the pi goes into a never ending reboot loop.
If I put "root=UUID=e86f613c-8db0-4fc6-99d1-53d8e4ff0e3a" I get "sd card resize" on the main screen and that too never ends. ( have waited for 30mins + and still no end).

Where have I gone wrong? It used to work fine from usb following the instructions on the main page, but now I can't get it to boot properly..... ???

What's on /dev/sda5?

Does this answer your question?

Terminal

xbian@cinema2film ~ $ sudo blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="xbianboot" UUID="9451-67CD" TYPE="vfat" PARTUUID="5790c140-01"
/dev/mmcblk0p2: LABEL="xbian-copy" UUID="d3af7a2f-02ca-4741-8741-f8b5f45a398a" U UID_SUB="1c44f090-45cb-49eb-be9b-dd1533e907f8" TYPE="btrfs" PARTUUID="5790c140-0 2"
/dev/mmcblk0p3: UUID="abb5a071-3643-42db-8ff3-a9d1df0debf9" TYPE="swap" PARTUUID ="5790c140-03"
/dev/sda5: LABEL="xbian-copy" UUID="e86f613c-8db0-4fc6-99d1-53d8e4ff0e3a" UUID_S UB="e2e0b185-4ad7-42fa-9cdb-3de550d905ba" TYPE="btrfs" PARTUUID="015292a4-05"
/dev/zram0: UUID="f4e825d3-652e-4fca-9b3c-037a50c6af68" TYPE="swap"
/dev/mmcblk0: PTUUID="5790c140" PTTYPE="dos"

If I follow the guide on the wiki I get error message in xbian-config. I am confused as it all used to work fine - but I guess I attract this kind of thing Wink

(12th May, 2018 06:56 AM)Skywatch Wrote: [ -> ]Does this answer your question?

Terminal
xbian@cinema2film ~ $ sudo blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="xbianboot" UUID="9451-67CD" TYPE="vfat" PARTUUID="5790c140-01"
/dev/mmcblk0p2: LABEL="xbian-copy" UUID="d3af7a2f-02ca-4741-8741-f8b5f45a398a" U UID_SUB="1c44f090-45cb-49eb-be9b-dd1533e907f8" TYPE="btrfs" PARTUUID="5790c140-0 2"
/dev/mmcblk0p3: UUID="abb5a071-3643-42db-8ff3-a9d1df0debf9" TYPE="swap" PARTUUID ="5790c140-03"
/dev/sda5: LABEL="xbian-copy" UUID="e86f613c-8db0-4fc6-99d1-53d8e4ff0e3a" UUID_S UB="e2e0b185-4ad7-42fa-9cdb-3de550d905ba" TYPE="btrfs" PARTUUID="015292a4-05"
/dev/zram0: UUID="f4e825d3-652e-4fca-9b3c-037a50c6af68" TYPE="swap"
/dev/mmcblk0: PTUUID="5790c140" PTTYPE="dos"

Not completely. Hopefully you have the folder structure root/ modules/ and /home on it.

Maybe the scripts getting confused due to the identical labels of /dev/mmcblk0p2 and /dev/sda5 (I don't believe this, but who knows ...)

Quote:If I follow the guide on the wiki I get error message in xbian-config. I am confused as it all used to work fine - but I guess I attract this kind of thing

Hmmm, maybe the wiki lies Tongue

But, seriously, that should not be a big problem cloning root partition:
Select function 6 inside xbian-config, source /dev/root, destination /dev/sda5 and let it run. I did this many times

Should finish without any error message, but if you get error message, it's not big surprise that booting from this partition fails ... Dodgy

Hmmm.... This is interesting... From fdisk -l

Terminal

Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5790c140

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 * 2048 141311 139264 68M b W95 FAT32
/dev/mmcblk0p2 141312 30614527 30473216 14.5G 83 Linux
/dev/mmcblk0p3 30615552 31116287 500736 244.5M 82 Linux swap / Solaris

Disk /dev/sda: 14.9 GiB, 16005464064 bytes, 31260672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x015292a4

Device Boot Start End Sectors Size Id Type
/dev/sda1 16065 31246424 31230360 14.9G f W95 Ext'd (LBA)
/dev/sda5 16128 31246424 31230297 14.9G c W95 FAT32 (LBA)

Those last 2 lines seem to suggest that the stick is showing up twice ??? - I wouldn't have thought it was possible?

Still, if I select /dev/sda1 to copy to I get error message. If I select /dev/sda5 it completes, but won't boot when cmdline.txt has it's root=/dev/sda5 edit.

Oooops, strange partition table. I'm unsure that scripts can deal with that table

Partition 1 is extended Partition, you can't write data into, it's just a container for other (logical) partitions
and partition 5 has wrong partition type, should have 83 (Linux) instead of 0xc (FAT32 LBA)

I would create a new partition table and with only one primary partition. The partition layout you have absolutely makes no sense

You see, I told you it wasn't working Tongue

I'll try again tomorrow as I had a little bit of an accident today and definitly ruined a 64Gb microSD card, maybe a pi3 as well - need to look into that urgently. Could take some time though. Sad

Thanks for confirming that the problem was really there and not just in my head! Wink