My Headless Ubuntu 24.04.4 LTS was running happily on 6.17.0-19-generic,the server was rebooted yesterday, and clearly 6.17.0.20-generic became the running kernel.

I started to then have havoc with my video surveillance and NFS drives..

journalctl logged...

Apr 07 06:14:42 hal kernel: ata2.00: status: { DRDY }
Apr 07 06:14:42 hal kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr 07 06:14:42 hal kernel: ata2.00: cmd 60/00:d8:58:e6:44/01:00:81:01:00/40 tag 27 ncq dma 131072 in
                                     res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Apr 07 06:14:42 hal kernel: ata2.00: status: { DRDY }
Apr 07 06:14:42 hal kernel: ata2.00: failed command: READ FPDMA QUEUED
Apr 07 06:14:42 hal kernel: ata2.00: cmd 60/08:e8:00:15:85/00:00:ff:02:00/40 tag 29 ncq dma 4096 in
                                     res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Apr 07 06:14:42 hal kernel: ata2.00: status: { DRDY }
Apr 07 06:14:42 hal kernel: ata2: hard resetting link
Apr 07 06:14:42 hal kernel: ata2: SATA link down (SStatus 0 SControl 300)
Apr 07 06:14:48 hal kernel: ata2: hard resetting link
Apr 07 06:14:48 hal kernel: ata2: SATA link down (SStatus 0 SControl 300)
Apr 07 06:14:48 hal kernel: ata2: limiting SATA link speed to <unknown>
Apr 07 06:14:54 hal kernel: ata2: hard resetting link
Apr 07 06:14:54 hal kernel: ata2: SATA link down (SStatus 0 SControl 3F0)
Apr 07 06:14:54 hal kernel: ata2.00: disable device

This happens on two Toshiba NAS drives (SDB and SDD)

I suspect this may be caused by 6.17.0-20-generic applying power management aggressively, and as I have m2, ssd and NAS drives power management clearly annoys them.

I have reverted to 6.17.0-19-generic and everything is stable again.

I assume the simple solution is to run around /sys/block//device/power/control and set them all to off?

Any advice would be appreciated... as this is a server, stable is happy...

Regards John

Kubuntu 24.04 updated.

I have a shell script to launch a program.

#!/bin/bash
motion

Then I name it script.sh and make it executable. I then add a keyboard shortcut with the full path to the script. Nothing happens. I have tried this for years with many scripts and cannot solve the puzzle.

I want to press Meta-M and the program should start. I have tried adding sh before the path. I have added /bin/sh.

I am installing Ubuntu 26.04 with a RAID1 setup, but the system fails to boot after installation.

Setup:

• 2× NVMe drives (1TB each)

• RAID1 for redundancy

• Layout:

  • /boot → RAID1 (md0, ext4, metadata 1.0)

  • / → RAID1 (md1, ext4)

Steps performed:

1. Created identical partitions on both disks

2. Created:

   • md0 (RAID1) → /boot

   • md1 (RAID1) → /

3. Installed Ubuntu normally via the installer

On boot, the system drops into a dracut emergency shell with errors such as:

Warning: root device does not exist

It also fails to start a shell (Minor):

sulogin: failed to execute /bin/bash: No such file or directory

From the dracut shell:

mdadm --assemble --scan

After running this manually, the RAID arrays are assembled and the root device becomes available.

So the RAID arrays are valid, filesystems presumably too, but initramfs, or dracut in this instance is not assembling the raid automatically.

I tested the exact same setup with 24.04, 25.04, 25.10, and it works perfectly fine on those versions.
Is this a known issue with Ubuntu 26.04 and dracut?
Should mdadm RAID setups require additional manual configuration for dracut, or is this a bug in the installer/initramfs generation?

I’ve been having this issue where Bluetooth won’t turn on whenever USB tethering is enabled. It’s really frustrating.

I have a 5 year old HP 15z-gwooo, product ID 1E411AV that I only used 2 years before the HDD went bad. It has Windows 10 OS and I want to buy a new SSD and install Ubuntu and I was wondering if I had to install Windows 10 first? I hope that I can just replace the HDD with a SATAIII SDD straight into Linux?

Another zillion questions are, I can replace the HDD and have even recovered data on several bad drives over the years. But I have no idea of all the steps involved to make this change. Can anyone tell me what all is involved to do this or post a link to reputable article(s).

