I was setting up a backup program for my newly installed Ubuntu 26.04 when I accidentally deleted all the files (and symlinks) which reside in the root folder of my system. No folders were deleted or changed. I don't have a backup because I haven't set that up yet.

How do I restore those files and links so that the system will boot again?

I can run the demonstration mode of the installation USB to just copy or create what is necessary.

My Kubuntu system can't figure out how much free space is left on my hard drive. There are three sources (as shown in the screenshots), and they all provide different information. I'm inclined to believe that I should have around 190-200 GB of free space, but the installer won't let me install files larger than the claimed 160 GB. Where did the other 40 GB go?

From what I gather, the main feature of Windows "Live File System" is not a Windows thing, but actually a feature of UDF revision 1.50 (1997). It added support for the "Virtual Allocation Table" (VAT), which allowed packet writing; that is, you can sort of treat the CD-R/DVD-R, which are WORM (Write Once, Read Many) as a rewriteable filesystem (not disc, filesystem).

Given this apparent generality, I imagine Linux does support this. However, I only found this, but it seems weird, since I found no udftools service nor the file where it says to be present. And I also suspect pktsetup (of Debian package udftools) has something to do with this, although I do not get its language nor explanation.

So! How do I do this?

I've been trying to get my UB600 Bluetooth dongle to work, however it seems that it's not compatible out of the box. In fact, there's only 1 place with a solution how to get it to work however it seems the explanation on how to do it goes over my head. I've tried using what they gave me in konsole but some things just error and I can't seem to get around that. The fix I've been attempting is this. The issue I'm having is, it detects the Bluetooth dongle, but the computer is then unable to detect any Bluetooth devices at all. The lsusb is exactly as shown on that link as is the journalctl.

Results of lsusb | grep -i 'tp-link':

Bus 001 Device 012: ID 37ad:0600  TP-Link Bluetooth USB Adapter

Results of journalctl:

usb 1-1: new full-speed USB device number 12 using xhci_hcd
usb 1-1: New USB device found, idVendor=37ad, idProduct=0600, bcdDevice= 2.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: TP-Link Bluetooth USB Adapter
usb 1-1: Manufacturer:
usb 1-1: SerialNumber: 18694530DB8B
Bluetooth: MGMT ver 1.23

I ran sudo dmesg | grep -i bluetooth and got this:

server@server-z87hd3:~$ sudo dmesg | grep -i bluetooth
[sudo] password for server: 
[647887.635955] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[647887.709668] Bluetooth: MGMT ver 1.23
[648046.220743] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648046.221733] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648046.222744] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648046.222748] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648046.224331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648046.224378] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648046.376751] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648046.443866] Bluetooth: MGMT ver 1.23
[648062.029928] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648062.105001] Bluetooth: MGMT ver 1.23
[648220.950989] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648220.951983] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648220.952966] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648220.952969] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648220.953197] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648220.953223] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648221.105982] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648221.173128] Bluetooth: MGMT ver 1.23
[648256.225222] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648256.298247] Bluetooth: MGMT ver 1.23
[649742.374342] Bluetooth: MGMT ver 1.23
[682771.713073] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[682771.785356] Bluetooth: MGMT ver 1.23

Is there any chance somebody could explain to me like I'm a 5 year old how to apply that patch, or better yet, create a solution for me? I am running Kubuntu 26.04 on kernel 7.0.0-27-27.

I have recently set up a server on an AWS EC2 instance with Ubuntu 24.04. I am trying to change the configuration to authenticate via password but when I try to log in I get a 'Permission denied, please try again.' error message.

I have done the following:

• PasswordAuthentication yes and KbdInteractiveAuthentication yes
• Created a new user that has been given sudo access.
• Restarted the ssh service with sudo systemctl restart ssh
• Checked the user isn't locked
• Checked AllowUsers isn't set in the config
• Triple checked the password is right (I can su to that user with no problem).
• Permissions are set correctl for ~/.ssh and any files/dir underneath
• Made sure owners/group/permissions are correct for /etc/passwd, /etc/group, /etc/shadow
• Rebooted a couple of times

codename: noble openssh-server: 1:9.6p1-3ubuntu13.16 amd64

I have a Dell Inspirion-16-5625 (Ryzen 5625) laptop and a ADATA Legend 800 SSD. I used it with Xubuntu 22.04 and 24.04 without problems. Now I updated to version 26.04 and I have at almost every cold start a system freeze after some time. Sometimes it switches to the boot screen, sometimes I can change to a console where I see a journald message saying that the file system is read only (trying to write in an endless loop), sometimes just freezes.

After a restart I often have to enter my dmcrypt password twice.

I have also Windows 11 installed which works without errors and after a warm start Xubuntu also works, so I think I can exclude any hardware problems.

I already searched in internet and I found some things:

• The SSD has a wrong implemented advanced power management.
• The graphics driver says DMCUB error.
• Read error in getting the edid of my external monitor (ASUS PA258QV)
• Dracut says the keyboard is in an unknown mode.

I tried everything I found in internet, but it seems that now its nearly at every cold start, before some cold starts worked.

So what I did:

• Update the PC BIOS
• Update the SSD firmware
• I checked the SSD with the ADATA utility in Win11 => no errors
• Set nvme_core.default_ps_max_latency_us=0 (or another value) in grub
• Set amdgpu.dcdebugmask=0x10 in grub
• Set drm.edid_firmware=HDMI-A-1:edid/hdmi.bin in grub
• Disabling the power saving modes of the SSD

