backup – ubuntu libimobiledevice ios 14 focal 20.04

current behavior

When trying to backup my ios 14 on my ubuntu 20.04 I have the below error

idevicebackup2 backup /home/jb/iphone_backup_tmp/
Backup directory is "/home/jb/iphone_backup_tmp/"
Started "com.apple.mobilebackup2" service on port 52815.
Could not perform backup protocol version exchange, error code -1

I have an another ios 13 device and backup is working fine.

When trying to install the latest version from their official website https://libimobiledevice.org/#get-started
I got the below error

sudo apt-get install libimobiledevice usbmuxd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package libimobiledevice

expected behavior

be able to install the latest version of libimobiledevice and backup my ios 14 device via libimobiledevice

server – After Reboot Ubuntu 20.04 – RAID10 goes INACTIVE

I installed RAID 10 on a fresh Ubuntu 20.04

By the Following commands:

1. mdadm --examine /dev/sdc /dev/sdd /dev/sde /dev/sdf

2. parted /dev/sdc
x. select /dev/sdd
x. select /dev/sde
x. select /dev/sdf
 
1. mklabel gpt
2. unit TB
3. mkpart primary 0.00TB 14.00TB
4. print
5. quit

6. mdadm --create /dev/md0 --level=10 --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf

7. cat /proc/mdstat
8. mkfs.ext4 /dev/md0
9. mount /dev/md0 /mnt/raid10/

10. nano /etc/fstab
/dev/md0                /mnt/raid10              ext4    defaults        0 0

mount -a
mount -av

12. mdadm --detail --scan --verbose >> /etc/mdadm/mdadm.conf

Even save all config, after reboot RAID goes inactive-array

This is only Happens with Ubuntu 20.04
With Ubuntu 18.04 Working Good.

If I use, Raid restart.

`mdadm --stop /dev/md0`

    mdadm --create --verbose /dev/md0 --level=10 --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf

mdadm: array /dev/md0 started.

boot – Ubuntu 20.04. crash after refusing password for 3 time

Today, after 4monthes of perfect function, my Ubuntu 20.04 made me mad. After inserting correct password I was brought again on the same page for two more times than everything become black with the following screen

(0.355889) Initramfs unpacking faild: Decoding failed
/dev/sad2 contains a file system with errors, check forced.
(nodes that were part of a corrupted orphan linked list found.

/dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Fsck exited with status code 4
The root filesystem on /dve/sda2 requires a manual fsck

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.2) built-in shell (ash)
Enter ‘help’ for a built-in commands.

When I entered ‘help’ command:

