[FAILED] Failed to start Samba NMB Daemon

Hello again,

So, during my last issue, the last line of my inxi showed Samba/nmb as a failed unit. As I was working on the problem I was having with btrfs and baloo, I wasn't concerned about the Failed unit Samba/nmb.

Well, now I'm having a different problem and I have not found a solution and it relates to the failed Samba/nmb unit. After making adjustments to btrfs and balooctrl, on my next reboot, the boot process hung. The last line when it hung up was:

[FAILED] Failed to start Samba NMB Daemon...

I had no choice but to do a ^AltD reset. The same thing happened again. I reset again and booted from a snapshot from earlier in the day on 03/05 and the system booted properly. However, after updating again and rebooting the boot process hung again exactly as before.

I have been trying to get vncserver working, but unsuccessfully so far, which entails some settings involving Samba and NMB in Network Drives as well as some settings done manually with vncserver (according to the Arch Wiki). After the reboot from the previous snapshot, those settings, as well as the adjustments I made to btrfs qgroups, quotas, and balooctl, were all undone and set back to the previous settings (defaults). I have since deselected everything I can find that has anything to do with Samba and NMB and nothing is showing under enabled services. However, I am still getting hung up at the same place in the boot process. The lines right before the line above in the boot process refers to 'Terminate Plymouth Screen' . I tried removing Plymouth from /etc/mkinitcpio.conf, thinking maybe Plymouth was to blame, but it had no effect.

You will notice that my current inxi does not show the failed Samba unit. I suppose that's because I have deselected and disabled everything I could find that relates to Samba. However, I still get the same message and hang on reboot attempts.

systemctl list-unit-files --all | grep -i -e smb -e samba

shows both Samba.service and smb.service as disabled.

Someone suggested that maybe I had a hdd failing, but I get no errors from smartctl on the system drive. As well, since I can reboot from a previous snapshot with no problems, it doesn't seem like a hardware issue to me. i have rebooted this way half a dozen times this evening as I have tried the various things I have detailed above. I am currently typing on the computer, having booted from the same snapshot. The system is updated as of a few minutes ago. I know that if I try to reboot it will hang with the same error message as above.

Here's what I think may be the pertinent portion of the previous boot (journactl -b -1)

Mar 06 19:06:48 Workbench kernel: zram: Added device: zram0
Mar 06 19:06:48 Workbench systemd[248]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.
Mar 06 19:06:48 Workbench systemd[1]: Queued start job for default target Graphical Interface.
Mar 06 19:06:48 Workbench systemd[1]: Created slice Virtual Machine and Container Slice.
Mar 06 19:06:48 Workbench systemd[1]: Created slice Slice /system/getty.
Mar 06 19:06:48 Workbench systemd[1]: Created slice Slice /system/modprobe.
Mar 06 19:06:48 Workbench systemd[1]: Created slice Slice /system/systemd-fsck.
Mar 06 19:06:48 Workbench systemd[1]: Created slice Slice /system/systemd-zram-setup.
Mar 06 19:06:48 Workbench systemd[1]: Created slice User and Session Slice.
Mar 06 19:06:48 Workbench systemd[1]: grub-btrfs.path: Bound to unit run-timeshift-backup.mount, but unit isn't active.
Mar 06 19:06:48 Workbench systemd[1]: Dependency failed for Monitors for new timeshift snapshots.
Mar 06 19:06:48 Workbench systemd[1]: grub-btrfs.path: Job grub-btrfs.path/start failed with result 'dependency'.

Any help would be appreciated.

System:
  Kernel: 5.15.26-1-lts x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/timeshift-btrfs/snapshots/2022-03-05_22-38-50/@/boot/vmlinuz-linux-lts
    root=UUID=6cafe1ae-53e0-4003-8e56-0566259c4051 loglevel=3 quiet
    rootflags=defaults,noatime,space_cache,noautodefrag,compress=zstd,subvol=timeshift-btrfs/snapshots/2022-03-05_22-38-50/@
  Desktop: KDE Plasma 5.24.2 tk: Qt 5.15.3 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: H97M-E v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2702 date: 03/28/2016