For now I have no more idea what I can do. I will attach the dmesg and journal of the last freeze.

I installed Ubuntu 26.04 onto my Dell Precision M4700 laptop. I was seeing some error messages during boot, and some of the googled suggestions were to turn on UEFI in the BIOS of the dell. I turned on Secure UEFI and 26.04 continued to boot, and the error messages went away. However, the problem is that Dell had an issue with the UEFI being buggy with the graphic cards in the Dell M4700, so from that point on, I can't see the bios (or anything) until Linux loads the drivers. The point is, I can no longer interact with the BIOS and have to wait for Linux to load. Well, now I want to reload Ubuntu 26.04 again from bootable USB pen drive, but can't interrupt the bios to do it (or change the boot order in the bios). My question is, since I can fully boot into Linux at this point, is there something I can do with Linux to force it to boot from the USB drive, so that I can reload Ubuntu?

I have an old server, with "mdadm - v3.2.5 - 18th May 2012", on Ubuntu version 12. Before trying to move my 5 disks RAID6 to the new server, I created an image with ddrescue of each disks (3TB per disk).

The new server is Ubuntu 26, with "mdadm - v4.5 - 2025-12-16 - Ubuntu 4.5-5ubuntu1"

On the old server, I can create "loop0-4" devices with losetup. and use the command:

mdadm --create /dev/md123 --assume-clean --level=6 --raid-devices=5 /dev/loop3 /dev/loop2 /dev/loop4 /dev/loop1 /dev/loop0

I can then mount the device and access my data.

I can use mdadm --assemble as well

# mdadm --detail /dev/md123
/dev/md123:
        Version : 1.2
  Creation Time : Tue Jul  7 17:18:35 2026
     Raid Level : raid6
     Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
  Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent

    Update Time : Wed Jul  8 11:15:21 2026
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : cchounas:storagearay  (local to host cchounas)
           UUID : 28d7897a:a42f83bf:200a03b2:ef093da5
         Events : 2

    Number   Major   Minor   RaidDevice State
       0       7        3        0      active sync   /dev/loop3
       1       7        2        1      active sync   /dev/loop2
       2       7        4        2      active sync   /dev/loop4
       3       7        1        3      active sync   /dev/loop1
       4       7        0        4      active sync   /dev/loop0

Everything is fine.

On the new server, I execute the same commands and it does not work.

Two of the disks are removed!

# mdadm --assemble /dev/md123 --uuid=28d7897a:a42f83bf:200a03b2:ef093da5 --verbose --metadata=1.2 /dev/loop3 /dev/loop2 /dev/loop4 /dev/loop1 /dev/loop0
mdadm: looking for devices for /dev/md123
mdadm: /dev/loop3 is identified as a member of /dev/md123, slot 0.
mdadm: /dev/loop2 is identified as a member of /dev/md123, slot 1.
mdadm: /dev/loop4 is identified as a member of /dev/md123, slot 2.
mdadm: /dev/loop1 is identified as a member of /dev/md123, slot 3.
mdadm: /dev/loop0 is identified as a member of /dev/md123, slot 4.
mdadm: added /dev/loop2 to /dev/md123 as 1
mdadm: added /dev/loop4 to /dev/md123 as 2 (possibly out of date)
mdadm: added /dev/loop1 to /dev/md123 as 3
mdadm: added /dev/loop0 to /dev/md123 as 4 (possibly out of date)
mdadm: added /dev/loop3 to /dev/md123 as 0
mdadm: /dev/md123 has been started with 3 drives (out of 5).
root@chounas:~# cat /proc/mdstat
Personalities : [raid4] [raid5] [raid6]
md123 : active raid6 loop3[0] loop1[3] loop2[1]
      8790405120 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/3] [UU_U_]

unused devices: <none>
root@chounas:~# mdadm --detail /dev/md123
/dev/md123:
           Version : 1.2
     Creation Time : Tue Jul  7 17:18:35 2026
        Raid Level : raid6
        Array Size : 8790405120 (8.19 TiB 9.00 TB)
     Used Dev Size : 2930135040 (2.73 TiB 3.00 TB)
      Raid Devices : 5
     Total Devices : 3
       Persistence : Superblock is persistent

       Update Time : Wed Jul  8 11:47:09 2026
             State : clean, degraded
    Active Devices : 3
   Working Devices : 3
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : resync

              Name : cchounas:storagearay
              UUID : 28d7897a:a42f83bf:200a03b2:ef093da5
            Events : 6

    Number   Major   Minor   RaidDevice State
       0       7        3        0      active sync   /dev/loop3
       1       7        2        1      active sync   /dev/loop2
       -       0        0        2      removed
       3       7        1        3      active sync   /dev/loop1
       -       0        0        4      removed

 cat /proc/mdstat
Personalities : [raid4] [raid5] [raid6]
md123 : active raid6 loop3[0] loop1[3] loop2[1]
      8790405120 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/3] [UU_U_]

unused devices: <none>

I get the following message in dmesg for the two removed drives( images)

md: kicking non-fresh loop0 from array!

Those are image files, the files have not been modified by the OS during boot, or anything else.

Why does the newer mdadm does not recognize all the 5 disks/images?

How can I "fresh-up" loop0 and loop4

Again, the same image file works just fine on the old server.

