ChatNoir

Moderators
  • Posts

    1592
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by ChatNoir

  1. In any case, ReiserFS is only supported for legacy reasons and is not recommended anymore (for some years I guess). https://wiki.unraid.net/File_System_Conversion
  2. You might want to start reading this :
  3. Is there a reason to use UD and not Unraid Pools ? It would require using BTRFS but there would be advantages (data available in the Shares, possibility of redundancy, etc.)
  4. This subforum is dedicated to users using Unraid as VM in another system EXSI, etc. From your post, I do not feel that it the case. Can you confirm so a Moderator can move the thread if necessary ?
  5. Unraid identifies the drives with their serial number, not the port on the Controller(s). The only time it can be an issue is with RAID controllers that change the S/N. It does not seem to be the case here.
  6. How is the content of the backup you downloaded ? Is there weird files there too ?
  7. The files you are transferring, are they big files or a lot of tiny files ?
  8. I see plenty of errors around 01:38 Aug 23 01:38:10 Storinator smbd[8648]: [2021/08/23 01:38:10.692320, 0] ../../source3/smbd/open.c:3817(open_file_ntcreate) Aug 23 01:38:10 Storinator smbd[8648]: open_file_ntcreate: Could not get share mode lock for Rebel_06/._.DS_Store Aug 23 01:38:10 Storinator smbd[8648]: [2021/08/23 01:38:10.692351, 0] ../../source3/lib/adouble.c:2102(ad_open_rsrc) Aug 23 01:38:10 Storinator smbd[8648]: ad_open_rsrc: SMB_VFS_CREATE_FILE failed Aug 23 01:38:11 Storinator smbd[8648]: [2021/08/23 01:38:11.947297, 0] ../../source3/smbd/open.c:3817(open_file_ntcreate) Aug 23 01:38:11 Storinator smbd[8648]: open_file_ntcreate: Could not get share mode lock for Rebel_06/Adams_Matkasse/._.DS_Store Aug 23 01:38:11 Storinator smbd[8648]: [2021/08/23 01:38:11.947327, 0] ../../source3/lib/adouble.c:2102(ad_open_rsrc) Aug 23 01:38:11 Storinator smbd[8648]: ad_open_rsrc: SMB_VFS_CREATE_FILE failed And it goes on for 4000 lines like that. Then between 01:49 and 01:53 your ethernet is down Aug 23 01:49:43 Storinator kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Down Aug 23 01:49:43 Storinator kernel: bond0: (slave eth0): link status definitely down, disabling slave Aug 23 01:49:43 Storinator kernel: device eth0 left promiscuous mode Aug 23 01:49:43 Storinator kernel: bond0: now running without any active interface! Aug 23 01:49:43 Storinator kernel: br0: port 1(bond0) entered disabled state Aug 23 01:49:44 Storinator dhcpcd[1824]: br0: carrier lost Aug 23 01:49:44 Storinator avahi-daemon[2304]: Withdrawing address record for 10.0.0.59 on br0. Aug 23 01:49:44 Storinator avahi-daemon[2304]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.0.0.59. Aug 23 01:49:44 Storinator avahi-daemon[2304]: Interface br0.IPv4 no longer relevant for mDNS. Aug 23 01:49:44 Storinator dhcpcd[1824]: br0: deleting route to 10.0.0.0/24 Aug 23 01:49:44 Storinator dhcpcd[1824]: br0: deleting default route via 10.0.0.1 Aug 23 01:49:45 Storinator ntpd[1899]: Deleting interface #3 br0, 10.0.0.59#123, interface stats: received=1154, sent=1154, dropped=0, active_time=255675 secs Aug 23 01:49:45 Storinator ntpd[1899]: 216.239.35.0 local addr 10.0.0.59 -> <null> Aug 23 01:49:45 Storinator ntpd[1899]: 216.239.35.4 local addr 10.0.0.59 -> <null> Aug 23 01:49:45 Storinator ntpd[1899]: 216.239.35.8 local addr 10.0.0.59 -> <null> Aug 23 01:49:45 Storinator ntpd[1899]: 216.239.35.12 local addr 10.0.0.59 -> <null> Aug 23 01:53:36 Storinator kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 23 01:53:36 Storinator dhcpcd[1824]: br0: carrier acquired Aug 23 01:53:36 Storinator kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Aug 23 01:53:36 Storinator kernel: bond0: (slave eth0): making interface the new active one Aug 23 01:53:36 Storinator kernel: device eth0 entered promiscuous mode Aug 23 01:53:36 Storinator kernel: bond0: active interface up! Aug 23 01:53:36 Storinator kernel: br0: port 1(bond0) entered blocking state Aug 23 01:53:36 Storinator kernel: br0: port 1(bond0) entered forwarding state Aug 23 01:53:36 Storinator dhcpcd[1824]: br0: rebinding lease of 10.0.0.59 Aug 23 01:53:36 Storinator dhcpcd[1824]: br0: probing address 10.0.0.59/24 Aug 23 01:53:41 Storinator dhcpcd[1824]: br0: leased 10.0.0.59 for 86400 seconds Aug 23 01:53:41 Storinator dhcpcd[1824]: br0: adding route to 10.0.0.0/24 Aug 23 01:53:41 Storinator dhcpcd[1824]: br0: adding default route via 10.0.0.1 Aug 23 01:53:41 Storinator avahi-daemon[2304]: Joining mDNS multicast group on interface br0.IPv4 with address 10.0.0.59. Aug 23 01:53:41 Storinator avahi-daemon[2304]: New relevant interface br0.IPv4 for mDNS. Aug 23 01:53:41 Storinator avahi-daemon[2304]: Registering new address record for 10.0.0.59 on br0.IPv4. Aug 23 01:53:43 Storinator ntpd[1899]: Listen normally on 4 br0 10.0.0.59:123 Aug 23 01:53:43 Storinator ntpd[1899]: new interface(s) found: waking up resolver I do not know much about the first issue, maybe someone can offer suggestions. For the Network, not sure if it is Unraid specific or your network in particular.
  9. Your diagnostics might show what happened if you didn't reboot. In any case, it would provide context to understand the situation better. Go to Tools / Diagnostics and attach the full zip to your next post.
  10. Your diagnostics might show something. Go to Tools / Diagnostics and attach the full zip to your next post.
  11. Yes. It's Safe Mode that prevents plugins from loading. It is available at startup, or you can reboot the system from Main and tick the box to start in Safe Mode.
  12. Probably because file transfer generally first create the directories and your splitlevel makes it that the share want to keep everything together.
  13. Asus does not keep the specification of old product online, but from I could gather your P5W DH Deluxe has : Storage/RAID Intel ICH7R South Bridge: * 1 x UltraDMA 100/66/33 * 3 x Serial ATA 3.0Gb/s avec Intel® Matrix Storage Technology pour le support RAID 0, 1 et 5 Jmicron JMB363 controller * 1 x UltraDMA 133/100/66 * 1x Serial SATA 3.0Gb/s * 1x External Serial ATA 3.0Gb/s (ASUS SATA-on-the-Go) * Support SATA RAID 0, 1 and JBOD (by 1x External SATA & 1x Internal SATA) Silicon Image 4723 Hardware RAID controller (ASUS EZ-Backup) * 2 x Serial ATA 3.0Gb/s with RAID 0, 1 support * Support RAID 10 cross Intel® ICH7R and Silicon Image 4723 controller Not sure what is the driver status for Silicon Image ? Maybe try to stick with the 3 Intel ports and the Jmicron ? Not sure if this could help though.
  14. Looks like the Marvell controller is only used for e-SATA. You should be OK on that front.
  15. This is a Plex issue, not and Unraid issue. You should ask for support in the support thread of the application you are using. You can access it directly from the Docker tab of Unraid , clic on your app icon, then Support.
  16. Content que tu n'ais pu récupérer tes données.
  17. C'est l'autre méthode oui. Comme je te le disais, j'ai la chance de n'avoir jamais eu besoin de faire ce genre de manip moi même. Mais du coup, mon expérience pour les conseils ne vient que des forums et de la doc.
  18. You should post that in the bug report section. https://forums.unraid.net/bug-reports/prereleases/ Either on the release post or as a separate thread.
  19. You can use either Krusader, Unbalance or Midnight Commander (mc in the console). With Krusader and MC, be aware to always move file disk to disk or share to share and never mix the two or you might loose data. Unbalance is safer for this. Personally I'd use Unbalance as it can move at once all files from any directory that are on several drives. Less operations for the user.
  20. Si tu es sûr de tes disques, oui.
  21. You might want to try USB UPS cable instead of Smart.