billat29

Members
  • Content Count

    159
  • Joined

  • Last visited

  • Days Won

    2

billat29 last won the day on September 14

billat29 had the most liked content!

Community Reputation

10 Good

About billat29

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. This is now a bit off topic but when I had my moment with this, I looked in the log afterwards and there were a number of entries along the lines of "xxx has been successfully terminated" as if it wasn't actually a crash but something had sent a signal to terminate the tasks. Also my shares were still up on the network.
  2. Yes. You just delete the directory. You need sudo prior to the command. (Make sure that you don't mistype the command). Nothing magical will happen. Just ls -la again to make sure it has gone. Why the fuss? It's a left over from 5.2 and not needed in 6.1.7. However, if it is there in 6.2.3 it will cause all the services to crash after boot. You then get about 5 seconds after boot to ssh in and delete the directory before ssh itself crashes and locks you out. Been there (only ran ls -l). Done that. Recovered that. Same feeling as you had when you first attempted upgrade and it all went horribly wrong.
  3. Excellent! My plan was to get you to a stable platform so that you could easily SSH in and remove the .xpenoboot directory before jumping to the latest stable release, 6.2.3. You can stop and enjoy some movies but I suggest you plan some time to make the move before you forget how to do an upgrade. But do the bit about the directory removal now. Upgrade when you are ready.
  4. But see what it says tomorrow before you try. I should be back at around the same time tomorrow. IG-88 looks like they are around earlier.
  5. Progress. Try option 2. You will need to press and hold the down key just in advance of the menu coming up. Then you will have time to select the correct option. Or use the instructions in the FAQ to amend the timeout in the bootloader. If that works and you can connect this time, then I am expecting that you can download the 6.1.7 .pat file and do a manual install keeping your configuration,
  6. Boot the HP when you've done that. You need to see some messages from the loader on the console and then connect to the box from your PC with Synology Assistant or find.synology.com. Report back on the options that it shows.
  7. Some answers: C1E (or C1) is a BIOS setting. It needs to be set to disable on my AMD based Gen7 machine otherwise my loader does not boot (no xpenology messages on console). Might not be a requirement on your Intel G8. Go and have a look and disable it if you find it. vid stands for vendor id and pid is product id. They are properties of the card you are going to boot from. You need to follow the tutorial to identify them and put them in the cfg file on the loader you are creating otherwise your DSM system won't start. If you are going to overwrite your existing SD card, then you can use the same values as before. You can also use the mac and sn from from the cfg file you posted earlier. So go and do that. You have to make a decision whether you want to go "my" way and do an intermediate upgrade to 6.1.7 or take IG-88's advice and go in one step. If you are going to 6.1.7, you need the1.02b DS3615xs loader If you are going to 6.2.3 you need the 1.03b DS3615xs loader AND the HP must be booting in BIOS rather than UEFI mode (if there is such a thing on that box),
  8. First of all, IG-88 is the guru as their signature says. I just stumble around here :-). You trashed your SD card when you attempted the upgrade. The HP needs to boot the loader from the card and the loader can then bring up the DSM system which is resident on the system partition of all your disks. SO you need to do two things: 1) You need to create a new bootloader which must match the version of DSM you are trying to run. Until you do that we are not going anywhere 2) If you plan to upgrade directly to 6.2.3, you must find and delete the /.xpenoboot directory first. If you have no system, then you must boot something else, mount the RAID array and delete from the system partition (looks like /dev/sda1). One other piece of information is that on my older box (Gen7), 6.17 worked just fine without deleting that directory, So my different advice would be to upgrade to 6.1.7 and get your system running. And then you can delete .xpenoboot and upgrade to 6.2.3, Twice the work, but the "same" steps twice. ...more
  9. I guess that you attempted the upgrade without updating the USB stick first. How did you attempt the upgrade? Or rather how do we know that the version that was being installed was 6.0.3?
  10. The answer is the same for both: 6.2.3 Update 2 with juns DS3615xs loader v1.03b in legacy BIOS only. UNLESS you are successfully using disk hibernation on the Gen 8 in which case, disk hibernation may not work on 6.2.3. In that case, you want to try 6.1.7 (juns 1.02b loader). C1 needs to be disabled in BIOS for the N54L and if you previously had version 5 installed on the box, then you need to find and delete the hidden /.xpenoboot directory before the upgrade to 6.2.3. The linked post is about upgrading a Gen 8 with a crashed drive, but the posts about the upgrade are relevant.
  11. OK. That's even better. I would go for option 1 in that case. Pull everything out of the box. Two new drives and new USB and full install. Nice clean system;.
  12. OK. My option 1 was to say that you had copied all your files onto another computer somewhere. In that case you could afford to wipe everything clean and start again. When you had finished you can copy those files off the other computer. That doesn't seem to be what you are able to do here as all your files are on volume2. While there other options, I think that they add a whole new level of complexity. So. After my testing, what I would do is this: Insert volume2 and the two new disks in the box and boot. It should come up with a system with volume2 and two uninitialised disks. Go to storage manager and create your new RAID group (repeat after me: RAID is not a backup) and create a new volume on that RAID. Mine came up as... volume1. Create a new shared folder (or series of folders) on Volume1 and copy everything across. Now shutdown and pull volume2 and keep it somewhere safe. Reboot just to check that you have a working (ish- all the packages are broken) system and all the data is there. Yow will now need to ssh into the box (probably using putty from windows) with a user that has admin rights and do. cd / sudo rm -r .xpenoboot Now shutdown and pull the USB stick. Put it in the safe place with volume2. You asked why you should remove volume2 and the answer is that if the next steps go wrong, you can always go back to your running 6.0.2 system and start again / try something else. Now you can insert your newly created v1.03b USB stick and boot the system. Now you should be able to connect to the box via synology assistant or find.synology.com and run a manual upgrade specifying the 6.2.3 file you downloaded onto your computer. Assuming that it all works then you may need to repair your broken packages and go through all your config. What to do with volume2? Well, you could have left it in the box as you said and kept it as part of the upgrade but taking it out does give you a fall back position. And it is an old disk and given that its partner has failed, so maybe it is not long for this world. If you keep it, then it is a backup of your files at this point.
  13. Not quite. Let me go away for a bit. I have a test VM for DSM. I will clone it and try to set up your two options to make sure I am not sending you down the wrong path...