Also the HP laptop has a really crappy AMD Silver 3050U 2.3GHz up to 3.2GHz processor and 8GB DDR4 SODIMM RAM that is up-gradable to 32GB maximum but I think it would be wasted money considering the processor? According to HP this Lap Top supports NVMe M.2SSD up to 4TB. Thanks

I just switched back to Ubuntu 25.10 from Win 11. I have two monitors with different resolutions. Windows 11 has a handy tool built-in that allows for "smooth transitions" between monitors, so that if I am in the bottom or top part of my monitor with a higher resolution, it will still move the mouse over to the other monitor instead of hitting the edge of the screen and stopping until I get to the part of my screen where they "touch". To be clear, this isn't because of sticky edges or docks, just raw screen resolution differences.

Is there a tool to download that essentially does the same thing? I realize this is not the most urgent problem, but I am switching monitors a lot and it is a bit of an inconvenience. I know I can get used to it, but if there is a tool to accomplish this, then I would like to just use it. Thank you in advance.

Xubuntu 24.04.4

I've been running a new Intel Xeon W7-2595X system for a number of months now. I've experienced a couple of serious problem with a raid consisting two two Samsung 990 PRO 4 TB M.2 PCIe SSDs. The SSD partitioning is:

Partition        Label    FS Type    Mnt Pt      Flags       Size
--------------   ------   --------   ---------   ---------   ---------
nvme[01]n1p1:    esp      fat32      /boot/efi   boot, esp     1.05 GB
nvme[01]n1p2:    root     ext4       /           --          160.00 GB
nvme[01]n1p3:    user     ext4       /u          --            3.48 TB
unallocated:     --       --         --          --            1.84 MB

And the RAID1 consisted of two mirrored partitions:

/dev/md0:  /dev/nvme0n1p2  &  /dev/nvme1n1p2    # root filesystem
/dev/md1:  /dev/nvme0n1p3  &  /dev/nvme1n1p3    # user filesystem

A couple of months ago I got raid errors regarding the nvme1n device and partitions 2 and 3 were detached from the array. After a lot of searching through the logs I couldn't identify what happened, and decided that there was nothing seriously wrong with the SSD so I reattached both partitions and they synced up and everything has been running smoothly up until yesterday. This time it was nvme0n that was the problem and got detached and I discovered many serious errors reported by dmesg. I took relevant excerpts from the dmesg output and placed them in a file that can be reviewed here:

http://cjsa.com/misc/MD_dmesg.txt

My best guess is that this is a hardware failure. The devices still exist:

# ls -l /dev/nvme*
crw------- 1 root root  10, 261 Apr  1 08:50 /dev/nvme-fabrics
crw------- 1 root root 241,   0 Apr  1 08:50 /dev/nvme0
brw-rw---- 1 root disk 259,   0 Apr  6 11:27 /dev/nvme0n1
brw-rw---- 1 root disk 259,   1 Apr  6 11:27 /dev/nvme0n1p1
brw-rw---- 1 root disk 259,   2 Apr  6 11:27 /dev/nvme0n1p2
brw-rw---- 1 root disk 259,   3 Apr  6 11:27 /dev/nvme0n1p3
crw------- 1 root root 241,   1 Apr  1 08:50 /dev/nvme1
brw-rw---- 1 root disk 259,   4 Apr  6 15:11 /dev/nvme1n1
brw-rw---- 1 root disk 259,   5 Apr  6 15:11 /dev/nvme1n1p1
brw-rw---- 1 root disk 259,   6 Apr  6 15:11 /dev/nvme1n1p2
brw-rw---- 1 root disk 259,   7 Apr  6 15:11 /dev/nvme1n1p3

I marked the devices as failed and then removed them from the array. When I attempt to reattach them I get the message:

# mdadm  --manage  /dev/md0  -a  /dev/nvme0n1p2         # re-add device
mdadm: Failed to write metadata to /dev/nvme0n1p2

# mdadm  --manage  /dev/md1  -a  /dev/nvme0n1p3         # re-add device
mdadm: Failed to write metadata to /dev/nvme1n1p3

lsblk reports on the devices:

# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1     259:0    0     0B  0 disk
├─nvme0n1p1 259:1    0     1G  0 part  /boot/efi
├─nvme0n1p2 259:2    0   160G  0 part
└─nvme0n1p3 259:3    0   3.5T  0 part
nvme1n1     259:4    0   3.6T  0 disk
├─nvme1n1p1 259:5    0     1G  0 part
├─nvme1n1p2 259:6    0   160G  0 part
│ └─md0       9:0    0 159.9G  0 raid1
│   └─md0p1 259:9    0 159.9G  0 part  /
└─nvme1n1p3 259:7    0   3.5T  0 part
  └─md1       9:1    0   3.5T  0 raid1
    └─md1p1 259:8    0   3.5T  0 part  /u