It is peculiar that it removed two disks. Since it is a RAID6, removing two disks is OK. I should be able to recover the data, but it would be risky if ever one disk fails. The five images are spread over 3 disks, two 4TB and one 1 TB drives.

so i've disabled nested virtualization in light of this CVE https://ubuntu.com/security/CVE-2026-53359

Is there a fix? How can I get the fix because I've disabled nested on my proxmox, but I actually kinda need it for my platform.

Thanks <3

Can i install the Nginx 1.30.3 source download from Nginx.org since not seeing the update release for nginx 1.30.3 in the Ubuntu official site. Is it recommended to install the source from Nginx.org in the Production servers?

Not very familiar with Ubuntu, so this may be simple. Basically I want to run an app image from a FAT32 formatted USB stick. Needs to be FAT32 for portability reasons.

The app image is Veracrypt, and I'm trying to make a portable version so I can just plug in the stick and run it. I read that which one can create a 'traveller' version in Windows (done that), in Linux, you need to use the AppImage - which is fully self contained.

So, the stick has on it a file 'test' which is the encrypted volume created in Veracrypt, plus a folder to contain the executable. So, put the AppImage into the folder.

But, try to run it, and I can't, because it doesn't have execute permission - which I cannot set because it is FAT32.

So, created a script veracrypt.sh containing

#! /bin/bash    
sudo VeraCrypt-1.26.29-x86_64.AppImage

Same problem, cannot make it executable.

Cannot see how to get around this, suspect it might not be possible from FAT32? I suppose I could co[y the app image to somewhere on whatever system I am sitting it and make it executable there, but it's a clunky answer.

Basically, what I need to do is create a self contained version of Vercrypt on the USB stick, that gives root permissions to the app. The reason for root is that Veracrypt needs it to mount a volume.

I updated Ubuntu 24.04 when the popup window for the software updater showed up and asked if I wanted to install the updates. I chose to 'install' and then did a restart and when I went to YouTube, videos don't play. I get the list of videos, but when I click on a video, it opens the new page and everything comes up, but no video window and no video. On this other computer YouTube is playing videos. Both have Firefox version 152.0.4 and are running Ubuntu 24.04. I also tried getting the URL from the "Share" icon. I copied it and pasted it into the address line but that didn't work either.

With Xubuntu 24.04 the File Manager sees, in "Browse Network", NFS mount points. With Xubuntu 26.04 NFS mount points are not visible but can be reached by specifying the mount point.

I tried to use the comment=x-gvfs-show but this seemed to have no effect. Using gio to mount the NFS mount point gets the error message "volume doesn't implement mount".

Is the "File Manager" in 24.04 a different implementation than the one in 26.04?

I've already checked:

• systemd-analyze blame
• systemd-analyze critical-chain
• boot logs with journalctl -b

System Information

• Laptop: HP Victus 15-fa2xxx

• Operating System: Ubuntu 22.04 LTS

• Kernel: 6.8.0-124-generic

• Secure Boot: Disabled

Problem Description

The built-in Wi-Fi adapter is not working under Ubuntu. The system detects the PCI device, but no wireless interface is created and no kernel driver is bound to the device.

The same hardware works correctly in Windows.

Hardware Information

Windows identifies the adapter as:

Realtek RTL8852BE-VT Wireless LAN WiFi 6 PCI-E NIC

Hardware ID:

Windows Device manager showing the info

PCI\VEN_10EC&DEV_B520&SUBSYS_88E9103C

PCI Device Detection

Command

lspci -nnk

Relevant Output

03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:b520]
    DeviceName: Realtek Wireless LAN + BT
    Subsystem: Hewlett-Packard Company Device [103c:88e9]

Unlike other devices, there is no:

Kernel driver in use:
Kernel modules:

section for the Wi-Fi device.

Loaded Wi-Fi Driver Modules

Command

lsmod | grep rtw

Output

(no output)

No Realtek rtw89 modules are loaded.

Installed Driver

Command

modinfo rtw89_8852be

Relevant Output

filename:
/lib/modules/6.8.0-124-generic/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852be.ko

modinfo rtw89_8852be lists aliases for PCI IDs 10ec:b852 and 10ec:b85b, but not 10ec:b520:

10ec:b852
10ec:b85b

There is no alias for 10ec:b520.

Kernel Alias Check

Command

grep -i "10EC.*B520" /lib/modules/$(uname -r)/modules.alias

Output

(no output)

Manual Driver Loading

Command

sudo modprobe rtw89_8852be

Result

modprobe: ERROR: could not insert 'rtw89_8852be': Invalid argument

Relevant dmesg Output

rtw_8852b: disagrees about version of symbol ...
rtw_8852b: Unknown symbol ...

DKMS Status

Command

dkms status

Output

(no output)

No third-party DKMS drivers are currently installed.

Troubleshooting Performed

I have already tried the following:

• Disabled Secure Boot.

• Updated Ubuntu packages.

• Booted different 6.8 kernels.

• Installed and later removed the out-of-tree lwfinger/rtw89 driver.

• Reloaded the rtw89 modules.

• Verified the hardware using lspci.

• Checked lsmod, modinfo, modules.alias, dmesg, and journalctl.

None of these steps resolved the issue.

Why this question is different from:

How to solve "No Wi-Fi Adapter Found" error with Realtek RTL8852BE WiFi 6 802.11ax PCIe in Ubuntu 22.04?

I have already reviewed the existing question:

