SMB drive "local device name already in use", dashboard inaccessible

  • 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.

    • New
    • Official Post
    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:


    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.

    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.

    Code
    sudo fdisk -l
    Disk /dev/sda: 3.64 TiB, 4000752599040 bytes, 7813969920 sectors
    Disk model: My Passport 2626
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  • 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.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!