NooL

Members
  • Content Count

    51
  • Joined

  • Last visited

Community Reputation

5 Neutral

About NooL

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. NooL

    NVMe cache support

    When look at var/log/messages my logs seems filled with 2020-09-01T15:00:13+02:00 DiskStation SystemInfo.cgi: nvme_cmd_raw_binary_get.c:54 fread failed 2020-09-01T15:00:13+02:00 DiskStation SystemInfo.cgi: nvme_temperature_get.c:24 Can't get the smart-log raw binary 2020-09-01T15:00:32+02:00 DiskStation synostoraged: nvme_cmd_raw_binary_get.c:54 fread failed 2020-09-01T15:00:32+02:00 DiskStation synostoraged: nvme_temperature_get.c:24 Can't get the smart-log raw binary Any ideas how to fix this?
  2. Hmm no real good ideas, but let me try digging around a bit and see if i can find something
  3. Downgrade your Video Station installation. I am having issues with the most recent one as well. It refused to pick up all my files. As an example, I could have a folder ShowName1, Subfolder Season 01, 6 Files in the folder, all named with the same naming scheme - but only one or two of the files would get picked up no matter what i did. Tried reinstalling video station several times and reindexing, same result. Tried downgrading it to https://archive.synology.com/download/Package/spk/VideoStation/2.4.7-1603/ and it worked as it should again, so try the same perhaps? NB: The old versions media data search does not seem to work, as i think they moved to a new system. So hopefully a new version will be out soon.
  4. NooL

    NVMe cache support

    Any idea why only 1 of the 2 identical drives is listed correctly with name? They are identical drives so a bit puzzling.. DSM also gave the warning about using different drives for NVME cache when recreating it.
  5. NooL

    NVMe cache support

    This is brilliant - Thank you so much for your work @flyride and @The Chief !!
  6. i didnt look much into it, as i had a custom-flashed NIC in the mail. So i just temporarily fixed it after boot
  7. I had the same issue - only the first port got "spoofed" while the other one was left untouched, and there was no errors in grub file
  8. I dont wanna go the SFP route, i wanna keep it RJ45 - So Netgear GS110MX seems a good choice with 2x 10/5/2.5GbE and 8x 1GbE at around 160~€
  9. If nothing else, then you should be able to see the serial number of the drive in question in DSM Storage Manager - that serial number should also be listed on the actual drive itself
  10. Another day, another question Using the alias part of control panel you can set up alias for synology apps.. like /file /video /photo etc. How would one go about creating custom aliases? E.g i use Serviio and would like to use /serviio for that.. Thanks in advance.!
  11. For others checking the topic - If you get the error that site cannot be opened when you try opening the QuickConnect in Control Panel - Or try to setup a synology.me DDNS - Then its a serial number/mac issue. If you check tail /var/log/messages when this occurs, you will see an error stating invalid serial/mac combinatination or the likes.
  12. SUCCESS AGAIN! Synocheckshare was the magic command to get my shares back and running. Everything is now as if nothing had happened.
  13. And the raid parity check went with no problems. BUT - i am still not seeing the "Shared Folders" in the GUI - they are there and i can copy data via SSH - but i am not seeing them in GUI - which is making everything a bit harder as I cannot use the built in tools to transfer (Windows share, ftp, etc etc) Does anybody have an idea how i can restore the Shared Folder metadata that was lost in the crash/reboot?
  14. Same deal basically with md3 - md4 was fine already. mdadm --assemble --force --run /dev/md3 /dev/sdk6 /dev/sdl6 /dev/sdm6 /dev/sdj6 /dev/sdn6 -v i tried to --re-add at first with md3 since it was just missing 1 drive, but the event counts were to much different , so had to re-assemble it with above
  15. SUCCESS!!! I now have access to my data! mdadm --assemble --force --run /dev/md2 /dev/sdg5 /dev/sdh5 /dev/sdi5 /dev/sdk5 /dev/sdl5 /dev/sdm5 /dev/sdj5 /dev/sdn5 -v vgchange -a y vg1000 lvm lvchange -ay /dev/mapper/vg1000-lv mount /volume1 was the magic commands. Any ideas on how to re-create the Meta-data of Shared Folders? I can see in the log that it was removed after reboot following the crash.