How to solve "No Wi-Fi Adapter Found" error with Realtek RTL8852BE WiFi 6 802.11ax PCIe in Ubuntu 22.04?

However, my issue appears to be different for the following reasons.

Different hardware revision

The linked question concerns the following device:

10ec:b852

My adapter is identified by Windows as:

Realtek RTL8852BE-VT Wireless LAN WiFi 6 PCI-E NIC PCI\VEN_10EC&DEV_B520&SUBSYS_88E9103C

Ubuntu also detects the device as:

03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:b520]

This is a different PCI device ID from the one in the linked question.

Questions

1. Does Ubuntu 22.04 (kernel 6.8) support the RTL8852BE-VT (PCI ID 10ec:b520)?

2. Is this PCI ID supported only in newer Linux kernels?

3. Is there a newer or backported rtw89 driver that supports this device on Ubuntu 22.04?

4. Do my diagnostics indicate a configuration problem, or is this likely a missing driver/kernel support issue?

A few years ago, I created a username and password for my Linux Ubuntu PC. I’ll call the username user1 and the password pass1. A few months ago, my wife created a new username and password (which I’ll call user2 and pass2). She created it while in the administration mode, which I had logged in.

A few days ago, my wife forgot her password, and cannot remember it. In the Grub menu, only user1 appears (user2 does not appear). When I restart the computer, only user2 appears, and when I go to the administration menu, in order to change the password, I need pass2 (which we forgot).

This is what I want: user1 to appear when I start the computer, or (better yet) to be able to change the password for user2. Are either of these two options possible? And please let me know if you need more information: I don't know how to explain the problem well.

I am using Ubuntu 26.04 with the default GNOME desktop.

I want to change the font and font size in the Terminal, but I cannot find the Preferences option. Most tutorials say to open Terminal and go to Preferences, but that option does not exist in my installation.

I tried:

• Checking the Terminal menu (top-right/hamburger menu).
• Right-clicking inside the Terminal window.
• Looking through the application settings.

None of these show a Preferences option.

Questions:

1. Has the Terminal application changed in Ubuntu 26.04?
2. How can I change the Terminal font and font size?
3. If the Preferences menu was removed, what is the new way to configure the Terminal?

If needed, I can provide screenshots of the Terminal window and menu.

I just did a fresh install of Ubuntu Server 26.04LTS, and am seeing loads of broken links already.

Since installing the OS, I have done an apt upgrade, added one additional user, and a static MoTD, so almost nothing really.

Yet, when I run:

sudo find / -xtype l -ls

I get scores (at least) of broken links showing up (I can post a complete list if it would help). If I exclude some paths thus:

find / -xdev -xtype l \
-not -path "/proc/*" \
-not -path "/sys/*" \
-not -path "/run/*" \
-not -path "/dev/*" \
2>/dev/null

it reduces the number of broken links listed to this list, which is still surprising (at least to me!)

/usr/src/linux-headers-7.0.0-27/scripts/kernel-doc
/usr/src/linux-headers-7.0.0-27-generic/rust
/usr/share/locale/it/LC_TIME/coreutils.mo
/usr/share/locale/be/LC_TIME/coreutils.mo
/usr/share/locale/ia/LC_TIME/coreutils.mo
/usr/share/locale/af/LC_TIME/coreutils.mo
/usr/share/locale/el/LC_TIME/coreutils.mo
/usr/share/locale/lt/LC_TIME/coreutils.mo
/usr/share/locale/ka/LC_TIME/coreutils.mo
/usr/share/locale/eo/LC_TIME/coreutils.mo
/usr/share/locale/sv/LC_TIME/coreutils.mo
/usr/share/locale/gl/LC_TIME/coreutils.mo
/usr/share/locale/et/LC_TIME/coreutils.mo
/usr/share/locale/cs/LC_TIME/coreutils.mo
/usr/share/locale/hu/LC_TIME/coreutils.mo
/usr/share/locale/uk/LC_TIME/coreutils.mo
/usr/share/locale/fi/LC_TIME/coreutils.mo
/usr/share/locale/bg/LC_TIME/coreutils.mo
/usr/share/locale/sr/LC_TIME/coreutils.mo
/usr/share/locale/zh_TW/LC_TIME/coreutils.mo
/usr/share/locale/ru/LC_TIME/coreutils.mo
/usr/share/locale/ja/LC_TIME/coreutils.mo
/usr/share/locale/ms/LC_TIME/coreutils.mo
/usr/share/locale/ga/LC_TIME/coreutils.mo
/usr/share/locale/id/LC_TIME/coreutils.mo
/usr/share/locale/ko/LC_TIME/coreutils.mo
/usr/share/locale/sl/LC_TIME/coreutils.mo
/usr/share/locale/pl/LC_TIME/coreutils.mo
/usr/share/locale/hr/LC_TIME/coreutils.mo
/usr/share/locale/vi/LC_TIME/coreutils.mo
/usr/share/locale/lg/LC_TIME/coreutils.mo
/usr/share/locale/da/LC_TIME/coreutils.mo
/usr/share/locale/nl/LC_TIME/coreutils.mo
/usr/share/locale/fr/LC_TIME/coreutils.mo
/usr/share/locale/pt_BR/LC_TIME/coreutils.mo
/usr/share/locale/es/LC_TIME/coreutils.mo
/usr/share/locale/ca/LC_TIME/coreutils.mo
/usr/share/locale/pt/LC_TIME/coreutils.mo
/usr/share/locale/sk/LC_TIME/coreutils.mo
/usr/share/locale/ro/LC_TIME/coreutils.mo
/usr/share/locale/nb/LC_TIME/coreutils.mo
/usr/share/locale/ta/LC_TIME/coreutils.mo
/usr/share/locale/kk/LC_TIME/coreutils.mo
/usr/share/locale/tr/LC_TIME/coreutils.mo
/usr/share/locale/eu/LC_TIME/coreutils.mo
/usr/share/locale/zh_CN/LC_TIME/coreutils.mo
/usr/share/locale/de/LC_TIME/coreutils.mo
/usr/share/man/man1/hashsum.1.gz
/usr/share/doc/libxml2-16/NEWS.gz
/usr/share/doc/xfsprogs/changelog.gz
/usr/share/doc/perl/Changes.gz
/usr/share/doc/python3-wadllib/NEWS.rst.gz

