Jump to content
XPEnology Community

kbonnel

Transition Member
  • Posts

    5
  • Joined

  • Last visited

kbonnel's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. FYI: I replaced the libsynoshare.so.5 with the original DSM 5.0 4493 version (including in this thread), did a reboot, and all is good. I am starting to think that the update 5 version of the libsynoshare.so.5 has an issue with multiple disks. Or it could just be my setup. Anybody else have the ability to test?
  2. Hi All, So, I did my third test. I initially redid my test 1, which resulted in a result that was the same as the previous test, everything worked fine with encrypted folders/shares. I then shut the system down, and added the remaining 2 disks. Upon boot up, I added them to the SHR volume and let it build overnight. In the morning one of the two disks had been added and it began working on the second disk. I decided to see if I could mount one of the few encrypted folders, but I got the same error "The operation failed. Please log in to DSM again and retry". It seems very strange that everything works fine with a single disk, but stops working when additional are added. Any thoughts? I am now going to try and replace the libsynoshare.so.5 with the one in this thread. (which appears to be the original libsynoshare.so.5 from the DSM 5.0 4493 load)
  3. FYI: So I did a test: 1) Fresh install, to just 1 disk, DSM 5.0 update 5, and did not have the issue with adding an encrypted shared folder. After reboot, still able to mount no problem. Date/size of the libsynoshare.so.5 was: Sep 4th, 1am. 644 permissions / size: 104616 Before the update 5, the file was: May 30th, 09:26am. 644 permissions / size 104596 2) Fresh install, 3 disks, DSM 5.0 then update to 5. When I try to create the encrypted shared folder, I get "The operation failed. Please log in to DSM again and retry." The permissions, size, date of the libsynoshare.so.5 is the same as it was in task number 1 after the update 5. I am going to try one more test tomorrow, repeating step 1, verify it works, then add the other 2 disks into the SHR, let it build, and try the test again.
  4. I have been doing some testing on my TS140 as I have seen some strange variations in my xpenology DSM 5.0 - 4493 installs. In my initial install, where I only had 1 hard drive in it (WD RED 4TB), the initial DSM 5.0 installed fine, and I did the manual install to Update 5. I did have to do a hard reset after the update as the system froze after bootup (after the post message. I would get the diskstation login, but it would then hang) After booting back up, it worked fine, and I was able to create shared folders, including encrypted shares. I then added a 2nd and 3rd 4TB drive, and all worked fine. I was doing a lot of testing with DSM 5.0, and decided to do a fresh install, and when I did the update 5, I again had to do the hard reboot. (this seems normal, as I have seen the issue with previous updates as well). This is when I ran into the same "Operation not possible. Please sign in DSM and try again" message when I tried to create an encrypted share. This got me wondering why it worked the first time, but not the second, and the only difference in the installs was the 1 vs 3 drives. So, I did another test and did a fresh install with just 1 drive, did an update 4 (I wanted to see if I got the same freeze, that required a hard reboot, which it did),, and then did an update to 5. This time around, I was able to add encrypted shares without the error. I ran out of testing time, but I am going to do the following: 1. Do a new fresh install to DSM 5.0, and then do an update to update 5 with just 1 drive. (I will do this twice, once where I only remove the SHR volume from the disk, where it will show as migratable, and one time where I will completely wipe the drive before I do the install. Just to see if there is any difference) If everything works fine, I will then: 2. Do a new fresh install of DSM 5.0, and then do an update to update 5 with all 3 disks. Will report back.
  5. Hardware: Lenovo ThinkServer TS140 70A4000HUX i3-4130 3.4GHz Server with 4GB ECC memory. PCI-E: Intel EXPI9301CTBLK installed in 1x slot USB: ADATA Superior Series S102 PRO 32 GB USB 3.0 Flash Drive AS102P-32G-RGY I installed Nanoboot 5.0.3.2 with DSM 5.0-4493 X64 then installed Update 5. I am using the built-in i217 NIC and the Intel EXPI9301CTBLK in a BOND setup. Installed without any issue, using 3 x 4TB WD Red drives. NOTE: I got a private message from unmesh asking if I am using UEFI boot vs legacy and power usage. I can't seem to reply to private messages. In any case, I will double check later today/tomorrow, and update. 9/25/14 NOTE: I checked my TS140, and it is set to be AUTO in terms of BIOS mode. It will use UEFI or Legacy depending on O.S. installed, at least that is how I read the BIOS settings. I am not sure which one xpenology uses. As for the power usage, initial power on with 3 4TB WD Red drives hits about 70watts, and when everything is running, it idles at around 30 - 35 watts. While doing a parity check of volume, the system fluctuates from 37 - 45 watts.
×
×
  • Create New...