Neither gnome-disks nor gparted can see the nvme0n device.

As I said, I'm pretty sure this is a hardware failure with the SSD, but I wanted to ask whether there were any known ongoing problems with the mdadm software that I should be aware of? Thanks.

My computer has a usb floppy disk drive plugged in & when my computer is on it polls the drive every two seconds to check for a disk. How do I change/disable this so my drive stops clicking? I am on Ubuntu 24.04.04 LTS

OS: Xubuntu 24.04.4

I'm just looking for a little reassurance here from RAID experts.

I had a RAID1 array comprised of two Samsung 990 PRO 4 TB M.2 PCIe SSDs with device names of /dev/nvme0n1 and /dev/nvme1n1. Both SSDs were partitioned as follows:

Partition        Label    FS Type    Mnt Pt      Flags       Size
--------------   ------   --------   ---------   ---------   ---------
nvme[01]n1p1:    esp      fat32      /boot/efi   boot, esp     1.05 GB
nvme[01]n1p2:    root     ext4       /           --          160.00 GB
nvme[01]n1p3:    user     ext4       /u          --            3.48 TB
unallocated:     --       --         --          --            1.84 MB

nvme01n1p1 was the /boot/efi device

The RAID1 consisted of two partition:

/dev/md0:  /dev/nvme0n1p2  &  /dev/nvme1n1p2    # root filesystem
/dev/md1:  /dev/nvme0n1p3  &  /dev/nvme1n1p3    # user filesystem

