I am using a Seagate 16tb drive and when I create partition on /dev/sda I get the foll

I am logged in as pi (admin) using cockpit <div class="snippet-clipboard-conte

Error mounting system; operation not permitted,about retronas/retronas

Comments (15)

danmons commented on May 19, 2024 1

When you install fresh, please ensure you are using RPiOS 64bit. Comments on the RPi forums are that very large disks require a 64bit kernel to access large file systems.

The "retrosmb" name is broadcast by Samba's nmbd service (i.e.: what Microsoft calls "WINS"). This should be updated on your client side dynamically. If not, it may be to do with if you've saved passwords for network shares. See this guide on Microsoft's site on how to delete cached/saved password entries:

https://answers.microsoft.com/en-us/windows/forum/all/how-do-i-delete-saved-passwords-from-windows-10/4772c5ca-115a-4b3c-b3b7-ced54bd1e800

from retronas.

birdybro commented on May 19, 2024

Can you hook up the drive to another computer and format it, and then try again?

from retronas.

rogersta99 commented on May 19, 2024

Yea I am currently formatting it to ext4 using mini partition wizard. I will report back after it is done. When I formatted it in retro nas it was almost instantaneous so maybe retro nas is not actually formatting it?

from retronas.

birdybro commented on May 19, 2024

RetroNAS might just be wiping out the partitions, remaking them, and doing a quick format. My theory was more that there could be a proprietary nature to the stock partitions.

from retronas.

rogersta99 commented on May 19, 2024

So I am still getting the same error msg when I try to mount the hd after formatting to ext4 using the mini partition tool.

from retronas.

rogersta99 commented on May 19, 2024

I got the seagate 16tb drive because I was having an issue get the 18tb wb elements drive I had to work. I did get the wb drive to work but only by formatting it to exfat in the mini partition tool. I mounted it to the retronas and everything seemed to be working fine. Now after messing with the wb drive I am gettting the same error when I try to mount it to retronas.

from retronas.

sairuk commented on May 19, 2024

Can you add the commands you are running, console output or screenshot are fine

Which user are you operating as during mount?
What tool are you using to mount the drive cli/cockpit/gui?
Dump your /etc/fstab here
run id $(whoami)
run ls -la /dev/sda*

does your fstab have an old 18tb drive entry?

from retronas.

rogersta99 commented on May 19, 2024

I am logged in as pi (admin)
using cockpit

pi@RetroNAS:~ $ id $(whoami)
uid=1000(pi) gid=1000(pi) groups=1000(pi),4(adm),20(dialout),24(cdrom),27(sudo),29(audio),44(video),46(plugdev),60(games),100(users),105(input),107(render),109(netdev),999(spi),998(i2c),997(gpio)

pi@RetroNAS:~ $ ls -la /dev/sda*
brw-rw---- 1 root disk 8, 0 Feb 18 23:26 /dev/sda
brw-rw---- 1 root disk 8, 1 Feb 18 23:26 /dev/sda1

