Joel Graff's questions

Question spawned from a previous question found here:

Very long startup time on Ubuntu Server (network configuration)

I have two swap partitions mounted in my fstab which seems odd. I'm guessing it's a byproduct of the process of builing a RAID array (maybe I botched something somewhere).

Some relevant logs as suggested by @heynnema:

/etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md2 during curtin installation
/dev/disk/by-id/md-uuid-4c695059:2f774b0b:9e5492d2:bcb62609 / ext4 defaults 0 0
/dev/disk/by-id/md-uuid-05f3f447:6002213f:2bb97c81:6416f121 none swap sw 0 0
# /boot was on /dev/md0 during curtin installation
/dev/disk/by-id/md-uuid-58dd9ab9:74b02d8a:10890b55:2212c9cb /boot ext4 defaults 0 
0
/swap.img   none    swap    sw  0   0

swapon -s:

Filename                Type        Size    Used    Priority
/swap.img                               file        4194300 0   -2
/dev/md1                                partition   8379388 0   -3

ls -al /:

-rw-------   1 root root 4294967296 Jun  9  2020 swap.img

free -h:

              total        used        free      shared  buff/cache   available
Mem:          7.7Gi       1.3Gi       5.0Gi        22Mi       1.4Gi       6.1Gi
Swap:          11Gi          0B        11Gi

The output of fdisk -l does not list any swap partitions...

I've been trying to sort out two problems that I suspect are interrelated. Recently, our network got reconfigured and afterward, I encountered a very long boot time due to network configuration issues and, after booting, no longer able to access the samba file share from a Win10 client.

The boot time messages:

[  OK  ] Reached target Network (Pre).
Starting Network Service...
Starting Wait for Network to be Configured...
Starting Network Name Resolution.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[**    ] A start job is running for Wait for Network to be Configured (XX / no limit)

It takes about two minutes for the last message to clear. I suspect it's maybe a DHCP or DNS-related issue. I've also noticed several of the "NXDOMAIN / potential DVE2018-0001 violation" errors interspersed in /var/log/syslog. At the moment, I really don't know where to go poking next to figure out what's causing this delay (or why the file server isn't visible to Win10 clients). Incidentally, Samba appears to be running and Webmin reports that the folder share is active...

EDIT 1:

Per the suggestion of @heynnema in the comments, the output of cat /etc/netplan/*.yaml:

# This is the network config written by 'subiquity'
network:
    ethernets:
        enp4s0:
            dhcp4: true
    version: 2

EDIT 2:

Samba-related output.

fstab contents:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/md2 during curtin installation
/dev/disk/by-id/md-uuid-4c695059:2f774b0b:9e5492d2:bcb62609 / ext4 defaults 0 0
/dev/disk/by-id/md-uuid-05f3f447:6002213f:2bb97c81:6416f121 none swap sw 0 0
# /boot was on /dev/md0 during curtin installation
/dev/disk/by-id/md-uuid-58dd9ab9:74b02d8a:10890b55:2212c9cb /boot ext4 defaults 0 
0
/swap.img   none    swap    sw  0   0

smb.conf Share Definitions:

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain 
Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin


[media_Public]
    create mode = 777
    path = /home/media/Public
    writeable = yes
    public = yes
    directory mode = 777

I have been trying to get a RAID5 partition going on a home file server with limited success. Thus far, I've managed to build the array, and I can mount it manually.

However, it creates the array at /dev/md127, whereas I was expecting to see it at /dev/md0.

Also, it doesn't automount, I'm assuming because I have to add the individual disks to /etc/fstab? It certainly doesn't like it when I try to mount /dev/md127. I can mount it using the GUI on the server, but commandline mount via ssh fails, anyway.

It's a software-based RAID array using mdadm.

So I'm trying to get an older system that has an integrated VIA graphics chipset. It's supported directly by the openchrome driver, which I installed from the repo.

The driver requires setting up xorg.conf, which I did following the manpage instructions

However, when it boots the desktop shows up and becomes garbled, then returns shortly thereafter. I think what' happening is the driver is crashing and it's defaulting to the VESA driver, as that's what's loaded when I call lshw from the commandline.

Anyway, I'm not sure where to begin troubleshooting. I looked through the syslog, but nothing stood out to me.

I have a 32-but linux install and I've checked Xorg.0.log for errors and noted:

[drm] Failed to open DRM device for pci:0000:01:00.0: No such file or directory

dmesg returns the following:

pci 0000:01:00.0: vgaarb: setting as boot VGA device pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none pci 0000:01:00.0: vgaarb: bridge control possible

then later:

pci 0000:01:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]

So the PCI address is valid...