Jump to content
XPEnology Community

CtrlAltDel

Member
  • Posts

    344
  • Joined

  • Last visited

Everything posted by CtrlAltDel

  1. This seems like a good configuration for a virtualised Xpenology build. Worthy of detailed tutorial in its own thread imho. Couldn't you image your ESXI installation to an external drive prior to an update so you have an easy rollback path if some show stopping issue arises? If the image had everything you need to get back Xpenology and your primary OS instance recovery time would be rapid, plus you would have your important stuff back ready to work with, without too much effort.
  2. There's a list here for quicknick's dsm6 build here > viewtopic.php?f=2&t=24308#p81999 and there's info for Jun's build here > viewtopic.php?f=2&t=22100
  3. A number of people have reported updating to ud6 without issue.
  4. The nForce is supported in Quicknick's new loader and tool package > viewtopic.php?f=2&t=24308#p81999 read the first post for full details.
  5. It gets freakier than that, I had a Sandisk 8gb that was working fine with the original loader of Jun's. I updated it with the new v1.01 image with all the details remaining the same but the machine wouldn't see it as a boot device? I dug out a tatty old 2gb unbranded stick applied the same image with new vid/pid and the same ser/mac's and it booted without issues? I don't get why it worked with one version and not with another?
  6. Thanks for sharing your work Quicknick. I haven't tried it out yet but it looks very comprehensive with good docs, change logs and support info. Great job.
  7. Take a look at Quicknick's new loader and boot tool his build looks like it supports your RTL8111C nic viewtopic.php?f=2&t=24308#p81999 The downloads are linked in the second post viewtopic.php?f=2&t=24308#p81997 for full details start reading from post one.
  8. I've just set this up on a friends clean baremetal install on a gen8 but it should be the same for gen7's. You need Arcao's power button package here > viewtopic.php?f=2&p=75406#p75404 Then you need to ssh/winSCP on to your box and copy the files into the appropriate folders and set scripts to executable. You can extract the package in the root or do each upload individually. The later maybe a little slower but the chances of an error is reduced...plus you get to understand more about what's going on. I didn't upload the files in etc/acpi from the package as they were present. I tested without including them and it worked fine. Reboot and test the power button shutdown - job done. Edit: For anyone reading this after installing on an HP gen7/8 the following maybe on your check list: WOL works otb. Just make sure you use the mac address defined in the grub. PowerSave Governor works otb. Defaults is "powersave".
  9. It works for me on Gen8 and Gen7 N40L so there should be no reason for it not to work on your machine that I know of. This is a bit old but may be of some use viewtopic.php?f=2&t=20216&start=420#p74492 things have changed since then, but I haven't tried the new loader so I can't tell you what to expect. I'm not sure if Arcao's power button fix is included in the current release or not?
  10. The problem is that you didn't follow the correct update path. Because you have tried to upgrade from within the DSM update process your system is in an unknown state. I'm not going to test it to see what happens and I doubt anyone would spend time investigating an edge case that's caused by user error. You have few options: 1: Try and force an update with your machine in it's current state 6.x to 6.x using Jun's loader. Edit the grub to select the default boot option or press the arrow keys to interrupt the boot process. Personally I wouldn't spend too much time on this option as it's an unknown. 2: Roll back to the most recent Xpenology version and recover to a known good position and then follow the tutorial for installing 6.x using the migration process. 3: If your data is safely backed up and verified use a linux boot disk and trash the partitions on the drives. Once your drives are cleared of Synology partition data follow the tutorial and rebuild from scratch. If I were in your situation that's what I would opt for. In fact I wasn't in your situation and after testing my migrated build I decided to do a fresh install (bit of ocd I wanted a clean build rather than gaining any other benefit). Make sure you use the AMD installation option from the grub, if you miss that step you will be pissing in the wind. You're going to have to bite the bullet and pull the trigger on one of those choices imho. I'm crap with linux though so maybe someone has better ideas involving some linux magic?
  11. Did you try http://10.10.10.3:5000 ? If you use http://10.10.10.3 it should redirect to the set-up page if you're doing an install or the web page if DSM is set-up and web hosting is configured. https://10.10.10.3:5001 if you had set-up the ssl and migrated that port should still be working. Edit: Those port numbers are only relevant if you clean install or migrate and didn't change the default port values in the old installation.
  12. Afaik you can't mount a drive in the way you would like under DSM. You can create a diskgroup/volume which consists of one single disk and you can use the ext4 file system on that volume (which can be mounted under any number of linux distros for recovery). I haven't noticed an option to use ntfs as the underlying file system on a group/volume. In my experience if one disk wakes they all wake. Having said that I haven't investigated what happens in the configuration you mention. I suspect you will find that it will wake regardless of it being a separate group/volume. If I'm wrong I'm sure someone will correct my mistake/s.
  13. Yes, see this post viewtopic.php?f=2&t=20216&start=420#p74492 some of the other info may have changed since the launch of Jun's v1.x loader.
  14. Look back two or three posts above your post and you will find the answer.
  15. I haven't needed to do it and I don't have a way to look at the files right now but there should be something like this at the top "GRUB_DEFAULT=0" where 0 equals the option to boot by default. There's another line that allows you to change the delay time of the menu, if you increase that value the menu will stay up long enough for you to pick the boot item you want. You can also try pressing the arrow key during the boot like you would the fkey to access bios for example.
  16. Your post count maybe too low to add images? Have you tried adding a disk group and then adding the volume after that?
  17. Read Jun's opening post in this thread and read this post > viewtopic.php?f=2&t=22100 and yes it works for Baremetal builds. Not all the drivers that have been supported in the past are available using Jun's loader though, which could be an issue if your hardware isn't supported.
  18. You could try editing the grub so that the option you want gets loaded by default and then reboot without the monitor attached. There is nothing to see using June's loader anyway. Wait a while and then search for the device with Synology assistant or look in the router for the ip address, then use your browser to navigate to the setup/migration page. That should work if the monitor is causing issues. Also try different thumb drives because some people have reported issues with some usb drives.
  19. Not sure using a restore from an older version is a good idea. Restore config works great. That's actually a a step to move from ext4 to btrfs That's good to know. Personally I would be very wary of using old config restores especially when it involves major versions. Config's handled by a migration script may handle conflicts by design, where as a straight restore may not handle them as expected? I would rather not assume especially when it has the potential to make a recovery difficult, if vital parameters have been filled with garbage or the files get totally trashed. If you know for sure there's no risk then obviously that's a different kettle of fish.
  20. Not sure using a restore from an older version is a good idea.
  21. Use ssh and look in /etc and also /etc.defaults both contain different versions of synoinfo.conf. /etc.defaults is required for certain changes that will only become persistent when the change is applied to synoinfo.conf in that location. Edit After upgrading to DSM6 the root account will be independent of the primary admin account for increased security. You need to login with the primary account and password for your ssh session. Then use "sudo su -" or you can find instructions to set a pw for the root account. There is info about changing the root pw here > viewtopic.php?f=2&t=20216&start=420#p74492 .
  22. Yes, read this thread > viewtopic.php?f=2&t=22100 and the OP of this thread > viewtopic.php?f=2&t=20216
  23. No, everything isn't on the flash drive the flash drive is only used in the boot process, post boot it has not function. There is an OS/DSM partition on every drive in the system. Yes you can recover drive 0 provided you're using multi disk groups/volumes in some form of raid. In a one drive set-up there is zero redundancy, so recovery is extremely unlikely. If you're lucky you may be able to recover the data by mounting the drive under a linux system and using conventional file copy to recover data to a backup drive/system.
  24. Yes, set-up a domain here > https://www.changeip.com/accounts/cart. ... roduct&i=0 and install the ddns updater 2 package. Configure the domain and port forwarding job done.
  25. I have a gen8 which I upgraded from 5.2.x and then a totally fresh clean build and https worked fine for the apps in both cases. Just need to do all the regular stuff like setup the ports etc. in the application portal and set the firewall rules. I also setup a lets encrypt cert no problems there either, but I only assigned it to sites hosted on the web server using virtual domains, not the apps. The only thing that seems different is the auto/forced redirect for http to https. I just fixed that with htaccess rules after failing to find the option in the control panel. I haven't got round to trying the reverse proxy yet. I think you may need to use reverse proxy to apply the lets encrypt cert to apps based on a few comments I have read elsewhere. I don't open the apps up to the outside world so I haven't investigated that as yet. htaccess rule RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]
×
×
  • Create New...