Is it expected that there would be a load of broken links on a fresh install? If not, perhaps something went wrong when I installed, and I should wipe and start from scratch, or perhaps the disk is knackered (although I did run the built-in disk diagnostic from the boot menu, and it found no issues).

Any suggestions welcome, and given I have almost nothing invested, I am also happy to use this for any tests that might be useful to understand what is happening.

I just upgraded my Ubuntu 24.04-4 MATE install to the latest version. I noticed that in Firefox the save dialog box refuses to save a file on the proposed location when hitting [Enter] like it always did. I first blamed Firefox but it is system-wide. Any GTK app has this unwanted behavior. Other PCs, a fully up-to-date Linux Mint 22.3 workstation and a fresh test install of Ubuntu 24.04 MATE on an HP USDT (Ultra Small Desktop) save just fine on [Enter].

But not only that, I also noticed files being overwritten without any warning when clicking Save (or using [Alt]+s). Barring a complete system re-install, how can I fix this?

Since a v151 Firefox supports Webserial natively. For me this is an long awaited function. But I cannot seem to find any documentation on how to get this running with the installed snap version in Ubuntu (26.04 in my case).

What I tried:

The serial port I wanted to try is popping up in the /dev folder as 'ttyACM0'

I read about webserial with Chromium (snap) where you need to connect the raw-usb to snap. But raw-usb seems not to be available for firefox

# sudo snap connect firefox:raw-usb          
error: snap "firefox" has no plug named "raw-usb"

with:

sudo snap connect chromium:raw-usb

everything works as aspected but I prefer firefox

Is the snap package just not ready (yet) or is there anything else I can try?

I’m currently using Ubuntu 24.04 on Acer Aspire Lite AL15G 52 and trying to downgrade to Ubuntu 22.04 by booting from a USB drive, however during the boot process from the USB the system freezes at a black screen with the following boot messages.

[    2.826655] scsi 0:0:0:0: Direct-Access SanDisk SanDisk 3.2 Gen1 DL17 PQ
: 0 ANSI: 6
[    2.827507] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.828378] sd 0:0:0:0: [sda] 244457472 512-byte logical blocks: (125 GB/117 GiB)
[    2.828780] sd 0:0:0:0: [sda] Write Protect is off
[    2.828795] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 00
[    2.829118] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[    2.894887] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    2.894898] GPT:9799523 != 244457471
[    2.894903] GPT:Alternate GPT header not at the end of the disk.
[    2.894907] GPT:9799523 != 244457471
[    2.894911] GPT: Use GNU Parted to correct GPT errors.
[    2.894925]  sda: sda1 sda2 sda3
[    2.895411] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    3.552325] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 1
[    3.554854] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no)
[    3.555281] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/
LNXVIDEO:00/input/input11
[    3.555752] vga_switcheroo: enabled
[    3.557761] fbcon: i915drmfb (fb0) is primary device
[    3.560959] Console: switching to colour frame buffer device 240x67
[    3.572091] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
_

I created the iso image using "dd" with command: sudo dd if=ubuntu.iso of=/dev/sda status=progress bs=10M && sync but i don't think that's the issue here cause i installed Ubuntu 24.04 in the exact same way and boot settings and chose the option to erase disk (uninstall windows 11) and it worked.

Edit 1: I am trying to install ubuntu-22.04.4-desktop-amd64.iso and previously i installed ubuntu-24.04-desktop-amd64.iso without any issues with same boot settings.

Edit 2: Based on @oldfred's comment, here's the output of "gdisk" command:

$ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.10

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 244457472 sectors, 116.6 GiB
Model: SanDisk 3.2 Gen1
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): ABBD44C4-640C-4CEA-ACCB-CA38273F602E
Partition table holds up to 248 entries
Main partition table begins at sector 2 and ends at sector 63
First usable sector is 64, last usable sector is 9799460
Partitions will be aligned on 4-sector boundaries
Total free space is 1 sectors (512 bytes)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64         9788791   4.7 GiB     0700  ISO9660
   2         9788792         9798859   4.9 MiB     EF00  Appended2
   3         9798860         9799459   300.0 KiB   0700  Gap1

Apart from "dd", i also used "etcher" to flash the ISO again and even reflashed the ISO with "dd" again but cleared the partition table with: sudo wipefs --all /dev/sda this time to see if it works & encountered the same error in both cases. I even changed my USB to another one but that also resulted in same error so i assume it has nothing to do with the USB am using.