February 18, 2022
6:29 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
6:29 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
4
6:27 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
6:27 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
4
6:26 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:26 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
6:22 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
6:21 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
7
6:21 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
6:06 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:06 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
5:19 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
5:19 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
3
2:12 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:12 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
3
2:11 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:11 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
3
2:11 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
2:11 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
2:07 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:07 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
3
2:07 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:07 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
2:06 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:06 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
2:03 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:03 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
2:02 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:02 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2:01 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2:01 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
4
2:01 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2
2:01 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
1:58 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
1:58 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
1:58 PM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
1:58 PM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
10:50 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:50 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
10:33 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:33 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
10:32 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:32 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
10:29 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:29 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
10:25 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:25 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
10:24 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
10:24 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:58 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:58 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:57 AM
<error> [1645192646.0642] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:57 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:57 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:57 AM
<error> [1645192636.0441] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:57 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:57 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:57 AM
<error> [1645192626.0541] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:57 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:57 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:56 AM
<error> [1645192616.0442] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:56 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:56 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:56 AM
<error> [1645192606.0439] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:56 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:56 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:56 AM
Failed to set privacy: Rejected (0x0b)
bluetoothd
8:56 AM
sap-server: Operation not permitted (1)
bluetoothd
8:56 AM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
8:56 AM
<error> [1645192580.9164] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:56 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:56 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:56 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:56 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
Reboot
8:55 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:55 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
2
8:55 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
2
8:55 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:55 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:55 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:54 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:54 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:54 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:54 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:52 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:52 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:49 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:49 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:48 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:48 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:46 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:46 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:45 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:45 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:45 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:45 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
8:44 AM
/usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
systemd
8:44 AM
Failed to create unit file /run/systemd/generator/storage.mount, as it already exists. Duplicate entry in /etc/fstab?
systemd-fstab-generator
February 13, 2022
7:25 PM
Failed to start Discard unused blocks on filesystems from /etc/fstab.
systemd
February 11, 2022
9:47 AM
exFAT-fs (sda1): bogus allocation bitmap size(need : 17165777, cur : 17165778)
kernel
9:24 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
9:24 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
February 8, 2022
10:17 AM
exFAT-fs (sda1): bogus allocation bitmap size(need : 17165777, cur : 17165778)
kernel
10:17 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
10:17 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
10:10 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
10:10 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
10:02 AM
EXT4-fs (sda1): filesystem too large to mount safely on this system
kernel
4
10:01 AM
exFAT-fs (sda1): bogus allocation bitmap size(need : 17165777, cur : 17165778)
kernel
9:57 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
9:57 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
9:49 AM
<error> [1644331772.3736] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:49 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:49 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:49 AM
<error> [1644331761.4431] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:49 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:49 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:49 AM
<error> [1644331750.4031] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:49 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:49 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:48 AM
<error> [1644331739.4425] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:48 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:48 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:48 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
9:48 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
9:48 AM
<error> [1644331728.4322] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:48 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:48 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:48 AM
Failed to set privacy: Rejected (0x0b)
bluetoothd
9:48 AM
sap-server: Operation not permitted (1)
bluetoothd
9:48 AM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
9:45 AM
<error> [1644331536.8722] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:45 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:45 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
Reboot
9:44 AM
<error> [1644331485.4158] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:44 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:44 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:44 AM
<error> [1644331475.3957] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:44 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:44 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:44 AM
<error> [1644331464.4657] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:44 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:44 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:44 AM
<error> [1644331454.3953] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:44 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:44 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:44 AM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
9:44 AM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
9:44 AM
<error> [1644331443.4650] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:44 AM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:44 AM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
9:43 AM
Failed to set privacy: Rejected (0x0b)
bluetoothd
9:43 AM
sap-server: Operation not permitted (1)
bluetoothd
9:43 AM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
February 7, 2022
8:56 PM
<error> [1644285367.6777] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:56 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:56 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
Reboot
8:40 PM
<error> [1644284412.3730] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:40 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:40 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:40 PM
<error> [1644284401.4039] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:40 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:40 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:39 PM
<error> [1644284390.4220] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:39 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:39 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:39 PM
<error> [1644284379.5921] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:39 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:39 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:39 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:39 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
8:39 PM
<error> [1644284353.9512] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:39 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:39 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:39 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
8:39 PM
sap-server: Operation not permitted (1)
bluetoothd
8:39 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
8:39 PM
<error> [1644284343.0923] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:39 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:39 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
Reboot
8:37 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:37 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
8:19 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:19 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
6:22 PM
EXT4-fs (sda): filesystem too large to mount safely on this system
kernel
2
6:20 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:20 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
6:17 PM
EXT4-fs (sda1): filesystem too large to mount safely on this system
kernel
6:16 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:16 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
6:12 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:12 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
6:07 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
6:07 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
5:47 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
5:47 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
5:30 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
5:30 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
5:29 PM
<error> [1644272992.8439] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:29 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:29 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:29 PM
<error> [1644272982.8039] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:29 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:29 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:29 PM
<error> [1644272971.8239] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:29 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:29 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:29 PM
<error> [1644272961.8039] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:29 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:29 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
February 6, 2022
7:38 PM
<error> [1644194319.1651] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
7:38 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
7:38 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
7:38 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
7:38 PM
sap-server: Operation not permitted (1)
bluetoothd
7:38 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
7:38 PM
<error> [1644194308.4642] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
7:38 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
7:38 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
Reboot
5:23 PM
<error> [1644186190.8465] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:23 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:23 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:23 PM
<error> [1644186180.8565] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:23 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:23 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:22 PM
<error> [1644186169.8760] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:22 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:22 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:22 PM
<error> [1644186159.8462] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:22 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:22 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:22 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
5:22 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
5:22 PM
<error> [1644186148.8661] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
5:22 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
5:22 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
5:22 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
5:22 PM
sap-server: Operation not permitted (1)
bluetoothd
5:22 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
February 2, 2022
9:24 PM
<error> [1643855060.5703] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
9:24 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
9:24 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
Reboot
8:38 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:38 PM
sd 0:0:0:0: [sda] Asking for cache data failed
kernel
8:29 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:29 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
8:28 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:28 PM
sd 0:0:0:0: [sda] No Caching mode page found
kernel
8:27 PM
sd 0:0:0:0: tag#0 timing out command, waited 180s
kernel
8:24 PM
sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel
8:24 PM
sd 0:0:0:0: [sda] Asking for cache data failed
kernel
8:17 PM
<error> [1643851034.9973] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:17 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:17 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:17 PM
<error> [1643851023.9873] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:17 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:17 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:16 PM
<error> [1643851013.0073] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:16 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:16 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:16 PM
<error> [1643851001.9775] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:16 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:16 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:16 PM
<error> [1643850991.0672] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:16 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:16 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
8:16 PM
eth0: DHCP lease expired
dhcpcd
8:16 PM
<error> [1643850980.0664] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
NetworkManager
8:16 PM
Failed to initialize control interface '/run/wpa_supplicant'. You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again.
wpa_supplicant
8:16 PM
nl80211: kernel reports: Match already configured
wpa_supplicant
23
7:03 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
7:03 PM
sap-server: Operation not permitted (1)
bluetoothd
7:03 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
7:03 PM
dhcpcd_prestartinterface: wlan0: Operation not possible due to RF-kill
dhcpcd
Reboot
7:03 PM
script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: Terminated
dhcpcd
6:20 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
6:20 PM
sap-server: Operation not permitted (1)
bluetoothd
6:20 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
6:20 PM
dhcpcd_prestartinterface: wlan0: Operation not possible due to RF-kill
dhcpcd
January 27, 2022
Reboot
9:24 PM
timed out
dhcpcd
9:24 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
9:24 PM
sap-server: Operation not permitted (1)
bluetoothd
9:24 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
9:23 PM
dhcpcd_prestartinterface: wlan0: Operation not possible due to RF-kill
dhcpcd
Reboot
9:23 PM
script_runreason: /lib/dhcpcd/dhcpcd-run-hooks: Terminated
dhcpcd
Reboot
8:23 PM
Failed to start Configure Bluetooth Modems connected by UART.
systemd
Reboot
8:23 PM
timed out
dhcpcd
Reboot
8:23 PM
timed out
dhcpcd
8:23 PM
dhcpcd_prestartinterface: wlan0: Operation not possible due to RF-kill
dhcpcd
Reboot
8:23 PM
Failed to set privacy: Rejected (0x0b)
bluetoothd
8:23 PM
sap-server: Operation not permitted (1)
bluetoothd
8:23 PM
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
bluetoothd
8:22 PM
dhcpcd_prestartint