There appears to have been a catastrophic failure on the /dev/nvme0n1 SSD and its partitions p2 and p3 were detached from the respective mirrors. It appears that the SSD is non-recoverable (that's a separate issue and post) but I'm concerned about rebooting successfully after taking the machine down to extract the bad device. When setting up the mirror during the original system build I followed the excellent advice in this article:

https://kifarunix.com/install-ubuntu-24-04-with-uefi-and-software-raid-1/

I duplicated the FAT boot partition from the first SSD (nvme0n1p1) to the second (nvme1n1p1) and reassigned the same UUID to the second.

Here is the relevant line from /etc/fstab:

/dev/disk/by-uuid/2E76-394F  /boot/efi  vfat  defaults  0  1

And as seen here, the damaged SSD was the boot partition for the currently running system:

# lsblk -f
nvme0n1
  nvme0n1p1     1G     1%    /boot/efi
  nvme0n1p2
  nvme0n1p3

Here is the UUID of partition nvme1n1p1:

# blkid /dev/nvme1n1p1
/dev/nvme1n1p1: UUID="2E76-394F" BLOCK_SIZE="512" TYPE="vfat"  ...

The article indicates that with the same UUID this should allow the system to automatically boot from /dev/nvme1n1p1 without problem.

My question is whether this looks correct to others, and if I should encounter problems, are there any recovery steps I should be aware of before the reboot?

Thanks for any insights.

Jeff Small

I'm trying to install 24.04.4 Ubuntu Server from a usb stick.

Tell me there is a way to change the text color. The white text on a yellow background and the white text on a white background have me in an unfavorable state for much social.

Not being able to SEE the text is making things like setting the username and password impossible.

Im currently at 1600x900 both at sddm and desktop, The problem is that uppon logging in to x11 the cursor becomes small again to 1920x1080 and then it goes back to normal aka 1600x900 after some seconds before it loads the desktop…How can I smooth this out?

Im using Kubuntu 25.10

I am running Ubuntu 24.04.4 on a ThinkPad T14s. I am having trouble connecting to the Eduroam WiFi network at my school on Ubuntu. When I try to connect, it takes a long time and usually only connects after multiple attempts. Sometimes it fails several times before finally connecting.

I do not have this issue with other WiFi networks. They connect quickly and work normally. The problem only happens with eduroam.

Here is the Eduroam security configuration that shows the security configuration I am using for Eduroam.

Has anyone experienced this issue before or knows what might be causing the slow connection and repeated connection attempts?

Have tried all online instructions and suggestions available. Nothing has helped so far. Tuta uses a different type of file for their app download. Proton mail installs easily from terminal but tutamail uses some type of executable.

Maybe someone here might help?

Can't connect to various websites via text-based browser W3M.

Works in Lynx however.

Cookies are activated in settings (default, and I have viewed generated cookies from other websites to make sure).

Error message when attempting:

I'm trying to run a program from 2001 and they've used (according to some forum) an integer to express the amount of available RAM for the installer. An error message saying "not enough memory" interrupts as soon as you start.

I have a 2 gig module but I don't want to reconfigure physically if I can just change boot settings. Maybe there's a way to limit it at runtime even.

I am using a Baseus USB Bluetooth Adapter for my pc, and it works fine. However, when I am simultaneously connected via USB to my phone for tethering, it no longer allows me to turn on Bluetooth.

When I unplug and plug the dongle, Bluetooth apparently gets turned on, but I get a bunch of notifications saying ''Connection failed: Activation of network connection failed" (and it does not work either).

This adapter supports Bluetooth Low Energy (BLE). It comes with drivers and software for the Windoze environment. Ubuntu 24.04 recognizes the device but it is not functional out-of-the-box. It seems to require additional software or drivers...

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0c45:64ab Microdia Integrated Camera
Bus 001 Device 004: ID 2357:0604 TP-Link TP-Link UB500 Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

I have a Mini PC called Beelink Mini S12 that I use as Media Server. I has Ubuntu Server 24.04.4 LTS with 6.17.0-14-generic kernel on it.

I did all setups like 6 months ago and after that never had to touch it again. it was 100% working well and stable until yesterday when I was not able to connect into it anymore.

Today after some investigation I found that it had lost the Ethernet connect and as I was using it connected into my router via cable I lost the access. I re-enabled the WiFi temporally to be able to work on it until I found and fixed the issue with Ethernet, but after trying everything I'm still stuck and I don't have my Ethernet connection back.

Here is some prints from my setup/Ethernet:

Results of lsb_release –a:

My network interfaces:

Network hardware Realtek RTL8111/8168/8211/8411:

Driver updated to use r8168-dkms:

netplan that normally as only the Ethernet part and I leave the WiFi commented out:

I have no idea what is going as it was working before and I didn't update anything (at least not manually by myself).

I have an ~1 year old Lenovo Legion 7i laptop with Intel Core i9 processor and NVIDIA RTX4070 that I have recently made the jump from Windows to Ubuntu 24.04.3. While I am brand new to Linux and a bit over my head, the transition has overall gone very smoothly and I love the OS, however I have one persistent problem that I have not been able to resolve. The audio to my Google Pixel Buds Pro 2 is highly distorted and choppy. These same earbuds worked fine with this laptop on the previous Windows OS and continue to work fine with other devices (my Android phone and work laptop). Audio from the laptop speakers themselves is normal. Another pair of Bluetooth headphones (Sony) exhibited the same issue, but I do not intend to use these moving forward. The source of the audio does not seem to matter - I have the same issues regardless of web browser (I've tried Brave [preferred], Firefox, and Chrome), website or other media players.

EDIT: I have now confirmed that this is directly related to wifi interference. The audio distortion begins immediately upon turning on wifi and resolves immediately upon turning it back off. My wifi network is 5GHz so it theoretically should not be interfering with bluetooth but now I'm not so sure.

EDIT 2: The audio issues resolve if I switch to the 2.4G wifi band, which makes no sense to me. Unfortunately, as expected, having both wifi and bluetooth running simultaneously on this slows the internet down to practically unusable speeds so this is not really a viable fix.

EDIT 3: Further research has led me to suspect an issue with my laptop's Realtek hardware and the current kernel. However, when I tried to downgrade to a few different older kernels it completely broke my wifi, bluetooth, and trackpad so this also doesn't seem to be a viable fix.

Troubleshooting steps that I've tried based on my own research online, but have not helped (I will update as I continue my own troubleshooting):

1. Updated drivers

2. Ensured that High Fidelity Playback (A2DP Sink) is enabled in sound settings

3. Forget and Repair device multiple times.

4. Disabled noise cancellation through the buds app.

5. Disabled multipoint connection and audio switch through the buds app.

6. Disabled browser hardware acceleration.

7. Ensured that system is using fully updated Pipewire and performed a Wireplumber reset.

8. Forced a consistent sampling rate at both 48kHz and 44.1kHz

9. Forced a fixed buffer size (quantum) of both 1024 and 512

10. Disabled the Autosuspend function

11. Disabled the WiFi/Bluetooth coexistence from the terminal. No improvement. Subsequently re-enabled coexistence, still with no improvement.

12. Disabled wifi power management -- this actually made the sound distortion dramatically worse so I turned it back on.

13. Disabled Bluetooth LE Audio

14. Full disk wipe and reinstallation of Ubuntu and retried all above options.

I am hoping that someone can offer some insight into what I may be missing that could be contributing to this issue.

I'm experiencing frequent screen freezes where the system becomes unresponsive, requiring a reboot. The issue occurs randomly and is accompanied by multiple i915 GPU errors in dmesg. Here are some of the errors I see frequently:

➜  ~ sudo dmesg --level=err

[   43.626469] int3472-discrete INT3472:01: INT3472 seems to have no dependents.
[   44.188775] spi-nor spi0.0: error -EOPNOTSUPP: Failed to register OTP NVMEM device
[   44.887133] i915 0000:00:02.0: [drm] *ERROR* GT1: Request submission for GSC load failed -ETIME
[   44.887141] i915 0000:00:02.0: [drm] *ERROR* GT1: Failed to load GSC firmware i915/mtl_gsc_1.bin -ETIME
[   51.439648] i915 0000:00:02.0: [drm] *ERROR* GT1: GUC: Engine reset failed on 5:6 (other0) because 0x00000000
[   53.964142] iwlwifi 0000:71:00.0: WRT: Invalid buffer destination
[   55.719199] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: port,transcoder,
[   55.860928] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[   56.099264] iwlwifi 0000:71:00.0: WRT: Invalid buffer destination
[ 1193.503795] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=163843 end=163844) time 283 us, min 1418, max 1439, scanline start 1385, end 1447
[ 2563.320568] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error
[ 2564.080937] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error
[ 2691.516935] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe B (start=379456 end=379457) time 213 us, min 1418, max 1439, scanline start 1411, end 1413
[ 4788.425019] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=52920 end=52921) time 233 us, min 1184, max 1199, scanline start 1174, end 1210
[ 5377.547440] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=79302 end=79303) time 275 us, min 1184, max 1199, scanline start 1158, end 1159
[ 5437.747272] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=82914 end=82915) time 268 us, min 1184, max 1199, scanline start 1179, end 1220
[ 7149.620572] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error
[ 7150.364445] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error
[ 7154.130231] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error
[ 7184.521332] intel-ipu6-isys intel-ipu6-isys0: csi2-4 error: Frame sync error