.: (alias break cd chdir command continue echo eval exec exit export false getopts hash help history let local printf pwd read readonly return set shift test times trap true type ulimit umask unalias unset wait ( (( acpid arch ash awk basename blockdev busybox cat chmod chroot chvt clear cmp cp cut date deallocvt deluser devmem df du dumpkmap echo egrep env expr false fbset fgrep find fold fstrim grep gunzip gzip hostname hwclock ifconfig ip kill ln loadfont loadkmap ls lzop mkdir mkfifo mknod mkswap mktemp modinfo more mount mv nuke openvt pidof printf ps pwd readlink reboot reset rm rmdir run-init sed seq setkeycodes sh sleep sort stat static-sh stty switch_root sync tail tee test touch tr true tty umount uname uniq wc wget which yes

And I dont understand anything! What should I do now?

Please if anyone can help
Thank you

20.04 – Logging off after idle, regular settings set otherwise

I am using 20.04 on my HTPC and since last week everytime we change the input of the TV to the PC, there’s no signal being sent. Initially I thought the computer crashed and hard rebooted it; later I realized it was just logged off. I press Ctrl+Alt+F1 and the TV starts getting signal, brings me to the logon screen.

I searched all options regarding screensaver, logging out automatically, etc, it’s all set for this NOT to happen. Is there any other, non-obvious place where I could look to find an option that causes this behaviour?

Already tried the solutions from article below but the behaviour hasn’t changed:

Screen turning off when idle even with power settings disabled

Thank you.

20.04 – Logging in to ubuntu with lid closed

I am using a Lenovo Thinkpad T490 that I have wiped and installed ubuntu 20.04 on. Everything works well and I created a setup where I used three external monitors and just leave the laptop lid closed.

This is done using one monitor via USB-C and two via the other USB-C via a Lenovo Thinkpad USB-C Dock Gen 2 (where I also have my keyboard etc connected). All these pieces of hardware work together and there are no issues when the laptop is on.

Now, the issue I have is that when I boot the computer, I don’t get the login screen on any of my external monitors and I have to open the laptop lid to be able to log in. As soon as I open the laptoplid the keyboard will work and I can see the login screen on the laptop monitor and log in. As soon as I log in the laptop screen goes black (because I have disabled it) and the three external monitors kick in.

Is there a way I can fix this so that I don’t have to open up the laptop every time I boot the computer?

Dual boot failure: windows 10 and ubuntu 20.04 LTS

Yesterday my desktop stopped booting to either windows 10 or ubuntu 20.04. It gets to the grub screen where I can select either and continue but will only show black screen after.

  • Last thing windows did before the issue was install an update. So following advice from this site I rolled back that update, but didn’t help.
  • I tried booting from usb to live cd ubuntu which works (some of the times) and used boot-repair to fix it. Generated this report
    • It mentions in line 10 a full shutdown and then reboot – as opposed to a reset – so did that. Managed to boot into windows without a problem. Shutdown the computer from menu – waited a couple of secs – and started computer again. Same problem. Managed to boot into windows and ubuntu in similar fashion twice more of 2 dozen attempts, but not consistently.
    • It also mentions in line 130: => Windows 7/8/2012 is installed in the MBR of /dev/sdc. I had windows 8 installed but uninstalled and installed windows 10 about 2 weeks ago. Don’t know if that had anything to do with.
  • It sometimes mentions “initramfs unpacking failed: decoding failed” while booting, but that seems unrelated and I wasn’t able to fix it from a live usb ubuntu with these instructions.

Don’t see any way forward now. Hope anyone can give me some pointers forward. Would be much appreciated!

Linux 20.04 MCE Kernel Errors

Built a new PC: 10700k, z490 MSI board, 32gb Ram etc. Running Ubuntu 20.04 and getting an MCE (Machine Check Error): kernel: ( 0.185888) mce: CPU0: Thermal monitoring enabled (TM1).

The PC is just running the Game boost from the MSI Bios, and not manually overclocked. Using a Corsair H115 2*140mm cooler, with temperatures on idle being at most 32 degrees per core.

Apart from getting these MCE errors, sometimes the PC completely freezes when left on idle. A force restart is the only option. What could this be?

wireless – Ubuntu 20.04: Why does turning off “wi-fi can be turned off to save power” turn my wi-fi off?

The following item in Power…Settings… states:

Wi-Fi can be turned off to save power

wi-fi can be turned off

You can see that the option is currently turned on. That should mean that the system is allowed to turn off the Wi-Fi to save power.

However, when I turn off that option, my Wi-Fi is disabled (turned off).

I’m attempting to tell the system that it is not allowed to turn off Wi-Fi to save power.

However, when I turn off the option it actually turns off the Wi-Fi.
It’s seems that this item is not described properly in the Power….Settings…

Note: This option was the same under Ubuntu 18.04 also.

12.04 – ubuntu 20.04 NFS Share – permissions lost for nobody:nogroup on reboot

I am new to Ubuntu/linux, so, most of the config comes from reading guides.

Please bear with me.

I have a fresh install of ubuntu 20.04 server with the intention of using a NFS share as a NAS for a Hikvision camera.

This worked perfectly for a few months until I rebooted the server, and, the camera could not “see” the share. Rebooting the camera had no effect.

The error was (from memory) that the share path was not accessible. re-running

sudo chown nobody:nogroup /media/jack/camera1

Fixes it until reboot.

I am unsure how to fix this, can anyone advise? Why do the permissions get lost on reboot?

Steps I took to configure the server /share:

  1. Create a ext4 disc partition with the mount point /media/jack/camera1

  2. sudo apt update && sudo apt upgrade

  3. sudo apt -y install nfs-kernel-server

  4. add the following to etc/exports

    /media/jack/camera1 *(rw,sync,no_root_squash,no_subtree_check)

  5. cd/media/jack/camera1

  6. sudo rmdir lost+found

  7. sudo chown nobody:nogroup /media/jack/camera1

  8. sudo systemctl restart nfs-kernel-server

At this stage, I can connect to the share from the camera and store footage.
When the server reboots, the camera cannot “see” the drive, until I run

sudo chown nobody:nogroup /media/jack/camera1

Then I am back in business.

Appreciate any help you can give