chli01

Members
  • Posts

    4
  • Joined

  • Last visited

chli01's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Cannot be. It was working for years. However the disk was not initialzed with UD, since I already formatted it before. So maybe it was only working by chance. Anyways... it does not seem to be an intended feature so I have to chance the disk format. Thanks for your reply.
  2. I'm using a Luks->Ext4 (with system enc key) external HDD. In the past mounting this device was working well, however after last reboot (and perhaps a new version of UD) I'm no longer able to mount the device because UD tries to mount it as XFS. Decrypting and mounting the volume manually wis working fine so it's not an issue of the device, see also the log: Dec 18 19:15:11 lud unassigned.devices: Adding partition 'WD_Elements_25A3'... Dec 18 19:15:11 lud unassigned.devices: Mounting partition 'WD_Elements_25A3' at mountpoint '/mnt/disks/WD_Elements_25A3'... Dec 18 19:15:11 lud unassigned.devices: Using Unraid api to open the 'crypto_LUKS' device. Dec 18 19:15:11 lud emhttpd: shcmd (281): /usr/sbin/cryptsetup luksOpen /dev/sdb1 WD_Elements_25A3 Dec 18 19:15:13 lud unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/mapper/WD_Elements_25A3' '/mnt/disks/WD_Elements_25A3' Dec 18 19:15:13 lud kernel: XFS (dm-5): Invalid superblock magic number
  3. I also had this issue (transport endpoint not connected) every few days. In the end it turned out for me to be caused by bad memory. I was running Memtest for several days but got only rare errors (one issue every few hours) - so I wondered if that could cause the frequent shfs errors. However, replacing the memory module totally solved this issue for me (no errors since 2 months now). So maybe you should also check your RAM.