System information:

• OS: Ubuntu 24.04
• Kernel: 6.8.0-52-generic
• Desktop Environment: GNOME 46.0 (Wayland)
• Laptop Model: Dell XPS 13 9340
• CPU: Intel Core Ultra 7 155H (16-core)
• GPU: Intel Arc Graphics (Meteor Lake) - i915 driver
• RAM: 16GB
• Storage: 512GB NVMe SSD (Western Digital PC SN740)
• Networking: Intel Wi-Fi 7 AX1775

I don't know if it is related, but I also have noticed that there is a ghost screen (Unknown 24") for some reason, even with no external monitors attached. I always see a secondary display in the Settings app.

I have Kubuntu 23.04 running on Dell XPS 15. it won't boot after updating?

Kernel panic:

[ 1.062709] /dev/root: Can't open blockdev
[ 1.062798] Console: switching to colour frame buffer device 216x67
[ 1.064741] VFS: Cannot open root device "nvme0n1p8" or unknown-block(0,0): error -6
[ 1.064749] Please append a correct "root=" boot option; here are the available partitions:
[ 1.064753] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.064755] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.2.0-23-generic #23-Ubuntu
[ 1.064758] Hardware name: Dell Inc. XPS 15 9520/0YD3W1, BIOS 1.13.1 04/17/2023
[ 1.064760] Call Trace:
[ 1.064763]  <TASK>
[ 1.064766]  dump_stack_lvl+0x48/0x70
[ 1.064772]  dump_stack+0x10/0x20
[ 1.064773]  panic+0x37b/0x3c0
[ 1.064778]  mount_block_root+0x2c9/0x2d0
[ 1.064783]  mount_root+0x83/0xb0
[ 1.064784]  prepare_namespace+0x1f5/0x200
[ 1.064785]  kernel_init_freeable+0x1e5/0x220
[ 1.064786]  ? __pfx_kernel_init+0x10/0x10
[ 1.064791]  kernel_init+0x1b/0x200
[ 1.064793]  ? __pfx_kernel_init+0x10/0x10
[ 1.064795]  ret_from_fork+0x29/0x50
[ 1.064797]  </TASK>
[ 1.064966] Kernel Offset: 0x1f200000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff
[ 1.065497] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
_

