WD Sentinal DS5100 Xpenology


Recommended Posts

I got at auction a WD Sentinal DS5100 wich has a  Xeon E3-1220Lv2 dual core processor, four bays that can run up to 4 x 2TB drives. Specs can be found here. Where do I start to get a workinf Xpenology? I have no clue bootloader and model>?>?>?

Link to post
Share on other sites
1 hour ago, kbtarl said:

workinf Xpenology

maybe boot a rescue/live linux and do a "lspci -k" and post it here, that way we would see the used hardware in detail and the used drivers

 

the cpu is to old for loader 1.04b / 918+ so start with 1.03b 3617

 

beside the link from above you should read the faq

https://xpenology.com/forum/forum/83-faq-start-here/

and the tutorail made for 6.1 also applies to 6.2, with just a newer loader

https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

 

Link to post
Share on other sites

Thanks for all the help. I will run a live linux and get that data! I sure appreciate all this help. I really didnt know what I might do with this but looked like a good chance to try Xpen

 

this is what I found so you are right it is below 4th gen.......Ivy Bridge is the codename for the "third generation" of the Intel Core processors (Core i7, i5, i3).

Link to post
Share on other sites
9 hours ago, kbtarl said:

I will run a live linux and get that data!

as its hard to see what hardware was used its easier that way then just trying

 

in general the 1.03b loader needs legacy bios or csm mode if its a uefi bios

i case of uncertainty's try loader 1.02b (dsm 6.1) that one work legacy and uefi and if that checks out with drivers you can use the gained knowledge how to set up the laoder to try 1.03b again and rule out other problems with preparing the loader or drivers

 

Link to post
Share on other sites

ubuntu@ubuntu:~$ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller (rev 09)
    Subsystem: Intel Corporation Xeon E3-1200 v2/Ivy Bridge DRAM Controller
    Kernel driver in use: ie31200_edac
    Kernel modules: ie31200_edac
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
    Kernel driver in use: pcieport
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
    Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
    Subsystem: Intel Corporation 7 Series/C216 Chipset Family MEI Controller
    Kernel driver in use: mei_me
    Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller
    Kernel driver in use: serial
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
    Subsystem: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller
    Kernel driver in use: ehci-pci
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
    Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4)
    Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
    Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
    Subsystem: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller
    Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation C216 Series Chipset LPC Controller (rev 04)
    Subsystem: Intel Corporation C216 Series Chipset LPC Controller
    Kernel driver in use: lpc_ich
    Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
    Kernel driver in use: ahci
    Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
    Subsystem: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller
    Kernel driver in use: i801_smbus
    Kernel modules: i2c_i801
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller
01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller (rev c3)
    Subsystem: Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller
    Kernel driver in use: mvsas
    Kernel modules: mvsas
02:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02)
03:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21)
    Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family
    Kernel driver in use: ast
    Kernel modules: ast
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: Intel Corporation 82574L Gigabit Network Connection
    Kernel driver in use: e1000e
    Kernel modules: e1000e
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: Intel Corporation 82574L Gigabit Network Connection
    Kernel driver in use: e1000e
    Kernel modules: e1000e
ubuntu@ubuntu:~$

 

 

Thanks for all the help! Why are HDD capped at 2TB? Can that be upgraded?

 

 

Link to post
Share on other sites
1 hour ago, kbtarl said:

00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
    Kernel driver in use: ahci
    Kernel modules: ahci

00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
    Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller
01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller (rev c3)
    Subsystem: Marvell Technology Group Ltd. 88SE9480 SAS/SATA 6Gb/s RAID controller
    Kernel driver in use: mvsas
    Kernel modules: mvsas

 

storage is ok, ahci will work ootb

mvsas will need additional drivers (extended extra.lzma)

https://xpenology.com/forum/forum/91-additional-compiled-modules/

 

 

1 hour ago, kbtarl said:

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: Intel Corporation 82574L Gigabit Network Connection
    Kernel driver in use: e1000e
    Kernel modules: e1000e
05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: Intel Corporation 82574L Gigabit Network Connection
    Kernel driver in use: e1000e
    Kernel modules: e1000e

 

as normal as it could be, not probles at all, driver works ootb with the loader

 

1 hour ago, kbtarl said:

Thanks for all the help! Why are HDD capped at 2TB? Can that be upgraded?

 

there should not be a limit like this, the only controller/chip with a hardware limit i kow about is lsi sas 1068

not heard anything about a limit with marvell controllers and the chipsset ahci does not have that either

 