edit (mod): added code tags for readability

from retronas.

rogersta99 commented on May 19, 2024

I also just attempted to mount a 8 gb thumb drive and am getting the same error.

from retronas.

danmons commented on May 19, 2024

I think (gut feel, at this point) there might be two issues here.

This is one:

EXT4-fs (sda1): filesystem too large to mount safely on this system

ext4 can handle 1EB (1M TB), however I wonder if the RPi itself has upper limits? I've seen two other cases of 16-18TB drives causing problems (both WD brand).

I solved the previous user's problem by taking them through the process of putting a BtrFS file system on the raw device (/dev/sda, and not inside a GPT partition /dev/sda1, which you can do on a Linux non-boot device). That then gave zero errors on boot time mount and enabled the drive to work as expected.

Glaring downside is that there's no simple way to do this in Cockpit. It's all CLI driven, and requires familiarity with Linux devices so that the wrong drive isn't accidentally deleted.

I'm going to turn that guide into a wiki article and eventually video, but it will absolutely have to be covered in warnings - if people do it on an RPi vs an x86 machine, the devices will be very different, and blind copy/paste can be dangerous.

Issue 2:

I also just attempted to mount a 8 gb thumb drive and am getting the same error.

I think now there are lines in /etc/fstab which are going to interfere with trying to use a different device. Again, I saw this with another user - Cockpit "errors" on trying to add a drive, but it's already written the /etc/fstab entry which is now set at boot time.

If possible, using the Cockpit file browser to navigate to the file /etc/fstab, find the offending line that mounts the external drive (it'll be down the bottom, and will list your custom mount point like /data/retronas or /storage or wherever you defined), and simply putting a # at the beginning of the line to tell the system to ignore it will make using a smaller drive work again. There may be multiples of these depending on how many times you've tried that, so you may need to do this for more than one line.

from retronas.

rogersta99 commented on May 19, 2024

Maybe I should start over rewrite the pi sd card again as I have tried mounting multiple drives, multiple times. Would like to have the bigger hd so If you could walk me through the process of getting one of these drives to work by installing a file system outside the GPT partition that would be great. What is the biggest size hd you think would work based on your current config?

from retronas.

rogersta99 commented on May 19, 2024

I performed a fresh install of retronas with the most recent builds and was able to partition and mount the seagate 16tb hd. I am currently in the process of xfering my mister data from the wb 18tb drive. I am thinking I might try another fresh sd card install to see if the 18 tb drive will now work. Also, how do you remove the old "retrosmb" network label. It is stuck on trying to access the original setup and I cant seem to delete it. I can only access the new setup by typing in the physical ip address.

from retronas.

sairuk commented on May 19, 2024

@rogersta99 how did your reinstall go?

from retronas.

rogersta99 commented on May 19, 2024

@rogersta99 how did your reinstall go?

Hey buddy. I am still running the seagate 16tb with the rasbpi lite so image. Everything is running great there.
I have been out of town and have not messed with the new install for the wb 18tb. If I use a new sd card with the standard rasbpi image on the same pi4 and to try and mount the 18tb drive will there be any issue swapping back to original sd card with thd lite version in case things don't work?

from retronas.

sairuk commented on May 19, 2024

There should be no issue at all, they will be completely independent of each other.

If this is something you are not too concerned about at this stage (i.e. the 16TB is fine for now) we will probably go ahead and close this issue for now.

We can revisit if/when you have time to get back to this providing there is still an issue.

We have updated our recommendations that people use the 64bit images if they want to run large storage, so if you apply those recommendations on reinstall later on and still have issues we'd be glad to hear from you again to try and sort it out.

from retronas.

Error mounting system; operation not permitted about retronas HOT 15 CLOSED

Comments (15)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent