• Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About NooL

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. NooL

    NVMe cache support

    This is brilliant - Thank you so much for your work @flyride and @The Chief !!
  2. i didnt look much into it, as i had a custom-flashed NIC in the mail. So i just temporarily fixed it after boot
  3. 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
  4. 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~€
  5. 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
  6. 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.!
  7. 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 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.
  8. SUCCESS AGAIN! Synocheckshare was the magic command to get my shares back and running. Everything is now as if nothing had happened.
  9. 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?
  10. 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
  11. 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.
  12. Yeah i've been reading up on that, and thats the one that gave me hope. From what i read, it should be possible to mdadm assemble the raid in the correct order and get access to the data again.
  13. Unfortunately my friend have not had time to look into it yet, but after some intense googling i found that the space_history files contain the disk/partition order i believe. From before the crash it looked like this: is this any help?
  14. Yeah the raid was expanded as i used one of the 8tb as a temp storage while i built the NAS. They do not belong to same cable, as the 8TB disks are on different connectors. So its like the screenshot. 2,2,2,8 and 4,4,4,8 on the SAS controller. My theory, but im not sure.. do correct me if its not plausible. I already had one disk (Disk 9) which had 2 bad sectors (This will flag the disk as degraded?) This morning i then got a disk write failure (The one from the log) on disk 8 - which caused it to throw the raid as its a SHR1? Im not sure if this is it though as the raid was marked as healthy in the UI - even with the 2bad sectors on one of the disks.
  15. I have a friend who works professionally with unix/linux who will take a look at it monday, hopefully he can work some magic. If there are any suggestions or help, please keep it coming Thanks alot for the help so far - will keep you guys updated if i dont hear more in here