flyride

Members
  • Content Count

    845
  • Joined

  • Last visited

  • Days Won

    53

flyride last won the day on May 27

flyride had the most liked content!

Community Reputation

295 Excellent

About flyride

Recent Profile Visitors

4,508 profile views
  1. The values in /etc.defaults/synoinfo.conf are copied to /etc/synoinfo.conf each reboot. You will probably need SataPortMap=188 and DiskIdxMap=180008 for your drives to be properly visible spanning controllers. If you are asking whether this is new for version 6, you need to go to the FAQs and spend some time reviewing the 6.x loader instructions and how to implement those settings into the loader.
  2. Yes, a clean install would involve setting up a new copy of the loader. The RAID configuration of your data disks doesn't matter.
  3. If you cannot afford to lose the data, why were you upgrading? No backup? At least test using a spare disk? Anyway, does your system support another drive? If so, you can just install clean and then attach your data drives as long as they did not get overwritten by your upgrade procedure. Get a third drive that has no data on it and do an initial install with loader 1.03b and DSM 6.2.3. If you have difficulty with a basic 6.2.3 install too, at least you can troubleshoot and fix it without risking your data. Once DSM boots normally, do NOT create a Storage Pool or Volume. Just make sure DSM is booting and working then shut it down. Attach your data disks. It is important that the drive you just did the initial install on remains as drive #1 (or the lowest-numbered port). The data disks you add should be #2 and #3 if your sig is accurate. Boot up and your volume and data should be accessible. You'll need to "Fix the System Partition" to overwrite DSM on the array disks. As a result any DSM customization you may have made will be lost. If you did a DSS backup of your DSM settings you can re-import it and at least those items (user accounts, etc) will be restored. If you had complex folder perms they may be lost. Packages will need to be reinstalled. Make certain everything is green in Storage Manager. If you want to get rid of the extra drive, shut down DSM and remove the disk. Boot back up. No other action required.
  4. Wow. Just wow. Try starting here instead of the loader development thread:
  5. try editing /etc.defaults/synoinfo.conf. You did not post much information about your system. Are your disks passthrough? How many controllers? How many ports on those controllers? Did you have a custom setting for DiskIdxMap and/or SataPortMap in your loader?
  6. No, DSM is installed to all available block storage devices for redundancy (which is another reason not to present a monolithic device to your VM). All you need is the boot loader on the first Virtual SATA controller as device 0:0 Connect your RDM drives in sequence to the second Virtual SATA controller as device 1:0, 1:1, 1:2, etc 2nd virtual disk isn't required if you have RDM devices online Every disk has three partitions, Linux, swap and data. When you run the DSM install it will RAID 1 DSM (Linux and swap) to the first two partitions, respectively. Once DSM is fully installed you can use the data space for whatever array configuration and volume layout you wish.
  7. Always use DSM RAID, btrfs self-healing features and advanced disk management are the whole point of the system.
  8. RDM is probably your best choice, connect the RDM disks to second virtual SATA controller for 6.2.x SMART does not work because the code is custom compiled into Synology's utilities and you can't override the SMART query strings like on a normal system. You can get rid of the incessant SMART errors in /var/log/messages by following instructions here:
  9. pfSense will need to route the vlan's (and IP networks that connect them). Your PC apparently is bound to both VLANs and IP networks so it can see both. This is a basic networking problem. If you aren't sure how to fix this problem, I would question the value of your multiple VLANs in the first place.
  10. Your loader version doesn't make sense. 1.01? Should be 1.03b for DS3615xs and DSM 6.2. Are you using someone's prebuilt VM?
  11. Or even print the screenshot of your Storage Manager HDD's?
  12. Even if you lose the SHR setting, that only affects the ability to build and manage the array. It will still mount and you can go back in and add the setting if necessary. You cannot upgrade from the GUI. You will have to update the loader to 1.03b, change boot mode to BIOS if not already, and then do a migration install. Have backups. It does work but there are a lot of ways for it to go wonky.
  13. I was able to correct with a migration install from DS3615xs to DS3617xs. This reinstalled enough of the OS that the issue (and a couple of other odd things) was resolved.
  14. This thread is a year old and OP hasn't been back since then. Seems unlikely that he will answer?