I have been using chrome on ubuntu for years without problem. Since a while, it complains it is no longer the last version. I honestly don't remember how it was installed to begin with, most likely snap or apt, but neither indicate they can do any update. Everything is up to date. I don't know, maybe it has something to do with the 24.04 update? To be clear, I updated to 24.04 a while ago.

All I have to go on is this menu button:

I don't know where to start. I don't even know how to check how it was installed. I have tried to google this but I get mostly posts from 9 years old. Can anybody give me a few pointers, how to resolve this? Greatly appreciated!

How do I reverse the active/inactive tab colors in files for the default 24.04 ubuntu theme?

The active tab is 'greyed out' while the inactive tabs are 'white'. Dark theme reverses such that active is lighter than inactive, but the rest of dark theme is unusable for me, so that's not a viable alternative.

Possibly related aside: text edit also has grey active/white inactive. Fortunately I could install gedit (46.2) which adds a high visibility orange underline to the active tab and use that instead. Default Gnome terminal (3.52.0 for gnome 46) also includes the orange high visibility underline on tabs which is great.

I have recently set up a server on an AWS EC2 instance with Ubuntu 24.04. I am trying to change the configuration to authenticate via password but when I try to log in I get a 'Permission denied, please try again.' error message.

I have done the following:

• Updated /etc/ssh/sshd_config so: PubkeyAuthentication no, and PasswordAuthentication yes
• Created a new user that has been given sudo access.
• Restarted the ssh service with sudo systemctl restart ssh
• Checked the user isn't locked
• Checked AllowUsers isn't set in the config
• Triple checked the password is right (I can su to that user with no problem).

Here is the output from the attempted connection:

ssh -vvv username@18.xxx.xxx.xxx
OpenSSH_9.6p1, LibreSSL 3.3.6
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug2: resolve_canonicalize: hostname 18.xxx.xxx.xxx is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/Users/localuser/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/Users/localuser/.ssh/known_hosts2'
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to 18.xxx.xxx.xxx [18.xxx.xxx.xxx ] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /Users/localuser/.ssh/id_rsa type 0
debug1: identity file /Users/localuser/.ssh/id_rsa-cert type -1
debug1: identity file /Users/localuser/.ssh/id_ecdsa type -1
debug1: identity file /Users/localuser/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/localuser/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/localuser/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /Users/localuser/.ssh/id_ed25519 type -1
debug1: identity file /Users/localuser/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/localuser/.ssh/id_ed25519_sk type -1
debug1: identity file /Users/localuser/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/localuser/.ssh/id_xmss type -1
debug1: identity file /Users/localuser/.ssh/id_xmss-cert type -1
debug1: identity file /Users/localuser/.ssh/id_dsa type -1
debug1: identity file /Users/localuser/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.6p1 Ubuntu-3ubuntu13
debug1: compat_banner: match: OpenSSH_9.6p1 Ubuntu-3ubuntu13 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 18.xxx.xxx.xxx :22 as 'username'
debug3: record_hostkey: found key type ED25519 in file /Users/localuser/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from 18.xxx.xxx.xxx 
debug1: load_hostkeys: fopen /Users/localuser/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01@openssh.com, using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-s,kex-strict-s-v00@openssh.com
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug3: kex_choose_conf: will use strict KEX ordering
debug1: kex: algorithm: sntrup761x25519-sha512@openssh.com
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:zzSUWOxfnJ9mRowALRTDSqVH+jYFh5CQhMhJVn4j/wY
debug3: record_hostkey: found key type ED25519 in file /Users/localuser/.ssh/known_hosts:1
debug3: load_hostkeys_file: loaded 1 keys from 18.xxx.xxx.xxx 
debug1: load_hostkeys: fopen /Users/localuser/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '18.xxx.xxx.xxx ' is known and matches the ED25519 host key.
debug1: Found key in /Users/localuser/.ssh/known_hosts:1
debug3: send packet: type 21
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: Sending SSH2_MSG_EXT_INFO
debug3: send packet: type 7
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug3: kex_input_ext_info: extension publickey-hostbound@openssh.com
debug1: kex_ext_info_check_ver: publickey-hostbound@openssh.com=<0>
debug3: kex_input_ext_info: extension ping@openssh.com
debug1: kex_ext_info_check_ver: ping@openssh.com=<0>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug3: receive packet: type 51
debug1: Authentications that can continue: 
debug3: start over, passed a different list publickey,keyboard-interactive,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug3: ssh_get_authentication_socket_path: path '/private/tmp/com.apple.launchd.voOEBl7ytW/Listeners'
debug1: get_agent_identities: bound agent to hostkey
debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities
debug1: Will attempt key: /Users/localuser/.ssh/id_rsa RSA SHA256:ZcXd3HoA0S488gtDsGKvVP+p6yyaIyw6kxVmneraJpo
debug1: Will attempt key: /Users/localuser/.ssh/id_ecdsa 
debug1: Will attempt key: /Users/localuser/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /Users/localuser/.ssh/id_ed25519 
debug1: Will attempt key: /Users/localuser/.ssh/id_ed25519_sk 
debug1: Will attempt key: /Users/localuser/.ssh/id_xmss 
debug1: Will attempt key: /Users/localuser/.ssh/id_dsa 
debug2: pubkey_prepare: done
debug1: Offering public key: /Users/localuser/.ssh/id_rsa RSA SHA256:ZcXd3HoA0S488gtDsGKvVP+p6yyaIyw6kxVmneraJpo
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: 
debug1: Trying private key: /Users/localuser/.ssh/id_ecdsa
debug3: no such identity: /Users/localuser/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /Users/localuser/.ssh/id_ecdsa_sk
debug3: no such identity: /Users/localuser/.ssh/id_ecdsa_sk: No such file or directory
debug1: Trying private key: /Users/localuser/.ssh/id_ed25519
debug3: no such identity: /Users/localuser/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /Users/localuser/.ssh/id_ed25519_sk
debug3: no such identity: /Users/localuser/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /Users/localuser/.ssh/id_xmss
debug3: no such identity: /Users/localuser/.ssh/id_xmss: No such file or directory
debug1: Trying private key: /Users/localuser/.ssh/id_dsa
debug3: no such identity: /Users/localuser/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug3: send packet: type 50
debug2: we sent a keyboard-interactive packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: 
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: 
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
username@18.xxx.xxx.xxx 's password: 
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: 
Permission denied, please try again.