There are well over a decade's worth of mutually incompatible instructions for setting up basic pinyin input on previous versions of Ubuntu. People make lots of claims about needing to do now obsolete rubbish, which means that many people (including me) end up spending many hours only to end up with a broken install.

Is there a simple procedure to set up Chinese pinyin input for simplified characters that doesn't require many hours of trial and error and leave the system half broken?

My machine is running Ubuntu 20.04 dual booted with Windows 10. My Windows installation is working fine without any issues, and I am able to operate on Windows, but when I try to boot Ubuntu it kernel panics.

[    0.110628] x86/cpu: SGX disabled by BIOS
/dev/sda5: clean, 649596/30203904 files, 20811140/120787200 blocks
/sbin/init: error while loading shared libraries: /lib/x86_64-linux-gnu/libcrypto.so.1.1: invalid ELF head
[    2.784895] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[    2.784971] CPU: 11 PID: 1 Comm: init Not tainted 5.11.0-40-generic #44~20.04.2-Ubuntu
[    2.785050] Hardware name: Dell Inc. OptiPlex 3080/0M5WNK, BIOS 1.1.0 05/31/2020
[    2.785118] Call Trace:
[    2.785150]  dump_stack+0x74/0x92
[    2.785197]  panic+0x101/0x2e3
[    2.785237]  do_exit.cold+0x60/0xb0
[    2.785280]  do_group_exit+0x43/0xa0
[    2.785324]  __x64_sys_exit_group+0x18/0x20
[    2.785372]  do_syscall_64+0x38/0x90
[    2.785412]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    2.785468] RIP: 0033:0x7f40551852ae
[    2.785508] Code: 89 fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 14 0f 1f 44 00 00 89 d7 89 f0 0f 05 48 3d
[    2.785671] RSP: 002b:00007ffdbe0864f8 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
[    2.785746] RAX: ffffffffffffffda RBX: 00007f4054870550 RCX: 00007f40551852ae
[    2.785814] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f
[    2.785880] RBP: 00007ffdbe0871a0 R08: 00000000000000e7 R09: 0000000000000000
[    2.785947] R10: 00007f405518c169 R11: 0000000000000206 R12: 00007f405518e8b0
[    2.786013] R13: 00007f4054870590 R14: 0000000000000000 R15: 0000000000000000
[    2.786170] Kernel Offset: 0x8e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0x
[    2.786275] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---
_

after I couldn't do anything anymore while using Ubuntu 20.04 LTS I had to force power off, and now it won't boot anymore. I ran a hardware check and everything appears to be okay (obviously I was particularly concerned about the hard drive).

What happens is that I end up in the BusyBox shell when I try to boot Ubuntu. After typing "exit" to get more information (as suggested in many other threads) I get this:

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

(initramfs) exit
[   14.262022] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   14.262040] CPU: 6 PID: 1 Comm: sh Not tainted 5.4.0-53-generic #59-Ubuntu
[   14.262054] Hardware name: LENOVO 20N3S02J00/20N3S02J00, BIOS N2IET75W (1.53 ) 08/21/2019
[   14.262070] Call Trace:
[   14.262081]  dump_stack+0x6d/0x9a
[   14.262091]  panic+0x101/0x2e3
[   14.262099]  do_exit.cold+0x9b/0xb5
[   14.262108]  do_group_exit+0x47/0xb0
[   14.262116]  __x64_sys_exit_group+0x18/0x20
[   14.262127]  do_syscall_64+0x57/0x190
[   14.262136]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   14.262148] RIP: 0033:0x7fbeceb49136
[   14.262157] Code: fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 15 66 0f 1f 44 00 00 89 d7 89 f0 0f 05 48 3c
[   14.262190] RSP: 002b:00007ffe7f48cf88 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7
[   14.262206] RAX: ffffffffffffffda RBX: 00005653199a8704 RCX: 00007fbeceb49136
[   14.262220] RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
[   14.262234] RBP: 0000000000000001 R08: 00000000000000e7 R09: ffffffffffffffd0
[   14.262248] R10: 00005653185b28b8 R11: 0000000000000202 R12: 0000000000000003
[   14.262262] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[   14.262328] Kernel Offset: 0xea00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xf
[   14.262366] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---
_

