Jump to content
XPEnology Community

bearcat

Member
  • Posts

    790
  • Joined

  • Last visited

  • Days Won

    26

Posts posted by bearcat

  1. For the "ease of things", do this:

     

    1 - Create a USB disk, using the correct VID/PID, and a serial + your 2 MAC' adresses, based on Jun's Loader v1.02b - DS3615xs

    2 - Manually download DSM_DS3615xs_15284.pat and verify your download.

    3 - Prepare a HDD, by deleting any existing partitions on it (from a windows PC, you can use "diskpart /clean".

    4 - Connect the "clean" HDD, ,insert the USB and boot. When you (hopefully) get to the install part, manually provide the .pat you downloaded.

    5 - When install is done, cross your fingers, reboot your system (with the USB still inserted), and post your outcome... 

    (the USB will be need to stay inside, as it will be used to boot from, allways.

    DSM wil be installed on ANY hdd in the system, using a system partition, and a swap partition, those will be RAID'ed across all the HDD's)

     

     

     

    Edit: if you just want to read the USB stick from Windows, you can use this free tool from DiskInternals

  2. Not all AMD systems play nice with XPEnology, make sure any C1E options in BIOS is disabled.

     

    1 - What exactly is the problem you have?

    2 - Do you get a link indicator on your NIC?

    3 - Any signs of your "NAS" in the log of your DHCP server?

    4 - Try to install the Jun's 1.02 / 3615xs / DSM 6.1.x combo (adding the .pat file manually).

     

     

  3. On 4/13/2020 at 4:48 AM, Nickmedia said:

    Can I install xpenology on an intel xeon e3-1225 and how can it be done 

     

    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 ;-)

     

  4. 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?

     

  5. @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.

     

     

  6. @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.

     

  7. @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.

     

  8. @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...

     

     

  9. On 3/21/2020 at 5:11 PM, Jay Y said:

     

     

    My config:

    • HBAs:
      • LSI 3008 (Built into motherboard - 8 SAS Ports)
      • LSI 3224 (LSI 9305-16i) (Add on with 64 SAS Ports)
      • LSI 3008 (Dell H330 HBA) (Add on with 8 SAS Ports)
      • Motherboard also has 10 SATA ports (Only 4 used in my config)

     

     

     

    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?

     

×
×
  • Create New...