i'd suggest trying with one disk on a sata port of the chipset, that way you dont need a extra.lzma yet, that can be added later

if there is a bios and its uefi you would need to enable csm, if its a legacy bios you can leave things as they are for now

try 1.03b 3617, it it does not show up in network try 1.02b

if 1.02b does and .1.03b does not show up in network then it will be a uefi/csm problem

you can proceed like here

https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

but you will use loader 1.03b instead and use dsm 6.2.3

 

 

 

Link to post
Share on other sites

Wanted to thank you now although I have not tried any of this yet. Mother in Law lives upstairs where bonus room ( my computer lair ) is. She is in quarantine so maybe this weekend!

 

I did get some info from a guy on reddit  which probably supports what you have told me. Dont know his specs ----

 

"Although not the exact same system, I started working on a WD Sentinel DS6100 this last weekend. Using loader 1.03b for DS3617 I'm able to boot and discover the device on the network, albeit with no drives detected. Reading around I find that I need an extra driver for the SAS controller which involves replacing the extra.lzma on the bootable USB device that I created. One hiccup for me was that Ioader 1.03b must be booted from BIOS/CSM mode and would not work in UEFI mode for me. I'm still unable to install the system, but in the 6+ hours of attempting this, those are a few things that I've learned along the way. "

Link to post
Share on other sites

I was able to get the NAS detected with 1.02b but did not see any of my drives. 1.03b was not detected. This is where I have to go in and modify the loader with the flash drive VID and PID numbers, the S/N and MAC address. How do I had the extended extra.lzma. I downloaded the extra3617_v4.8 zip.

Link to post
Share on other sites
On 1/21/2021 at 4:47 PM, kbtarl said:

Do I use drivers for the Sata or do I use an actual file extended extra.lzma?

not sure where these drivers are from (the ahci support is already part of the kernel synology delivers) and how you where intending them to use but you are supposed to use the extendet extra.lzma i linked above (what extra.lzma you hae to use depends on the loader, dsm type and dsm version)

 

On 1/20/2021 at 4:44 PM, kbtarl said:

WD Sentinel DS6100

whats the difference in hardware to the 5100 you had used above? (seems to be the same cpu generation and same storage controller so i gess no difference when it comes to choosung the loader an drivers pack)

 

On 1/20/2021 at 4:44 PM, kbtarl said:

1.03b must be booted from BIOS/CSM mode and would not work in UEFI mode for me. I'm still unable to install the system, but in the 6+ hours of attempting this, those are a few things that I've learned along the way. "

you would not just need csm mode you also need to boot from the non uefi (legacy) usb boot device (often you will see the usb drive 3 times, 2x uefi (for every partition in the usb) and one without a "uefi" in the name anr thats the one you need to choose when booting

if you cant use csm you can still get 1.02b, that does both

 

4 hours ago, kbtarl said:

This is where I have to go in and modify the loader with the flash drive VID and PID numbers, the S/N and MAC address.

 

sn and mac are not important for installing and can be changed later if needed,

 

4 hours ago, kbtarl said:

How do I had the extended extra.lzma. I downloaded the extra3617_v4.8 zip.

you extract the extra.lzma from the zip and replace the file on the second partition of the loader with the new one

 

 

Link to post
Share on other sites
On 1/22/2021 at 6:01 PM, IG-88 said:

not sure where these drivers are from (the ahci support is already part of the kernel synology delivers) and how you where intending them to use but you are supposed to use the extendet extra.lzma i linked above (what extra.lzma you hae to use depends on the loader, dsm type and dsm version)

 

whats the difference in hardware to the 5100 you had used above? (seems to be the same cpu generation and same storage controller so i gess no difference when it comes to choosung the loader an drivers pack)

 

you would not just need csm mode you also need to boot from the non uefi (legacy) usb boot device (often you will see the usb drive 3 times, 2x uefi (for every partition in the usb) and one without a "uefi" in the name anr thats the one you need to choose when booting

if you cant use csm you can still get 1.02b, that does both

 

 

sn and mac are not important for installing and can be changed later if needed,

 

you extract the extra.lzma from the zip and replace the file on the second partition of the loader with the new one

 

 

If I have the manufactures marvell drivers, can those be loaded into the loader?

Link to post
Share on other sites
7 hours ago, kbtarl said:

If I have the manufactures marvell drivers, can those be loaded into the loader?

linux is very different from windows when it comes to drivers, you would need to compile your own driver from the source, you cant just use a (binary) driver

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.