hannibal1969

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hannibal1969

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. hannibal1969

    DSM 6.1.7-15284 Update 2

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: Jun's Loader v1.02b - DS916+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J3455-ITX - Additional comments: REBOOT REQUIRED | Extra reboot was required. USB boot was changed to HDD boot maybe mainboard issue?
  2. Polanskiman definitely! After my holiday I will make time for it and will do the upgrade.
  3. Sure Polanski I know the warnings. What I miss is clear directions how to overcome the 6.0.2 barrier and move forward to 6.0.3 and higher using the correct loader without to start all over again. According your statement above I would come up with these 2 possibilities. Prepare a 1.02b boot loader, Remove your current 6.0.2 disks, Investigate if you can get your system up and running with a spare disk and the new loader. This acknowledges that your hardware can be used with the new loader. Then put back your 1.01 loader start with the 6.0.2 disks and do the upgrade. After upgrading remove the 1.01 loader and swap the USB with the one where the new loader 1.0.2b is on. or start all over again and import disks and reinstall all applications Does that make sense?
  4. Missing driver(s)? I'm still interested if there is a proper upgrade method from DSM 6.0.2-8451 Update 11 on DS3615XS -> DSM 6.03 and higher using boot loader 1.02b. Simple question. Will boot loader 1.02b still work wit DSM 6.0.2-8451 Update 11 on DS3615XS?
  5. Sorry I digged the whole forum but I couldn't find a clear answer how to do the trick to move forward from DSM 6.0.2. I'm currently running stable at DSM 6.0.2-8451 Update 11 on DS3615XS bare metal. I was thinking to just create a new usb boot stick with loader 1.02b adjust the grub.cfg and boot my current DSM 6.0.2-8451 Update 11 with the new 1.02b loader. From there I like to upgrade just from the control panel. Can I do it this way? Thanks!
  6. But if you update the loader the NAS won't boot if the NAS is stil on DSM 6.0.2-8451 Update 9 so I asked if you update DSM 6.0.2-8451 Update 9 to 6.1 and you replace the USB stick with new loader is that the correct way? Sure I will wait a little longer.
  7. Sorry for being noob, I just installed new USB stick with latest Jun Loader to upgrade to 6.1. When I boot with new bootlader stick NAS tells me that I need to upgrade. Do I have to boot my nas with previous Jun's 1.01 boot loader, do the upgrade straight from nas GUI to latest 6.1 and after that reboot the nas but now with new 1.02a USB stick? Personally I think this is the way but I would just like to ask if this approach is correct. Thanks.
  8. hannibal1969

    DSM 6.1.x Loader

    Yes please do enlighten us on your procedure as I am getting the uneasy feeling that many people will start updating to 6.1 and then start crying like babies. I am currently advising this method viewtopic.php?f=2&t=13288 by adapting the version numbers but since I haven't tried it myself I can vouch for that. And if they do, they only have themselves to blame. I got no sympathy for 90% of the lazy community here that cannot even be bother to make a cursory Google search for ANYTHING. Sure I agree its true they have to blame themselves, but its no so black white as you say. Update 9 was also mentioned here by few that they upgraded and was successful. I'm also on U9 but after a while Polanskiman reported that its better to stay at U8 because there are some issues with U9. But see thats the problem some report it works and others start to upgrade so its never failsafe because not everything can be tested. And you didn't make a mistake in your life? And was that mistake not searchable by Google? I'm always a little bit cautious with targeting people to be stupid without google searching.
  9. Hi Polanski man. First great thanks for your support in all of this. I just read that 6.1 is a no go ATM. I also read that Update 9 is also problematic. I don't have any problems atm with update 9. Can you tell me why and how update 9 can give issues and what to avoid? Thanks!
  10. hannibal1969

    DSM 6.1.x Loader

    I am running DSM 6.0.2 on the ASRock J3455M (bare metal) and experienced some rather weird issues with the speed of the onboard Realtek RTL8111E chip. See the full details here: viewtopic.php?f=2&t=25026 After throwing in the Intel PCIe NIC and disabling the onboard Realtek chip, everything worked very smoothly. I read that topic ... this : I noticed that when downloading a file from DSM via SMB, there is a HUGE drawback in speed when I access it via its hostname (like \\mydiskstation). Download speed ranges from <1 MB/s to ~2.5 MB/s depending on the client I run the test on. Then I use the IP address instead (like \\192.168.1.10) everything is fine and I download at full GBit speed (up to 110 MB/s). Do you really its the realtek? This must be a hostname resolving issue. Multihomed nics / wifi?
  11. hannibal1969

    DSM 6.1.x Loader

    Well I did some tests. I have here several NICs. There is no significant difference between the onboard Realtec 81111GR, intel Gigabit CT desktop adapter and HP NC 110T. All of them fluctuate between 75 / 90MBs with iperf. The onboard performs even better then the HPNC110T. From windows or OSX i get transferspeeds of about 110MBs based on SMB3. Quite okay! (I use all my disks as individual drives so no raid, all of them are "basic"). So for me there is no reason for a no buy of the j3455 except from turbo boost which would be a nice bonus if it wwas working. I enabled my onboard nic again
  12. hannibal1969

    DSM 6.1.x Loader

    Are you sure? I'm here at J3455 AS Rock. Had intel first added because of easier way to change Mac address (ethtools) but had to use the NIC for another project. I'm here at maxed out speeds on that RTL 8111GR NIC. <- Not true .... Not so maxed out indeed.. just verified with iPerf and it maxes about 75MB/s also more parallel tasks will be limited to about 75? Better to replace intel NIC?
  13. Thanks for your answer. I installed hyperbackup and created a local backup of the important remaining shares on the Jbod to Volume 2. With putty i verified the @appstore folder to see the content of it. This was appache 2.2 only and I stopped this application. After that I removed the jbod initialized the new harddisk recreated the shares and started the Hyperbackup restore. After that I reinstalled the stopped appache. Everything is working again.
  14. Hi all. I have a baremetal XPEnology running using a mainboard with only 4 SATA ports. The first two drives are 6 + 3 TB which will remain there. The last two however are in jbod (1TB + 500GB) will be replaced by one new drive of 4TB. I like to migrate the whole content of the jbod (drive 3+4) to the new drive. Can I remove temporary drive 2 which I can miss for a few hours during the migration and replace it with the new drive so the jbod and the new drive are both there? If so what is the easiest way to migrate the whole contents of the jbod to the new drive? If I later remove the jbod drives and replace it again with the temporary removed drive 2 will all data be back? Is this a good strategy to migrate? I also though about buying a cheap 2 sata PCIexpress card so I can leave all disks in place and start the migration but they are quite hard to find. Thanks for your advise in advance.
  15. hannibal1969

    Thanks to all XPEnology Devs/Coders

    Happy newyear for everybody! More dancing for me in 2017 and less nerdy activities.