bearcat

As mentioned above: Seems like Seagate has been shipping some Barracudas with the same "problem". (SMR) Check out your models in case they are some of those.

@viktortrass How do you connect to it remotely, and what protocol are you using for the transfers?

@jocacoca Seems like I was replying, without bringing my brain sorry for the confusion. The J1800 is just like the J1900 based on the "Bay Trail". I installed 918+ on a J1900 board, so it should work on a J1800 as well

Let me be a sarcastic nitpicker, and answer this: NO, there is no way to install xpenology on a CPU. 🙄 In the topic, you mention a server, that server might have this specific CPU installed, but what is more important for us to know (to be able to help you) is the make and model of the server, more specifically the mainboard in use, what NIC and SATA controllers you have on this mainboard. If you come back, with this info, you may get the answer you might be looking for. You may also want to read some FAQ and tutorials to prepare for this journey

OK, if 6.1.7 works, you may stay with it for now I guess The few times i have seen that type of error, it has either been due to wrong vid/pid or existing filesystem (NTFS or others) on the disk's beeing used (as I remember). (Your drives are in AHCI mode, else they would not be found I guess) If the VID/PID is correct, and the drives has allready been in use with DSM, and DSM 6.1.x works, it sounds like either the .PAT file used (download again and do a checksum test) or a driver is causing the problem?

nevermind..

@merve04 I might have missed it, but what type of drives are you using? I came across this article today, and it made me think twice...

@bnicolae and @Artem_01 I was not paying attention to that "small detail" in regards to disabling C1E in the BIOS, bnicolae asked if he could install 6.2 without *changing* the BIOS, and he could do so. (most microservers are run with hacked/modified BIOS and the you need to *change* or upgrade your BIOS. Changing a setting, as in disabling the C1E, I read as something else. Besides, that has been mentioned in several threads and tutorials so I assumed you had read it allready.

@jocacoca Your CPU is to old to be used with 918- (look it up) Try this combo: (with no extra's) Loader: DS3615xs 6.1 Jun's Mod V1.02b DSM: 6.1.4-15217 (add the .pat manually) Report back on the outcome.

@Cubitus Your CPU is too old to use with the 918+ setup, (look it up). Now, the question is, what make/model is the NIC you have, and what driver does it support? Best choice for you, is to start with the 3615+ and DSM 6.1.x (Jun's 1.02b and manually supply the .pat file). If that works, great you may then try with the 6.2.x if you want to test if it's compatible. Edit: do not use any RAID options on your SATA ports/cards, only AHCI, let DSM do any RAID you want/need.

@binarybrain have you solved this yet? It might be sorted out, if you still suffer.

1 - is the VID/PID correct according to your USB? 2 - is the HDD(s) the same as you have used before?

@Pauman If you want to clean the WD drive, and loose ALL info/files on it, you may do so with a windows computer. Connect the drive, open a command promt (run as admin). Type in: diskpart (then press Enter..) Type in: list disk (then press Enter..) (identify your WD USB disk) Type in: select disk "X" (then press Enter..) (where "X" is the Disk number for your USB disk, please double/tripple check you have the right disk) Type in: clean (then press Enter..) (this is a quick deletion of ALL your drives partitions (and files), optional use: clean /all (takes longer time). Type in: exit (then press Enter..) Type in: exit (then press Enter..) Run: diskmgmt.msc and create any new partitions you want, and then format the partition(s). Result: An empty WD element disk, ready to be used.

@bnicolae Basically, thats what I'm saying, but be warned that any updates will brick your system (unless you modify your bootloader with extra drivers).

@wanye I might be wrong, as my new glasses are in quarentine, but I sptted this line from your log " request: "GET /webman/index.cgi HTTP/1.1", upstream: "scgi://unix:/run/synoscgi.sock:", host: "192.168.1.253:5000""" Is your service trying to run on the same default port as your DSM interface? That will crash... (I guess)

I might be totally off-topic, but did your DSM 5.2 use the "xpenoboot" bootloader? If so, you are now using Jun's bootloader? Then, you might as well look for, and delete the xpenoboot folder (sudo rm -r .xpenoboot), as that is known to cause funky sh*t.

Did your old running config have any updates installed after first time setup? That could explain the message you got. What bootloader do you use?

1 - Do you have Plex pass? 2 - What GPU do you have?

Is that "DSM 6.1.4-15217 Update 1" the one you placed on your new USB? What was your old running config using?

@zzgus As long as you don't "expose" it to internet, by manually open ports, or trusting UPpN on your router, there should not be a direct way "in". That beeing said, your connected computer, with the current user rights, have access to your NAS and your files... Stay safe, and use normal common sense, do not click on "funky" stuff ransomware might encrypt the files on your fileshares...

Just out of curiosity, if one of your HBA's have 64 SAS ports, why do you use any of the others? btw: are they all in IT-mode?

@Riis : No problem, just stop by my house tonight and pick it up But seriously, why would you use a Unifi XG for this project? What driver do you need for the NIC's and storage?

@MichaelMEIB : Have you found your sollution yet? In Win 10, you may map a network drive just make sure you have a user/password with read/write acces to the share.

@merve04 So, how is it going, are your new volumes expanded. and in use yet?

@pasdum: 1. SSH into your NAS 2. Log On with your Admin/Root Account or User Account 3. If User Account then type sudo -i and enter the Admin/Root Password 4. Type ls -la / 5. You should see a folder called .xpenoboot 6. sudo rm -rf /.xpenoboot 7. Type ls -la / to check it is removed 8. Reboot your NAS by typing reboot