That happens regardless if I try kernel 5.4.0-53 or 5.4.0-52. I don't have any other options during startup.

Switching to recovery mode (again it doesn't matter which kernel I select) I got some more output and then repeatedly this:

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

        -c DEV Reopen stdio to DEV after switch
        -d CAPS Drop capabilities
        -n     Dry run

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.2) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

        -c DEV Reopen stdio to DEV after switch
        -d CAPS Drop capabilities
        -n     Dry run

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.2) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

        -c DEV Reopen stdio to DEV after switch
        -d CAPS Drop capabilities
        -n     Dry run

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.2) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

        -c DEV Reopen stdio to DEV after switch
        -d CAPS Drop capabilities
        -n     Dry run

No init found. Try passing init= bootarg.

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

(initramfs) [   44.226330] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCIO.RP09.PEGP.NVDN], AE_NOT_FOUND (20190816/psargs-330)
[   44.226911] No Local Variables are initialized for Method [_Q3C]
[   44.227487] No Arguments are initialized for method [_Q3C]
[   44.228067] ACPI Error: Aborting method _SB.PCIO.LPCB.EC._Q3C due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
_

I tried to get access to my data using Ubuntu Live CD, but there is no /dev/sda*, just two partitions (UEFI and LVM Linux).

I get this kernel panic error when trying to start my computer:

[    0.344971] Initramfs unpacking failed: invalid magic at start of compressed
archive
[    0.540993] integrity: Problem loading X.509 certificate -65
[    0.541018] integrity: Problem loading X.509 certificate -65
[    0.727431] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.727463] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.4.0-47-generic #51-Ubuntu
[    0.727487] Hardware name: Acer Nitro AN515-52/Freed_CFS, BIOS V1.28 08/05/2019
[    0.727511] Call Trace:
[    0.727526]  dump_stack+0x6d/0x9a
[    0.727548]  panic+0x101/0x2e3
[    0.727553]  mount_block_root+0x23f/0x2e8
[    0.727569]  mount_root+0x38/0x3a
[    0.727581]  prepare_namespace+0x13f/0x194
[    0.727596]  kernel_init_freeable+0x231/0x255
[    0.727613]  ? rest_init+0xb0/0xb0
[    0.727626]  kernel_init+0xe/0x100
[    0.727640]  ret_from_fork+0x35/0x40
[    0.727702] Kernel Offset: 0x17000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    0.727738] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
_

I found a way to enter in a previous version of kernel (5.4.0-42) but when the computer reboots I'm still getting the same message. I'm new in Ubuntu so I really don't know what to do.

SMART Data & Self-Tests:

I am asking this question because I was facing the same issue and could not find a complete solution so here it is.
Steps to follow :
1. Open Files app, go to home.
2. Open .bashrc file using text editor (hit ctrl+H if .bashrc file is not seen)
3. Scroll all the way to the end and type this -

export PATH="$HOME/.local/bin:$PATH"

And save the file.
4. Now open the terminal and type -

source ~/.bashrc

5. You can either use option 4 or just restart your computer.

Been trying to setup a plex server for the last 2 days. I initially had it up and running, but I rebooted, and now I can't get it start back up.

Background:

• Running 16.04 32bit
• Had installed and set up server once everything was working fine
• Rebooted machine
• Since reboot, have not been able to get server running
  • Ran sudo dpkg -r plexmediaserver and sudo dpkg -P plexmediaserver, then reinstalled, but this bares no effect on the error
• Also running sonarr and nzbget (I doubt that has any impact on the issue, but you never know)

