NASFAN1

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About NASFAN1

  • Rank
    Newbie
  1. Thanks Polanskiman, that seems sensible. Now i’m a bit nervous but am pretty sure I can get back to 3615 without having a nervous breakdown I guess I need to reinstall and configure some packages, and add in the users again. if I used the Syno Config backup and imported that, do you know if it it would keep some / all settings? I imagine I need to install packages again first.
  2. hi hoppler, you are a hero - I eventually worked out the way to go - rather than the file copying I started with a fresh USB stick and the 3617 loader - and then did the "reinstallation" step. It did take time to appear in Synology Assistant. So far I can see all data and am reconfiguring. Are there any reasons to go back to the 3615x - so far it looks OK? I owe you a drink or two 👍👍
  3. hi hoppler, so I'm really not sure this is working as expected. After the grub error above with 3617 loader , I made a 3615 bootloader and could see the Synology system in Syno Assistant as "Recoverable". The only option I get is to click "Recover". It does some reboot stuff and then won't see the USB stick again to boot and tries to boot off LAN. 😔 Turned off and then copied the extra.lzma, rd.gz and zImage files again (from 3615xs) to see what happened - back onto the same 3615 loader USB. It will boot to the GRUB menu again for 1.03b - but I'm not sure which to pick, option 1 or option 2 "reinstall"? If I pick option 2 I get the same "Recoverable" loop again.
  4. At least it's getting past the red screen - with the 3617 loader image from Jun it stops at "Grub Rescue" What did I do wrong 🙄 Normal.mod is in the path as the error says - at least in the synoboot.img before flashing...
  5. Update - I'm getting stuck at the flashing the boot loader to the USB - I'm not sure if I'm using the wrong setting with OSFMount or Win32DiskImager but I keep ending up with a USB stick with partitions which can't be read by Windows (and so it won't write the 3617 synoboot.img which I've edited with my MAC and PID, VID to USB). Managed to sort it with DISKPART. Still working through the steps....
  6. hi hoppler, that makes lot of sense and really helps understand what I'm doing and the why. Thanks again for taking time to walk me through this. I'm trying it out now. best regards
  7. hi hoppler, two other points before I try your method. 1) I only used the 3615xs bootloader 2) My disks are just JBOD not RAID so I'm hoping I can check one at a time. I'm not 100% sure I understand your recovery instructions but think I do - I think I can go with the 3615 loader instead or replacing with 3617xs being replaced (so maybe I miss one step)?
  8. Hi hoppler; many many thanks for your reply. I’ll look at that tomorrow - I did have a quick read and think I follow. Do you think if I put the disks in a real DS918+ it will recover a functioning system with the data? I guess I’ll need to manually recreate all the settings. I’m definitely keeping with Xpenology if I can get it working but have been finding the recent updates too stressful and might go to Synology hardware for my live system. best regards
  9. Hi all, I made a mistake and have managed to trash my perfectly functioning 6.1.7 15284 system. I'm very desperate for help. 😪 I was on 6.1.7 15284 with Jun loader 1.02 and decided to go to 6.2 23739 but hadn't spotted that 6.2.1-23824 warning. I was tired and thought it was the former warning which 1.03b fixed (I'd researched for hours weeks ago and decided to wait). Without realizing 23824 was now out, I accidentally let the Syno assistant pick auto update. It all looked fine, did some reboots, but then went horribly wrong. That's when I spotted Polanskiman's warning message was a different version and felt sick. I feel very very very stupid and it's not the sort of thing I usually do. I've since tried putting a spare wiped drive into slot 1 and running loader 1.02 again, hoping it might let me get into a reinstall. It won't detect the Synology at all. I can’t understand why a blank drive won’t work unless the loader USB is damaged. Trying to boot 1.03 just gives a red screen halt (an HP screen which seems related to the MBR being unreadable). I haven't tried recreating the boot USB - but have tried reading the original disks 1 and 2 (out of 4) in my PC to see if I can read any data. I can't get them to mount or read with any of the apps like Linux Reader, Ext2, and Ubuntu - but they won't see anything. Now I'm really worried that the disks are unrecoverable and totally puzzled as to why a clean drive won't start a fresh install. It's a baremetal HP Microserver Gen 8. It's sitting at the "Decompressing Linux...Parsing ELF....Done. Booting the Kernel" in the terminal. Nothing I do will work - which now isn’t a surprise, 😡  I have just ordered a Synology DS918+ in the hope that I can create a new vanillla 6.2.1-23824 system and maybe read the data off or remount the other 3 drives. if anyone can give any advice, I will be eternally grateful. 🙏
  10. hi all, I'm in a similar situation and very desperate for help. 😪 Rather than starting on 5.2, I was on 6.1.7 15284 with Jun loader 1.02 and decided to go to 6.2 23739 but hadn't spotted that 6.2.1-23824 warning. I was tired and thought it was the former warning which 1.03b fixed (I'd researched for hours weeks ago and decided to wait). Without realizing 23824 was now out, I accidentally let the Syno assistant pick auto update. It all looked fine, did some reboots, but then went horribly wrong. That's when I spotted Polanskiman's warning message was a different version and felt sick. I feel very very very stupid and it's not the sort of thing I usually do. I've since tried putting a spare wiped drive into slot 1 and running loader 1.02 again, hoping it might let me get into a reinstall. It won't detect the Synology at all. Trying to boot 1.03 just gives a red screen halt. I haven't tried recreating the boot USB - but have tried reading the original disks 1 and 2 (out of 4) in my PC to see if I can read any data. I can't get them to mount or read with any of the apps like Linux Reader, Ext2, and Ubuntu - but they won't see anything. Now I'm really worried that the disks are unrecoverable and totally puzzled as to why a clean drive won't start a fresh install. It's a baremetal HP Microserver Gen 8. It's sitting at the "Decompressing Linux...Parsing ELF....Done. Booting the Kernel" in the terminal. Please help if you can sbv3000 or anyone else.
  11. NASFAN1

    Support for Seagate IronWolf?

    So I tried running the tests again, and cannot see any entries in Log Center. Is there anywhere else I could look for logs?
  12. NASFAN1

    Support for Seagate IronWolf?

    thanks IG88, I will see what I can find out in the logs. I honestly can't remember the Gen 8 model info (and am travelling) so will add to that too. cheers
  13. NASFAN1

    Surveillance Station - additional cameras?

    Thanks for confirming what I suspected Polanskiman.
  14. hi, does anyone know if I purchase a camera licence pack, will it work or is it relying on "real" SN/MAC ID? I have a HP Gen 8 and DSM 6.1.5, one camera but want to add 2 more. (2 are supported free). My guess (I have searched but cannot find a definitive answer) is yes a real SN / MAC are needed. All the free tools I can find do not seem to work - Quick Connect is the way I am testing valid pairs, which may be wrong. Thanks