• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by billat29

  1. Good point. Sorry wasn't reading your post properly
  2. Are you using 6.2.3? That is not what your post says.
  3. .. or it does start but no filestation, no packages and a "locked" Resource Monitor.
  4. Correct. As the messages at the top of the forum page say - 6.2.4 does not work right now
  5. It depends what you are trying to achieve, if you just want to run DSM on the box across the 4 drives then you don't want either the SATA expansion card or graphics card. The BIOS you have will do. You just need to make sure that the drives are in AHCI mode and that C1 is disabled in the BIOS. You will need the 1.03b DS3615xs or DS3617xs loader and 6.2.3. There's a whole lot of information listed here: You can ignore references to setting csm / legacy mo
  6. OK. That will teach us to follow some guide on the internet! So what do you have now? First of all, did you take the original (120GB) disk out? If the 500 is storage pool 2 is there a storage pool 1? and what does it say for RAID type?
  7. I am reading that as either DS3617 doesn't work on your hardware or maybe there is a problem with the config on that stick. but I think you are saying that DS3615xs works perfectly. If it boots normally from the DS3615xs stick and all works, I would say that it is fine. Erase the other stick and move on!
  8. AHCI mode is what is needed. Your image says "error 13". Error 13 doesn't usually mean that the file you downloaded is bad. It says "I tried to initialise the disk and load DSM onto it. Something went wrong." I don't know why 3617 doesn't seem to work, but I can see by searching the forum that people have had success with 3615xs. There is no problem with using that. Is DSM now working? If you are still getting error 13, then the first thing to check is that you modified grub.config in the loader to match the values for the USB stick you are using and that they a
  9. When I restarted, the storage pool had crashed I ignored that and connected by SSH and ran the magic command: sudo mdadm --grow --raid-devices=1 --force /dev/md2 That immediately sorted the crashed storage pool and started an expansion When that was done, I went to expand the volume as the link said but found it was already done and that was it. It seemed to have worked. My packages were still there as was my (limited) data.
  10. I started with my virtual machine on 6.2.3 U3. It had one 8GB drive. I then defined and added a 128GB virtual drive and rebooted the machine: I have two unused drives as the first is the bootloader and I haven't applied the fix for hiding it when running in a VM. I then went to Storage Manager>Storage Pool>Action and selected "change RAID type". I selected RAID1 and dragged and dropped my new drive Next it resynchronised. Then I shut down and removed the old drive before restarting ..
  11. The "one disk" strategy that I linked to appeared to work. The method is slightly different for 6.2.3. I'll put some screenshots up shortly
  12. @Vodka2014 I broke my virtual environment. That was while I was setting up to test this. I didn't get as far as trying it. Then @flyride came in and they really, really know their stuff. So I edited my post and crossed my offer out. I have watched flyride sort out the most difficult problems and would have every confidence that if anyone can sort you out, they can. My concern now, having reread all this, is what state is your system in? I don't understand why you need to order another 500GB disk right now. You started with a 120GB and tried to move @appstore onto the
  13. Just to be clear, you are installing 6.2.3: DSM_DS3617xs_25426.pat Once installed and running, you should go to Control Panel > Update and Restore and make sure that it is set to install updates manually: You should never install an update until you have checked the "updates" forum. It should at this time offer to install the minor update, Update 3, to 6.2.3. It is safe to install that.
  14. Yes, that should work. I have seen reports of people successfully running this version on ML110, so I am confident! When you have it up and running, DSM should offer an update to 6.2.3 update 3. That should be safe to accept.
  15. 1. Let DSM set up the RAID rather than doing it in hardware. 2. DSM partitions every disk - system, swap and (your) data. It installs a copy of DSM on every disk. So if one disk fails, it can always start from another
  16. 1. The USB stick contains the bootloader. DSM is installed on HDD. See this: 2. The USB is only used at boot time. If it dies, then you can create another one by the same method as the original. 3. Your data is kept on a separate partition on HDD. If for some reason, you cannot start DSM any more and it can't be fixed, then it is always possible to boot your box with a linux live USB stick to recover the data. The procedure for this is documented in the forum. 4. This post explains the link between loader versions and DSM versions, it also makes recommendations on how to c
  17. When you wiped the drives, what did you do? Did you delete all the partitions on them or just clean out the data partition?
  18. @santi If you read the first post of this thread and are none the wiser; if you want the easiest way to install DSM, then I would advise 1.02b DS3617xs and DSM 6.1.7. There's a good chance that it will "just work". If you want to do some more research, then you should search the forum to see how people have got 1.03b DS3617xs and DSM 6.2.3 to work on this type of hardware. Such as this ==> If you start installation and get stuck, then start a new thread in the appropriate forum describing your hardware, what you are trying to do, how far you got and what error me
  19. I found this, I'm going to try it in a virtual machine BRB
  20. Wait. That's a different question. Is your question really "I want to replace my current disk with a new one and keep all my data and applications settings"?
  21. I would like to know at what stage you get "disk full". If it is during the file move, then I am thinking about a permissions problem somewhere. What I did was the move, changed the symlinks and restarted DSM, I confirmed that the applications seemed to be working before I removed my original disk. But there was more work to do before removing the disk. I remember that I had to move the user home service from volume1 to volume2
  22. looking at the link. Should be sudo mv /volume1/@appstore/* /volume2/@appstore/ unless you were root already
  23. "disk full" when you tried the mv command?
  24. Going a bit OT, then in days of old and "real" IBM mainframes, there was a hardwired process to start the machine called Initial Program Load. There were dials on the console so that you could dial in the address of the IPL device (card, tape or disk) and press a button to load all of 24 bytes into memory (starting at address 0). Those 24 bytes contained the code to load the operating system - which needed to be loaded to address 0. So the first thing the 24 bytes would do is to copy themselves into "high" memory and branch to the copy. This left room for it to load the OS. This initial c
  25. 1. This is a major upgrade. You really, really need to have a backup of your data - even if you have to borrow drives to do it on. 2. You need to check this to make sure that you are selecting the correct combination of bootloader and DSM version for your hardware. For 1.03b you need to be able to boot in csm/legacy mode. 3. I would check the updates thread for 6.2.3 to see if someone has reported a successful update for hardware the same or similar to yours 4. You need to do this before booting 6.2.3 for the first time. 5.Use the tutorial as a guide. 6. Di