Jump to content
XPEnology Community

cstout

Member
  • Posts

    76
  • Joined

  • Last visited

Everything posted by cstout

  1. @fjf I have a full backup on my DS412+ so I pulled 5 of my 8 drives and the 1517 booted right up with my login. Logged in with my DSM config in-tact and my array degraded (as it should be). I removed the volume and restored from backup. I am planning on replacing the old drives anyway so if I can't find what's causing this strangeness then I'll be doing a clean install with the new drives anyway. Just thought it was interesting enough to share is all.
  2. Strange as it may be it worked wonderfully with the exception of this one small thing (which is no deal breaker). It's mostly just piqued my curiosity to see if anyone was aware of a modification within DSM outside of or carried over from the XPE usb booter. In the meantime I'll post any updates I get as I work with support. If this was a deal breaker I would of course start fresh but I preferred to see if a migration would work (it almost entirely did) and I wanted to retain my app data and customizations from the last four years. Thanks all!
  3. Yes, it's the same account, but even if I wanted to change it I can't. I can't get the login/register window to open whatsoever. Also, I use this same account for my DS412+ and it still works with that same account so I'm leaning more toward some file/setting that migrated over from XPE into the real hardware.
  4. @Polanskiman, please note I am not asking for tips or tricks to abuse QuickConnect on XPE. I've been working with Synology support and they don't know what the problem could be and I'm curious if it's something that carried over from XPE. Ok, so I've used XPEnology for about 4 years now and have loved it. So much so that I recently bought and migrated to a DS1517+. This thing is great. I got excited to use QuickConnect legitimately but quickly found that I am unable to even log in. I get hit with the same screen that many XPE users see, which is, "The system failed to perform the requested operation, there is an unknown error." The control panel has my old QuickConnect ID entered in but grayed out. I cannot edit it and cannot log in. All I get is that error. A similar block is in place for enabling remote access in Support Center->Support Services. If I try to enable it, it immediately disables itself. I'm curious, and hope someone has some insight, if there is a certain file somewhere in the system that carried over during migration that is causing Synology to flag my real DiskStation as a fake. Any help or recommendations are greatly appreciated! Thank you!
  5. Thank you for your understanding. I appreciate all your contributions to this forum. I will work toward moving away from QC on my off site XPE box to avoid anymore topics like this.
  6. @Polanskiman, I am most certainly not complaining about the service not working. I asked a question whether others were experiencing the same issue. Also, I OWN a legitimate Synology box and don't use QuickConnect on it. I do, however, use QuickConnect on one remote XPE box that doesn't work reliably with DDNS services. It's interesting to see this policing and strong opinion when the forum allows and outlines how to set up QuickConnect on XPE yet when you ask a question about it you get smacked in the face. I'm not trying to perpetuate a dead topic. For anyone having the same issue it was resolved by signing out and back in. This entire forum works in a gray area. If QuickConnect is black and white then the topic should be banned from this forum.
  7. Wow. Useless. This is a *forum* and there are plenty of guides for setting up QuickConnect. All I did was ask if others are being blocked from this service. I'm not throwing out entitlement or any BS that would provoke such an arrogant response.
  8. I've been using QuickConnect successfully for over a year now on an off-site box and just a few days ago, while I was connected to DSM (XPE 5.1) I lost the connection and now all the iOS apps and the QuickConnect link for web access no longer work. I restarted the box multiple times and everything works locally, but I'm curious if anybody else has been blocked from QuickConnect when using a generated serial and MAC address. I'm going to try logging out and back into the QuickConnect service in Control Panel but I don't know why, other than a block, out of nowhere it would stop working. Has anybody else seen this behavior?
  9. Hardware: Dell OptiPlex 7010 SFF Install Type: Baremetal NIC Model: Broadcom, supported Storage: SATA, 1x500GB HDD Issue: Installation/Hard Drives Loader Version: 2.2 I am eager to test this new loader but I keep running into an error on the initial setup screen (see photo below). I only have one hard drive installed (HGST 500GB SATA) and the BIOS is configured for AHCI SATA operation mode and only the SATA-0 port is enabled in the BIOS. This is my XPE test box and has been fully compatible with ever other loader that's come across this website. I'm curious what the hangup is here. I was able to SSH into the configuration tool and ran the quick setup and also set the number of drives to 1 and I still get the pre-installation failure reporting, "We've detected errors on the hard drives (2,3,4,5,6), and the SATA ports have also been disabled. This error only slightly changes in drive numbering if I enable all (and unused) SATA ports. Not sure where to go from here but I wanted to post this issue in case anybody else doing a basic baremetal install is running into issues.
  10. cstout

    DSM 6.1.x Loader

    I successfully installed DSM 6.0.2-8451 Update 4 on my bare metal box without any issues.
  11. cstout

    Working DSM 6

    I migrated from the latest version of XPE 5.2 to 6 on SHR without any data loss. It's called a "migration" and DSM handles it perfectly. @foster182, your doubt is pretty close to exactly what I did. The only difference is that when you burn the dsm6 loader to USB just make sure to enter your config for SN and MAC address.
  12. cstout

    DSM 6.1.x Loader

    I had this same issue initially and read that you had to swap out a file on the flash drive with an updated one. Sorry that's vague and not very helpful, but if you haven't already, I'd recommend starting over with jun's v1.0 that just released. The file swap and many other issues are all fixed in this release. I also use Optiplex 760's and I am very happy with them. Edit: Sorry, just saw your most recent post so this is irrelevant. Congrats on the successful build!
  13. Hello out there, I'm asking this question on behalf of anyone else out there that may have some obsessive compulsive tendencies... Since switching my RAID mode to AHCI (required for DSM 6 bare metal boot) my motherboard SATA and Marvell SATA connections are separated by four blank drive spaces (images below). I've seen the question asked before, but I have not found any threads with an answer or solution. Does anybody know how the drives are numbered in DSM? Is it possible to change the order? In XPE 5.2 I had this exact same issue and disabling eSATA in the BIOS removed the gap and placed all of my drives together in order. Since going to 6 the gap is back and eSATA is still disabled. Drives currently show 1,2,3,4,9,10,11,12 (1-4 Marvell, 9-12 Motherboard).
  14. cstout

    DSM 6.1.x Loader

    Simple enough! Used vi to edit /usr/share/init/syno_poweroff_task.conf, found the line with console output and changed to console none. No more improper shutdown message.
  15. cstout

    DSM 6.1.x Loader

    I feel like I'm missing something very simple...would you tell just how you made this change?
  16. cstout

    DSM 6.1.x Loader

    Yeah, I've got 7 *old* repurposed enterprise 1TB drives and one 1TB WD Blue (the 6gbps drive). These drives perform wonderfully for me and are so fast that my only bottleneck is the 1GB pipe it is connected to. My current report shows: [ 3.477028] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.478032] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.479021] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.480026] ata6: SATA link down (SStatus 4 SControl 300) [ 3.480053] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.670030] ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.670061] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.671019] ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.672016] ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 300) I'm curious what ata6 is though. I just left the house so I can't verify, but I'm wondering if eSATA got re-enabled in the BIOS. That would explain why my drives are numbered 1,2,3,4,9,10,11,12 again...super annoying for OCD but I'm glad it's functioning again. Last time the drives showed in this order eSATA was enabled and for some reason DSM is reserving 5,6,7,8 for that port. Disabling eSATA and switching the RAID mode to legacy was what got my drives listed in a 1-8 order last time.
  17. cstout

    DSM 6.1.x Loader

    Last update, and it's a happy one. I switched my RAID mode in the BIOS from legacy to AHCI and voila, my drives are all present and the RAID set has been successfully reassembled. This is a successful upgrade, bare metal, from XPE 5.2 to 6. Note: My BIOS RAID mode was originally set to legacy due to that being the only mode that all eight drives would properly detect in v5.2. Now, switched over to AHCI, everything appears to be in great shape!
  18. cstout

    DSM 6.1.x Loader

    Very interesting turn of events here...I just physically verified serial numbers and...the *only* drives showing in DSM are actually attached to the Marvell card. None of the four drives attached directly to the motherboard are being detected!
  19. cstout

    DSM 6.1.x Loader

    I ran the command and it only shows four of my drives: [ 0.000000] Sata Port Map: 8 [ 3.023055] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 4 ports 6 Gbps 0xf impl SATA mode [ 3.080735] ata1: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff100 irq 50 [ 3.080740] ata2: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff180 irq 50 [ 3.080742] ata3: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff200 irq 50 [ 3.080745] ata4: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff280 irq 50 [ 3.540025] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.542020] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.543024] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.543040] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Storage Manager only detects 4 disks as well, which is why it is displaying my volume as Crashed currently. Any ideas? I added the line "SataPortMap=8" into the grub.cnf and this is the same result as it was without the line added.
  20. cstout

    DSM 6.1.x Loader

    Marvell 88SE9235 is working fine, take care you've to update the .cfg file in order to support number of disks you've connected ‪Very interesting. When I had originally specified my disk count "SataPorts=8" I was getting the error stating 4 disks were missing. I'm running the legacy bios (hybrid uefi) booter posted a couple pages back. There was a note that mentioned something like "if booting legacy, SataPorts amendment is not necessary." So when I removed that line it was able to boot up without an error...but it also booted up without four of my disks being detected.‬ ‪DSM 6 installed quickly and I was able to log in normally after it completed but was greeted with "volume crashed" and only four disks showing.‬ ‪Any ideas? So glad to know it's not a driver issue!‬
  21. cstout

    DSM 6.1.x Loader

    Can anybody confirm if the Marvell 88SE9215 chipset is supported with this loader? I just did a migrate from 5.2 on my 8-disk box and it only sees 4 of my disks. I'm guessing this is a driver that needs to be added in and I jumped the gun. Can anybody confirm this? I've never compiled a driver so if anybody has any tips or guides on what, if anything, I can do I would greatly appreciate it!
  22. cstout

    Working DSM 6

    Hello Everyone, I wanted to write to let you know that the UEFI img for bare metal works flawlessly for me (tested on Dell Optiplex 7010). All I had to modify in the grub config was the number of sata ports (as mentioned 1-2 pages back). I set up a basic JBOD RAID and created a BTRFS volume. The BTRFS volume mounts after every reboot as well (to my surprise). I updated to the latest release (DSM 6.0.2-8451 Update 1) without any issue whatsoever. What shocked me even more is that QuickConnect works perfectly. I set a SN, MAC, and flashed my ethernet card with the new MAC address as you would on any other XPE build and I was shocked to see everything register perfectly. Confirmed QuickConnect functionality by using iOS apps as well. I am thrilled with the community development of this! Well worth the wait. Thank you all! I'm going to build out a couple more tests before I upgrade my XPE 5.2 machine to 6 but it's looking great so far. I want to make sure there aren't any strange issues when going from 5.2 to 6.
  23. cstout

    Working DSM 6

    From what stout has said, He has baremetal DSM6 working. This includes btrfs but only with MANUALLY mounting the Volume first (this would need to be done at every boot). It seems he has official packages installing however I'm not sure about community ones. Perhaps @cstout could post his steps including the .img and .pat files he used to get his working? I have a similar machine at home that I might try with - providing enough of it works. I just used the last link from @dynax for the .img: https://mega.nz/#!w9RkULAR!3_Hhvp7yX3kc ... kRBzxw1ONY I used the pat from @oktisme: https://mega.nz/#!sQlWSC5C!tgGduyY5bze3 ... 87PrPkx4fc Yes, BTRFS only with manually mounting the volume: same issue everybody seems to be having currently. I currently don't have time to write up a more detailed step-by-step, but if your'e familiar with the bare metal process from v5 just follow my rough outline of steps from my last post and use the files I linked above and you'll be in business (if your hw is compatible). Hope this helps! I've only tested official packages (all working) and I don't currently use any community packages.
  24. cstout

    Working DSM 6

    Well, this is pretty great. My Dell Optiplex 780 just so happens to be generic enough that I am confirmed booting bare metal to a 100% working DSM 6. The only BIOS setting I had to change was switching SATA operation from legacy (default) to RAID On. From there, I booted the flash drive I placed the latest .img on and booted from "install." Incredible how fast this boots...seriously, from power off to active network connection it was only a few seconds. From there, find.synology.com, upload the pat file, restart and let it use the "run" option. This boot took a little longer as it did the install list. After that was finished I sat at the "system is getting ready" progress bar. I thought this was the point of no return, but after waiting about two minutes it greeted me with the welcome screen! Entered a server name, username, password, etc and finished setup. Created a BTRFS volume (SHR, btrfs) and had the immediate crash issue as others have described. More on this in a moment. Then I ran (successfully) Update 1 from the Control Panel. Then enabled SSH. Logged into SSH and ran: mount /dev/vg1000/lv /volume1 and voila! There's my BTRFS volume mounted with no errors/issues. Created a new shared folder and verified everything is working as it should. Very...very cool. Control Panel Update & Restore: http://imgur.com/J9yHW7C Control Panel Info Center: http://imgur.com/WxdycQw Storage Manger/Volume: http://imgur.com/6vWBTCj
  25. cstout

    Change Model

    Ok sounds simple enough. I tried something like this a year back so in foggy on exactly what happened but I recall setting the serial and trying to use the 3615 pat and it said model mismatch. So...do you only change the serial after DSM is fully installed? I feel like it switched to "migratable" when I did it last.
×
×
  • Create New...