Ran sudo systemctl status plexmediaserver and output is as follows:

    plexmediaserver.service - Plex Media Server for Linux
    Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
    Active: inactive (dead) (Result: exit-code) since Mon 2017-11-20 21:47:11 EST; 44s ago
    Process: 5144 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/plexmediaserver/Plex Media Server" (
    Process: 5140 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" || /bin/mkdir -p "${
    Main PID: 5144 (code=exited, status=127)

    Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Unit entered failed state.
    Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
    Nov 20 21:47:11 media-server systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
    Nov 20 21:47:11 media-server systemd[1]: Stopped Plex Media Server for Linux.
    Nov 20 21:47:11 media-server systemd[1]: plexmediaserver.service: Start request repeated too quickly.
    Nov 20 21:47:11 media-server systemd[1]: Failed to start Plex Media Server for Linux.
    Nov 20 21:47:44 media-server systemd[1]: Stopped Plex Media Server for Linux.

results of journalctl -xe

-- Subject: Unit plexmediaserver.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit plexmediaserver.service has finished starting up.
-- 
-- The start-up result is done.
Nov 20 21:47:00 media-server sh[5132]: /bin/sh: 1: /usr/lib/plexmediaserver/Plex Media Server: not found
Nov 20 21:47:00 media-server systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=127/n/a
Nov 20 21:47:00 media-server systemd[1]: plexmediaserver.service: Unit entered failed state.
Nov 20 21:47:00 media-server systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Nov 20 21:47:04 media-server sudo[5137]:    david : TTY=pts/7 ; PWD=/home/david/Downloads ; USER=root ; COMMAND=/bin/systemctl status plexmediaserver
Nov 20 21:47:04 media-server sudo[5137]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Nov 20 21:47:05 media-server systemd[1]: Stopped Plex Media Server for Linux.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit plexmediaserver.service has finished shutting down.
Nov 20 21:47:05 media-server systemd[1]: Starting Plex Media Server for Linux...
-- Subject: Unit plexmediaserver.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit plexmediaserver.service has begun starting up.
Nov 20 21:47:05 media-server systemd[1]: Started Plex Media Server for Linux.
-- Subject: Unit plexmediaserver.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit plexmediaserver.service has finished starting up.
-- 
-- The start-up result is done.
Nov 20 21:47:05 media-server sh[5144]: /bin/sh: 1: /usr/lib/plexmediaserver/Plex Media Server: not found
Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Main process exited, code=exited, status=127/n/a
Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Unit entered failed state.
Nov 20 21:47:05 media-server systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Nov 20 21:47:10 media-server sudo[5137]: pam_unix(sudo:session): session closed for user root
Nov 20 21:47:11 media-server systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Nov 20 21:47:11 media-server systemd[1]: Stopped Plex Media Server for Linux.
-- Subject: Unit plexmediaserver.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit plexmediaserver.service has finished shutting down.

My Problem:

Ubuntu doesn't shutdown/reboot and is stuck on line like this:

/dev/sda: clean, xxx/xxx files, xxx/xxx blocks`

and sometimes with several similiar lines and sometimes with "recovering journal" at the top.

At first the problem was that it stucked with

CPU#X stucked for XXs

but I've managed it somehow from the list below :)

What I've done:

1. sudo update && upgrade && dist-upgrade and loaded updates with ubuntu-software-center.
2. sudo purge nvidia* and sudo apt-get install nvidia-361
3. switched to Intel HD card in "Nvidia settings" (nvidia prime).
4. fixed grub with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force
5. (tried apm=power_off and acpi=noirq too).(tried apm=power_off and acpi=noirq too).
6. disabled usb 3.0 legacy mode.
7. disabled swap partition with sudo swapoff /dev/sdaX and commented it's entry in fstab.
8. I changed something in /etc/modules that I've forgotten

My hardware:

MSI GE62 6QD (Laptop);
i5 6300HQ (4 cores);
intel hd530 + Nvidia gtx 960;
16gb RAM DDR4;
Windows 10 UEFI on default 1TB HDD;
SSD Intel 540s via M.2 (UBUNTU UEFI);
Dualboot via bootmenu (F11) yet..

I just didn't update kernel manually, but I can try if you'll help me a little with right way of doing it.

Installation process didn't go easy too. It got stucked on first "preparing" screen with "Ubuntu" logo. Solved with nomodeset in boot params. I've tried hackintosh OSX El Capitan on this M.2 SSD and it worked rather fine (of course not excellent).

I'm very sorry, cause I'm not a guru in kernels/terminal/bootargs/etc, so I tried almost every solution that helped somebody..

Hope for your help. I need my lovely OS working well on my new monster-laptop.

I have one speaker next to my computer which I use mostly as a headphone amplifier. On occasion I need to use it as a loudspeaker. Is it possible to quickly change the audio output from stereo to mono, either system-wide or as a plugin for a media player?

I am using dolphin as my file manager and when I download something via firefox, I right click the download dialog and choose "open folder", I always get nautilus.

Why doesn't firefox open the folder with dolphin? Thanks

Note: I tried adding the tag "dolphin" but because of my low rep I can't create new tags :(