CPU:
  Info: model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell family: 6
    model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 3482 high: 3493 min/max: 800/3900 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 3493 2: 3452 3: 3493
    4: 3492 bogomips: 27937
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
    IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel ports: active: HDMI-A-2
    empty: HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
  Device-2: Realtek RTL2838 DVB-T type: USB driver: N/A bus-ID: 3-2.2:4
    chip-ID: 0bda:2838 class-ID: 0000 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3")
    s-diag: 484mm (19.1")
  Monitor-1: HDMI2 mapped: HDMI-A-2 model: LCD-TV serial: <filter>
    built: 2007 res: 1600x900 hz: 60 dpi: 58 gamma: 1.2
    size: 700x390mm (27.6x15.4") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 1280x720 min: 720x400
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
    v: 4.5 Mesa 21.3.7 compat-v: 3.0 direct render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 9 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.26-1-lts running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.48 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK AM1I-A driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb
    bus-ID: 3-10:6 chip-ID: 148f:5572 class-ID: 0000 serial: <filter>
  IF: wlp0s20u10 state: up mac: <filter>
Drives:
  Local Storage: total: 4.55 TiB used: 1.37 TiB (30.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD5000AACS-00ZUB0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1B01
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD40EFRX-68WT0N0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD5000LPVX-80V0TT0 size: 465.76 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: GPT
Partition:
  ID-1: / raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.37 TiB (33.5%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%)
    used: 546 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.37 TiB (33.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.37 TiB (33.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.37 TiB (33.5%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.32 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 206 Uptime: 34m wakeups: 0 Memory: 15.32 GiB
  used: 2.29 GiB (14.9%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1761 lib: 410 Shell: fish
  v: 3.3.1 default: Bash v: 5.1.16 running-in: alacritty inxi: 3.3.13
Garuda (2.5.5-1):
  System install date:     2021-03-08
  Last full system update: 2022-03-06
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Timeshift
  Failed units:

Have you restored this snapshot from timshift GUI (and then rebooted, before anything else, like disabling smb and nmb services, your btrfs/baloo adjutments, and finally update)?
The boot_image above makes me think that you're still booted off a snapshot.

3 Likes

Yes, I am still booted off a snapshot. I have tried to restore from several snapshots using the timeshift gui, but upon restart experience the same failure on boot, so the restored values cannot take effect.

Well, this morning I tried a snapshot I thought I had tried before and the computer is now booting up again. It is booting with Snapshot and btrfs Assistant running, but it's booting without the error.

The last thing I did last night before I went to bed (booted into the snapshot in the inxi I posted) was to go back over all the btrfs and baloo settings I changed pursuant to the last thread (After update today (01 March 22) BTFRS and baloo_file_extractor again running amok) and reset them all. I also re-enabled samba.service, smb.service, and nmb.service. I tried a reboot and had the same error. This morning I tried again and had the same error. I then booted back into the previous snapshot, updated, then tried a couple more snapshots, both of which I thought I had already tried, and voila! The first one failed, but the second one I tried worked!

Dangit! spoke too soon. I just ran inxi again...as root this time...and see that I am apparently booting into the snapshot of a snapshot. Even after updates it is still booting into that snapshot...which is why it is booting up. Still showing smb, samba, and nmb as failed units.

System:
Kernel: 5.16.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/timeshift-btrfs/snapshots/2022-03-05_22-38-50/@/boot/vmlinuz-linux-zen
root=UUID=6cafe1ae-53e0-4003-8e56-0566259c4051 rw
rootflags=subvol=timeshift-btrfs/snapshots/2022-03-05_22-38-50/@
loglevel=3 quiet
Console: pty pts/2 wm: kwin_x11 DM: SDDM Distro: Garuda Linux
base: Arch Linux
Machine:
Type: Desktop System: ASUS product: All Series v: N/A serial: N/A
Mobo: ASUSTeK model: H97M-E v: Rev X.0x serial:
UEFI: American Megatrends v: 2702 date: 03/28/2016
CPU:
Info: model: Intel Core i5-4690 socket: BGA1155 (1150) note: check bits: 64
type: MCP arch: Haswell family: 6 model-id: 0x3C (60) stepping: 3
microcode: 0x28
Topology: cpus: 1x cores: 4 smt: cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 3492 high: 3493 min/max: 800/3900 base/boost: 3507/3900
scaling: driver: intel_cpufreq governor: performance volts: 1.2 V
ext-clock: 100 MHz cores: 1: 3492 2: 3492 3: 3492 4: 3493 bogomips: 27935
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: ASUSTeK driver: i915 v: kernel ports: active: HDMI-A-2
empty: HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
Device-2: Realtek RTL2838 DVB-T type: USB driver: N/A bus-ID: 3-2.2:4
chip-ID: 0bda:2838 class-ID: 0000 serial:
Display: server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3")
s-diag: 484mm (19.1")
Monitor-1: HDMI2 mapped: HDMI-A-2 model: LCD-TV serial:
built: 2007 res: 1600x900 hz: 60 dpi: 58 gamma: 1.2
size: 700x390mm (27.6x15.4") diag: 801mm (31.5") ratio: 16:9 modes:
max: 1280x720 min: 720x400
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 21.3.7 compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:03.0
chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 9 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
class-ID: 0403
Sound Server-1: ALSA v: k5.16.12-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.48 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK AM1I-A driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: down mac:
Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb
bus-ID: 3-10:6 chip-ID: 148f:5572 class-ID: 0000 serial:
IF: wlp0s20u10 state: up mac:
Drives:
Local Storage: total: 4.55 TiB used: 1.36 TiB (30.0%)
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD5000AACS-00ZUB0 family: Caviar Green size: 465.76 GiB block-size:
physical: 512 B logical: 512 B sata: 2.5 speed: 3.0 Gb/s type: N/A
serial: rev: 1B01 temp: 31 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 4y 296d 8h cycles: 9620
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD40EFRX-68WT0N0 family: Red size: 3.64 TiB block-size:
physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s type: HDD
rpm: 5400 serial: rev: 0A82 temp: 35 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 5y 281d 7h cycles: 153
ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD5000LPVX-80V0TT0 family: Blue Mobile size: 465.76 GiB block-size:
physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s type: HDD
rpm: 5400 serial: rev: 1A01 temp: 29 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 243d 13h cycles: 59648
Old-Age: g-sense error rate: 1586
Partition:
ID-1: / raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.36 TiB (33.3%)
fs: btrfs block-size: 4096 B dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%)
used: 546 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
used: 1.36 TiB (33.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-4: /var/log raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
used: 1.36 TiB (33.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-5: /var/tmp raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
used: 1.36 TiB (33.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.32 GiB used: 4.8 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 221 Uptime: 16m wakeups: 0 Memory: 15.32 GiB
used: 2.11 GiB (13.7%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1761 lib: 410
Shell: garuda-inxi (sudo) default: Bash v: 5.1.16 running-in: alacritty
inxi: 3.3.13
Garuda (2.5.5-1):
System install date: 2021-03-08
Last full system update: 2022-03-07
Is partially upgraded: No
Relevant software: NetworkManager
Windows dual boot: No/Undetected
Snapshots: Timeshift
Failed units: nmb.service samba.service smb.service

garuda-upgrade and pacman -Syu indicate "nothing to do."

Well, it looks like I've gone from bad to worse. I have updated and rebooted so many times, trying to figure this out, that Snapshot has deleted all the prior snapshots that were working. I noticed the last time it was up that it was set to store 5 snapshots and I was on the last one. Then the desktop froze up with baloo running in the background. I let it sit for over two hours with no change, no way to get back to terminal. Did a hard reset - no other choice - and now none of the snapshots will load the kernel. It won't get past grub.

I noticed also before the freeze that my Snapshot app indicated my two btrfs drives had 3TB of free space, yet the Snapshot setup indicated there was less than 1000mb space and would not allow me to select a drive to store new snapshots. Also, btrfs Assistant showed 2.7TB available, but the data bar indicated 98%. Refreshing did nothing. I read that disabling quotas and qgroups would not allow btrfs to know how much space was available for snapshot storage and that deleting previous snapshots would break the indexing. So, I re-enabled all of it, hoping it would sort out the storage issue, but no joy. It is pretty obvious also that Baloo has some problems as kde's indexer. My system should be plenty to run this OS with btrfs, but apparently it just isn't up to it.

Now that my machine won't boot at all, I guess it's a good time to look at going back to plain arch. I used it for a year before Garuda. I'm not very good with it, but at least there's a good wiki and I have a pretty saavy son who is great with it (he isn't familiar with Garuda, so not much help there). I'm not trying to sound like sour grapes, because I like Garuda's package, but I have spent more time in the past couple months trying to keep it running than getting anything done using it. Trying to sort out the btrfs/baloo issue was the last straw. Luckily my data is safe and this has been nothing more than a learning experience.

Thanks for all the help and sorry for the wasted time. I may try Garuda again down the road.

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.