Even with a bidaily reboot task schedule, my configuration still hates any reasonable uptime. If I don't "use" it, i.e. use the NAS drive or stream from Plex, after more than a day, the dashboard becomes inaccessible (even though my router shows it is connected) and any NAS link says "local device name already in use". Usually the most reliable solution is a hard reboot and check for updates - there seems to be a correlation with updates breaking it but I haven't proven it. Hard reboots are not a steadfast solution as I often work remotely and the whole point of setting up OMV is to use it through a remote proxy. I found no old threads about the local device name issue or if it's correlated with any other access or runtime problems - asking if other have had this problem or if there's a logical solution.
SMB drive "local device name already in use", dashboard inaccessible
-
-
So you have issues with the Plex, GUI of OMV and SMB?
You need to search the logs for errors.
I would start with the journal which you can read with journalctl.
-
Is this what you need?
-
-
Code
Mar 30 06:00:15 openmediavault kernel: sd 0:0:0:0: [sda] tag#0 timing out command, waited 180s Mar 30 06:00:15 openmediavault kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=180s Mar 30 06:00:15 openmediavault kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x4 [current] Mar 30 06:00:15 openmediavault kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x44 <<vendor>>ASCQ=0x81 Mar 30 06:00:15 openmediavault kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 83 81 01 20 00 00 00 08 00 00 Mar 30 06:00:15 openmediavault kernel: I/O error, dev sda, sector 2206269728 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2 Mar 30 06:00:15 openmediavault kernel: EXT4-fs warning (device sda): dx_probe:818: inode #68943913: lblock 0: comm Plex Media Scan: error -5 reading directory block
You have lots of error messages regarding the filesystem on sda. Is this drive part of a RAID?
At the end, the logs are strange:
Code
Alles anzeigen-- Boot 45599f5b9f17476bb8b803969aaac79d -- Mar 30 12:17:01 openmediavault systemd[1]: Starting Load Kernel Module drm... Mar 30 12:17:01 openmediavault systemd[1]: Starting Load Kernel Module fuse... Mar 30 12:17:01 openmediavault systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped. Mar 30 12:17:01 openmediavault systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Mar 30 12:17:01 openmediavault systemd[1]: Starting File System Check on Root Device... -- Boot 7df702e52e1c496cb83da777bb877cbc -- Mar 30 12:17:01 openmediavault systemd-modules-load[165]: Failed to find module 'softdog' -- Boot 45599f5b9f17476bb8b803969aaac79d -- Mar 30 12:17:01 openmediavault systemd[1]: Starting Journal Service... Mar 30 12:17:01 openmediavault systemd[1]: Starting Load Kernel Modules... Mar 30 12:17:01 openmediavault kernel: fuse: init (API version 7.37) Mar 30 12:17:01 openmediavault systemd[1]: Starting Coldplug All udev Devices... -- Boot d07e8f9d1f144bc68c83e4f41eaff1f6 -- Mar 30 12:17:01 openmediavault systemd[1]: Finished Set the console keyboard layout. -- Boot 7df702e52e1c496cb83da777bb877cbc -- Mar 30 12:17:01 openmediavault blkmapd[173]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory -- Boot cb04a942ff8a4e1abee314a02ebb0c62 -- Mar 30 12:17:01 openmediavault kernel: sd 0:0:0:0: [sda] Write Protect is off -- Boot 45599f5b9f17476bb8b803969aaac79d -- Mar 30 12:17:01 openmediavault kernel: sd 0:0:0:0: [sda] Attached SCSI disk Mar 30 12:17:01 openmediavault systemd[1]: Mounted POSIX Message Queue File System. Mar 30 12:17:01 openmediavault systemd[1]: Mounted RPC Pipe File System. Mar 30 12:17:01 openmediavault systemd[1]: Mounted Kernel Debug File System. Mar 30 12:17:01 openmediavault systemd[1]: Mounted Kernel Trace File System. Mar 30 12:17:01 openmediavault systemd[1]: Finished Restore / save the current clock. Mar 30 12:17:01 openmediavault systemd[1]: Finished Create list of static device nodes for the current kernel. -- Boot fc35e47723334326a64103ba47aa271a -- Mar 30 12:17:01 openmediavault systemd[1]: Finished Remount Root and Kernel File Systems. -- Boot 7df702e52e1c496cb83da777bb877cbc -- Mar 30 12:17:01 openmediavault systemd-sysctl[174]: Couldn't write '10000' to 'dev/raid/speed_limit_min', ignoring: No such file or directory
Usually each line staring with "-- Boot ??????????????????" indicate the start of the logs for a reboot. But in your log it is a total mess. No idea what that means.
I would check the SMART values of sda and run a filecheck.
-
No RAID, just an external 4TB WD drive.
Code
Alles anzeigensudo fsck /dev/sda/ fsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) fsck.ext2: Not a directory while trying to open /dev/sda/ The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>
If it's just a mount issue, I don't know how to kill the busy PID to unmount it as it appears to be related to the /srv/[dev-disk]/NAS/pi subfolder and it closes my SSH connection.
-
After a few days of working NAS (about as long as the last post - I didn't test Plex) it's down again. The router shows my Pi is online and I can ping to it but I cannot connect with SSH or access the dashboard.
-
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!