I can't any other possible reason it should not be working. Any guideance would be much appreciated.

Thanks

i am trying to create a partition but am unable due to error:

I see that Ubuntu server after the installation comes as default with NetPlan with a DHCP configuration (at least in Ubuntu 22.04 focal fossa).

Some users don't want NetPlan and just want NetworkManager, for example to use nmcli, nmtui, or import VPN configurations etc. and so after the installation I think it's frequent to migrate to NetworkManager.

At the moment this is my procedure to migrate from NetPlan to NetworkManager after a clean installation.

Create this file:

/etc/netplan/01-er-netplan-fix.yaml

With this content:

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
# Set and change netplan renderer to NetworkManager GUI tool
network:
  version: 2
  renderer: NetworkManager

Then run these commands:

# install Network Manager
sudo apt install network-manager

# disable NetPlan
mv /etc/netplan/00-installer-config.yaml /etc/netplan/00-installer-config.yaml.bak

# reload NetPlan
netplan apply

# I'm not proud of this but I reboot to apply everything now
reboot

Problem: when I reboot, the server obviously disconnects, but also it never renews its IP via DHCP.

As workaround, I open a physical terminal on the server, I run dhclient, and then I continue with nmtui adding a simple Ethernet configuration with DHCP, and everything is good again.

So my question is: how to migrate from NetPlan to NetworkManager? Possibly automatically renewing its IP? Possibly without any disconnection at all? so your SSH connection is not interrupted.

Feel free to suggest as answer to prefill at least a valid NetworkManager configuration for a valid DHCP after the reboot but I still don't understand if I can also avoid the reboot at all and keep a working SSH connection to do the whole migration process.

Thank you for your thoughts! Maybe this question is stupid but I don't know NetPlan, since I usually use Debian and I don't have these problems.

Hello I have a dualboot system with Ubuntu 20.04 and Windows 10 and the time of installing Ubuntu 20.04 I disabled fast startup in Windows to get rid of possible errors. But now I want to turn that feature ON because of slow Boot,slow shutdown and restart. So by some finding on Internet , I came to know that turning on that Windows feature ON in dualboot can cause data loss. So I do I enable that feature On without any data loss?

I can read and write Windows drive, did I have to change it to read only? and if so then how can I do that with GUI because terminal commands are confusing and wrong command can mess everything. Thankyou.

I'm trying to enable hibernation on my laptop, and discovered that my problems could have something to do with my Nvidia drivers. So I found this fine document on help.ubuntu.com which tells me to change some settings in /etc/X11/xorg.conf. But it's empty! So what do I do now?

I have three ssd's (ssd0, ssd1, ssd2). ssd0 and ssd1 have Ubuntu 18.04 installed on them via this procedure in the Ubuntu installer:

Erase disk and install Ubuntu

• (checked) Encrypt the new Ubuntu installation for security
• (checked) Use LVM with the new Ubuntu installation

That means I have full disk encryption, LVM and grub2 on ssd0 and ssd1 like this (output from lsbulk):

ssd0:

sdb                       8:16   0 447,1G  0 disk  
├─sdb1                    8:17   0   512M  0 part  /boot/efi
├─sdb2                    8:18   0   732M  0 part  /boot
└─sdb3                    8:19   0 445,9G  0 part  
  └─sda3_crypt          253:0    0 445,9G  0 crypt 
    ├─ubuntu--vg-root   253:1    0   445G  0 lvm   /
    └─ubuntu--vg-swap_1 253:2    0   976M  0 lvm   [SWAP]

ssd1:

sdc                       8:32   0 447,1G  0 disk  
├─sdc1                    8:33   0   512M  0 part  /boot/efi
├─sdc2                    8:34   0   732M  0 part  /boot
└─sdc3                    8:35   0 445,9G  0 part  
  └─sda3_crypt          253:0    0 445,9G  0 crypt 
    ├─ubuntu--vg-root   253:1    0   445G  0 lvm   /
    └─ubuntu--vg-swap_1 253:2    0   976M  0 lvm   [SWAP]

ssd2 has win10 installed on it.

Both grub2 bootloader (grub2 on ssd0 and grub2 on ssd1) recognize win10, but both grub2 bootloader do not recogize the other Ubuntu installation.

Why is that and how can I make it work?

