Jump to content
XPEnology Community

Hostilian

Member
  • Posts

    318
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Hostilian

  1. Hostilian

    DSM 6.1.x Loader

    Ummm. Yeah I do.. Unless I'm misinterpreting what you're trying to do! Always a chance! I thought I'd suggested a method (maybe I dreamed it?). ESXi.. You set up your VM in ESXi as you like it.. Shut it down. Go to the datastore on the host. Download the Boot drive VMDK of your VM to a new EMPTY folder on your PC.. You will note that there is more than one file when you download it (this is normal).. Your PC.. You should have Vmware workstation on your machine - this will allow you to Mount VMDK files as drive letters. Map the first VMDK file you downloaded to a Drive letter (NOT the vmdk file that has 'flat' or something in the file name), be sure to untick the 'read only' check box when mapping.. Go to the drive you mapped and edit the grub.cfg file. Save the file. Disconnect the mapped drive (right click on the VMDK file again) on your PC. ESXi again.. Next, go back to your datastore and upload BOTH vmdk files to the same location, one at a time. Close the datastore folder and power on your VM again. Watch how your SN and MAC addresses have changed.. Have a beer.. Yes, I've tested it and it works.. #H
  2. Resurrecting an old-ish thread but yeah, seeing slow Rsync copies between two machines. One custom server with DSM6.0.2 (i3 4330, 16GB Ram, 4x 3TB WD Red (with SSD cache), 2x NICs in LACP (confirmed working) - the other is a Synology 216j 2 bay NAS (1x NIC). Basically, I don't see it top 40MBytes/sec. Not massively slow, but nowhere near the maximum (I'd expect 90-100MB tops).. I've seen quite a few posts suggesting RSYNC is at fault but wondered if anyone had any suggestions. Interesting article.. https://lwn.net/Articles/400489/ Any thoughts on how to 'fix' it? Cheers, #H
  3. Hostilian

    DSM 6.1.x Loader

    I thought it was 'Original Poster'.. ...though I guess the meaning is roughly the same. #H
  4. Hostilian

    DSM 6.1.x Loader

    We're speaking here about the edition of VMDK file (provided in #1 topic) previously to any install, in order to follow QuickConnect registration process during installation ... Thanks. Ahh ok.. I've just started testing on ESXi with this image, so too early to say definitively.. I assume downloading the VMDK to another machine and trying to mount and edit it there has been tried? #H
  5. Hostilian

    DSM 6.1.x Loader

    Make sure the VM is shut down and its not 'locked'. Either close the VM in Workstation (or delete the .lck folder within the VM's folder) then, when you've finished mapping the VMDK file for editing, open it up again..
  6. Hostilian

    DSM 6.1.x Loader

    It's in the thread.. Download OSFMount tool and make sure you've not got the VM open - and read only isn't ticked.. http://www.osforensics.com/tools/mount-disk-images.html
  7. Hostilian

    DSM 6.1.x Loader

    The issue is not about reading the whole thread or asking question about linux commands. That is a problem you will find in any forum. You will always have those who need to be spoon fed constantly. The problem is that there has been several other loaders which have been posted by other members in the thread because Jun did not provided a BIOS compatible loader among other things. It's not a bad thing per say and he probably doesn't have much time as well but it does create confusion on what loader to use, trust etc. Giving the loader a name and version would also make things easier to track. Finally this forum is quite outdated and would need an overhaul but that is another issue. I think we all know what the issues are - and we've both now suggested ways to improve them.. The reading the whole thread point was a separate point. It still needed stating though as it would certainly help 'reduce' any confusion.. #H
  8. Hostilian

    DSM 6.1.x Loader

    I'm with Polanskiman on this. I think what you guys are doing is fantastic but please, can we get this under control. I am sure that a small number of you are more than capable of building your own custom loader and getting it to work, but I worry that the vast majority of users have little idea of what is going on (many have just managed to stumble through the tutorials that used to live on fan sites) and it's all going to go horribly wrong for them. Can we mark this thread as "Development Only" or something like that and ask one of you guys to start another thread as he suggests. Please? Partially agree.. I think a happy medium needs struck - without stifling innovation (and getting stuff out there to you and I)! At the very minimum, we need versioning numbers - and maybe some sort of package naming convention.. Other than that, I don't see too much of an issue. People should really read the whole thread. If people are asking how to perform basic linux commands then maybe they should pop onto Youtube and learn (like I did years ago), rather than expecting someone to step you through it here (it just dilutes the threads and information within). Reading this whole glorious thread won't take too long - it will definitely be worth the 30 mins or so effort required. #H
  9. Hostilian

    DSM 6.1.x Loader

    Also tested on old Dell Optiplex 755 (8GB 1x 250GB hdd). Works fine. Just needed the boot image from page 10. Enabled the serial port to save me another step. Updated to 8451 and then update 2 perfectly fine.. This is just for testing and fiddling about (ie, update to 8451-2 etc). My other one is rock solid! #H
  10. Hostilian

    DSM 6.1.x Loader

    Yeah, works fine.. You need to use the original network card MAC addresses - not the ones in your grub.cfg. I used my PCI-E add in card and made sure my BIOS settings were set as required. I had to tweak ASPM = 1 to get it to work, but work it does.. edit.. I should say, that's with LACP configured with my two NICs as a 2GB link.. I needed to use the original network card MAC address; because, when shut down, that's all that can be seen on the network.. #H
  11. Anyone tried Vistualbox on DSM6 (on bare metal)? http://xpenology.com/forum/viewtopic.php?f=15&t=3497#p20949 Cheers, #H
  12. Hostilian

    DSM 6.1.x Loader

    Anyone got DLNA working yet? Maybe I just need to be patient and let my TV find the box.. I've reduced the advertisement down to 600 (from the default) and the media is all indexed.. edit.. Solved. Was a TV problem. Now confirmed working fine on 6.0.2! #H
  13. Hostilian

    DSM 6.1.x Loader

    Ouch... all my data in the old version will be deleted, right? Copy your data to another system or other drives. If you don't have, recommend purchasing drives. It's good to have spare copies. Sent from my SM-N930T using Tapatalk I back up my documents, photos, music and family videos to BluRay occasionally too.. I have on an external USB3 disk for backups as well.. Once I think this 'hack' is stable on my server, I'll begin to use it (it'll have 4x 3TB drives when I move my other 2 disks into it).. To be honest, it seems fine as it is (and it's only pulling about 35Watts). My 216J synology will then be relegated to my backup device. I'll put an old 1TB drive in it and use it as a security camera drive. A second 5TB drive will be for backups across the LAN. Hoping you can have 2 independent disks in it (haven't checked that yet). #H
  14. Hostilian

    DSM 6.1.x Loader

    Thanks Jun.. Improper shutdown - fixed! #H
  15. Hostilian

    DSM 6.1.x Loader

    Known issue.. I'm sure your system really sees i5 and 4 cores.. You can check with SSH - look for the commands in this thread!
  16. Hostilian

    DSM 6.1.x Loader

    Just rename the file? Nice one! edit.. Yep, worked for me fine..
  17. Hostilian

    DSM 6.1.x Loader

    WRT the "improper shutdown" issue.. I've been digging around in some logfiles and config files via SSH.. It looks like there is a little script that checks for the presence of some files.. If there is a file called var/.NormalShutdown present, the error message (improper shutdown) does not appear. I have tested this by creating the file, shutting the box down and then starting it up again. With the file present, I don't get the error.. If this file is not present, the script creates another file called tmp/.ImproperShutdown The presence of this file - checked by another script - determines that an 'improper shutdown' has occured - and we get the error message.. It looks to me that the shutdown process (I haven't looked into that) is either in error (and it's not creating that .NormalShutdown file - even though there are no logs that I can find that suggest it is in an error state) OR The shutdown process is fine but there is a bug (and the file simply isn't being created).. Thoughts?? edit.. Thanks FiberInternetUser for the info.. Yeah, I noticed those earlier, when looking at my logs. How do I disable TTY please? #H
  18. Hostilian

    DSM 6.1.x Loader

    Not that I've seen.. Disks and CPU are zero % after booting up - every time - after seeing this message about the improper shutdown. I don't think it's doing a parity check - or anything, really. My box was powered down using either the power option on the console, the shutdown or poweroff commands (at a SSH terminal), so it was 'going down properly'.. It didn't suddenly switch itself off and reboot.. Personally, I think it's a bug (and there have been previous notifications on 'actual' synology devices about this bug) but it would be nice to resolve it.. #H
  19. Hostilian

    DSM 6.1.x Loader

    Me too And me.. Not too worried about it though.. I would say this is a nice to have (unless there really is a problem that puts the data at risk)..
  20. Hostilian

    DSM 6.1.x Loader

    I don't use Synology assistant as I didn't want to install anything and I didn't want to accidentally select my 'real' Synology device. I use a little program called NetScan.exe (from softperfect). It's free and will scan your network to find the synology box's IP given to it by DHCP (take a note of your MAC address). It also doesn't require installation (and is a lot more useful). Been using it well over 5 years.. I used the EFI/Legacy boot image from Setsunakawa on p10 (thanks man) - https://mega.nz/#!88dhAYCL!V_RviNsst7qi%20...%20GOz6P8GnZ0 I then got the boot image from Jun on page 1. (https://mega.nz/#!Z4UzWZxZ!hu9SZXpzJBTakHk7lO8pJfyHYb-YgGatI-Em9E3JXWI) I used the first image and burned it to a USB drive using USB Image Tool.exe. Then I needed to edit the grub.cfg file on it to reflect the USB drive's VID,PID. You need to set the desired SN and MAC addresses and add the SataPortMap=? if required. I replaced the ramdisk.lzma file on the USB drive with the one in Jun's image (second link above) at \image\DS3615xs The grub.cfg file is pretty much the same sort of file as your previous Isolinux.cfg file (which isn't there anymore).. No, you can't skip that step! My grub.cfg is... (Obviously, you NEED TO REPLACE the ???????'s with your own values.) set default='0' set timeout='2' set fallback='0' menuentry 'Synology DS3615xs' --class os { insmod fat linux /image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=4 HddHotplug=1 SataPortMap=3 syno_hw_version=DS3615xs vid=0x???? pid=0x???? console=uart,io,0x3f8,115200n8 sn=?????????? mac1=?????????? mac2=?????????? mac3=?????????? mac4=?????????? withefi elevator=your_magic_elevator quiet initrd /image/DS3615xs/ramdisk.lzma } Good luck, #H
  21. Hostilian

    DSM 6.1.x Loader

    Sorry, I can't see a link to an image under the EditEdit post on page one.. Which ramdisk.lzma should I use? Edit.. Version numbers are your friend!!! Just noticed that there was a new version of the image, rather than just the Ramdisk.. Testing now. EditEdit.. Looking SUPERB.. BTRFS and SSD Cache all working well on 8451-1. I was even able to set up a network team (LACP) - just need to move it upstairs to its new home. Looks like you've cracked it! Well bloody done! It actually has 4 cores.. Just displays it incorrectly! Cheers, #H
  22. Hostilian

    DSM 6.1.x Loader

    Yep, can confirm this works fine, thanks!! I added 'SataPortMap=2' to the line to get it to see only my two HDDs.. Also the USB drive came with 2 partitions already (from the image)! #H
  23. Hostilian

    DSM 6.1.x Loader

    I used the EFI/Legacy image, posted a few pages back..
  24. Hostilian

    DSM 6.1.x Loader

    Ok.. I've been tinkering around a bit and noticed that the drives with errors on them are the ones that didn't have anything plugged into them.. Odd. I removed a drive, then got error (1,2,5,6) If I move my 2x 3TB disks to ports 1 and 2, the error was (3,4,5,6). I tried changing various BIOS settings - but couldn't find a way to disable them individually. So.. I filled ALL my SATA ports with spare disks - and SUCCESS!! I was able to get an install prompt at the NAS URL! I still got errors when installing the PAT (6.0.2 v8451) though - "Failed to install the file. The file is probably corrupted" So.. I plugged my USB stick into a Windows machine to get the PID and VID (have a look in device manager), edited the Grub.cfg file (changing the PID and VID values) and.............. I was able to move forward. Unfortunately, after what looked like a successful install of 6.0.2 v8451 as 'Migrate' install. It did not work after a reboot (disks moved from previous system). A clean install does not seem to work either, after it reboots. It says disks were moved from previous system. A step forward though! Is there any way we can get it to discount certain SATA ports - or do we simply need to ensure all ports are filled? #H
  25. Hostilian

    DSM 6.1.x Loader

    Thanks for the new image but I get the same error as before (on bare-metal).. When accessing the synology NAS URL I get.... "We've detected errors on your hard drives (2,5,6) and the SATA ports have also been disabled." It then tells me to remove or reinstall them.. I've edited the grub.cfg to change my SN, MAC and PID but no joy.. #H
×
×
  • Create New...