The desired configuration would be that I still have a seperate grub2 on ssd0 and ssd1 and both should recognize the other Ubuntu (as well as win10) such that I can remove ssd0 or ssd1 and still have a a bootloader for the Ubuntu/win10 dualboot. When ssd0, ssd1 and ssd2 are connected, then I simply set in the BIOS which bootloader to use, wheter the bootloader from ssd0 or the one on ssd1.

Some probably necessary information:

• UEFI BIOS
• Partition scheme is GPT

I am trying to install Single node configuration, I succeeded to certain point like downloading and unzipping the tar and editing all the configuration files, but faced problems when formatting the namenode.

The errors are:

14/07/14 02:56:40 WARN fs.FileUtil: Failed to delete file or dir [/home/renu123/yarn/yarn_data/hdfs/namenode/current/seen_txid]: it still exists.
14/07/14 02:56:40 WARN fs.FileUtil: Failed to delete file or dir [/home/renu123/yarn/yarn_data/hdfs/namenode/current/VERSION]: it still exists.
14/07/14 02:56:40 WARN fs.FileUtil: Failed to delete file or dir [/home/renu123/yarn/yarn_data/hdfs/namenode/current/fsimage_0000000000000000000]: it still exists.
14/07/14 02:56:40 WARN fs.FileUtil: Failed to delete file or dir [/home/renu123/yarn/yarn_data/hdfs/namenode/current/fsimage_0000000000000000000.md5]: it still exists.
14/07/14 02:56:40 FATAL namenode.NameNode: Exception in namenode join
java.io.IOException: Cannot remove current directory: /home/renu123/yarn/yarn_data/hdfs/namenode/current
    at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:299)
    at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:523)
    at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:544)
    at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:147)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:837)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1213)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
14/07/14 02:56:40 INFO util.ExitUtil: Exiting with status 1
14/07/14 02:56:40 INFO namenode.NameNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at ubuntu/127.0.1.1
************************************************************/

After searching on google I formatted namenode by switching to root account as below:

root@ubuntu:~/yarn/yarn_data/hdfs/namenode# hdfs namenode -format
Re-format filesystem in Storage Directory /home/renu123/yarn/yarn_data/hdfs/namenode ? (Y or N) Y
14/07/14 02:59:30 INFO common.Storage: Storage directory /home/renu123/yarn/yarn_data/hdfs/namenode has been successfully formatted.
14/07/14 02:59:30 INFO namenode.FSImage: Saving image file /home/renu123/yarn/yarn_data/hdfs/namenode/current/fsimage.ckpt_0000000000000000000 using no compression
14/07/14 02:59:30 INFO namenode.FSImage: Image file /home/renu123/yarn/yarn_data/hdfs/namenode/current/fsimage.ckpt_0000000000000000000 of size 196 bytes saved in 0 seconds.
14/07/14 02:59:30 INFO namenode.NNStorageRetentionManager: Going to retain 1 images with txid >= 0
14/07/14 02:59:30 INFO util.ExitUtil: Exiting with status 0
14/07/14 02:59:30 INFO namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at ubuntu/127.0.1.1
************************************************************/

Even after formatting still I can see the directories in hdfs/namenode folder i.e current

Assuming the namenode is formatted I proceeded further and tried to start namenode using the command start-dfs.sh, but wasn't able to.

This is the log take out from usr/local/hadoop/logs:

2014-07-14 02:49:10,478 WARN org.apache.hadoop.hdfs.server.common.Storage: Cannot access storage directory /home/renu123/yarn/yarn_data/hdfs/namenode
2014-07-14 02:49:10,484 INFO org.mortbay.log: Stopped SelectChannelConnector@0.0.0.0:50070
2014-07-14 02:49:10,585 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Stopping NameNode metrics system...
2014-07-14 02:49:10,585 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system stopped.
2014-07-14 02:49:10,586 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system shutdown complete.
2014-07-14 02:49:10,587 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /home/renu123/yarn/yarn_data/hdfs/namenode is in an inconsistent state: storage directory does not exist or is not accessible.
    at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:292)
    at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:200)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:787)
    at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:568)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:443)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:491)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:684)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:669)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1254)
    at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1320)
2014-07-14 02:49:10,590 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1
2014-07-14 02:49:10,602 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG: 

Help me find the solution to this.

My configuration files are

core-site.xml

<configuration>
<property>
   <name>fs.default.name</name>

   <value>hdfs://localhost:9000</value>
</property>
</configuration>

yarn-ste.xml

<configuration>
<!-- Site specific YARN configuration properties -->
<property>
   <name>yarn.nodemanager.aux-services</name>

   <value>mapreduce_shuffle</value>
</property>
<property>
   <name>yarn.nodemanager.aux-services.mapreduce.shuffle.class</name>

   <value>org.apache.hadoop.mapred.ShuffleHandler</value>
</property>
</configuration>

mapred-site.xml

<configuration>
<property>
   <name>mapreduce.framework.name</name>

   <value>yarn</value>
</property>
</configuration>

hdfs-site.xml

<configuration>
<property>
   <name>dfs.replication</name>

   <value>1</value>
 </property>
 <property>
   <name>dfs.namenode.name.dir</name>

   <value>file:/home/renu123/yarn/yarn_data/hdfs/namenode</value>
 </property>
 <property>
   <name>dfs.datanode.data.dir</name>

   <value>file:/home/renu123/yarn/yarn_data/hdfs/datanode</value>
 </property>
</configuration>