G33RT
-
Posts
10 -
Joined
-
Last visited
Posts posted by G33RT
-
-
Thank you so much for the help !
-
6 hours ago, IG-88 said:
if you already opened it you can also try to unconnect the usb dom and boot a live linux or even try to boot xpenology loader to check the network
😮 are you kidding me, you can do that !?
you mean the small print with the flash chip with the label DS1815+ on it ?
are there any tutorials (step-by-step) instructions available of this procedure ? -
16 hours ago, sbv3000 said:
a silly idea perhaps, but could you remove your raid disks, boot with no disks and see if the network is ok?
not sure of the boot process but imagine that with no disks the unit boots with dom based drivers for 'basic' connectivity, but once DSM is installed it uses drivers from the .pat file. if the DSM driver is 'corrupt' then fails to load. Above could also identify if network hardware has failed?
Next step would be to install DSM to a spare/new HDD, check that works, if so you just need to 'repair' on the raid drives
I tried that all no luck.
-
But what causing the driver to fail, that I don't understand.
I doubt that the hardware is defective, I have meassure the 3 main voltages on the Marvel chip ald these are all good.
Can I determine somehow why the driver failed to load ? -
On 4/25/2020 at 11:40 PM, sbv3000 said:
depending on your dsm version, the the 'admin/root' account will have been disabled, but you should be able to telnet/serial to the device with the account you created as your replacement 'admin' account and its password. you might be able to get a basic network connection with a wifi dongle add on, to help diagnostics, or backup
I have managed to login with names as admin as also root via the serial console.
Don't now if I realy have root access though !?
Unfortunately it synodsdefault does not work as it is not in /usr/syno/sbin/Can someone advice my how to factory reset this box by command as it is not possible by reset switch.
23 hours ago, IG-88 said:thats a PHY chip also used on intel based nic's, its referenced in trh igb driver source to i guess igb.ko is ok for your unit
Okay, so it is infact an intel driver for that Marvell chip, I dident know that.
my linux knowledge is limited, can you suggest something i can try?
-
Hi,
Does anyone happen to know the Login & Password when connect via serial console ?
My DS1815+ does have no ethernet anymore.
It gives a failure when loading the 4-Port Ethernet driver and I like to try fix this.
And Yes, I already tried in Syno-forum's but no help from there.This is the error I get:
:: Loading module igb[ 14.128354] Intel(R) Gigabit Ethernet Network Driver - version 5.3.5.3 [ 14.135657] Copyright (c) 2007-2015 Intel Corporation. [ 14.141711] igb 0000:00:14.0: Hardware Initialization Failure [ 14.148195] igb: probe of 0000:00:14.0 failed with error -5 [ 14.154666] igb 0000:00:14.1: Hardware Initialization Failure [ 14.161155] igb: probe of 0000:00:14.1 failed with error -5 [ 14.167622] igb 0000:00:14.2: Hardware Initialization Failure [ 14.174112] igb: probe of 0000:00:14.2 failed with error -5 [ 14.180572] igb 0000:00:14.3: Hardware Initialization Failure [ 14.187061] igb: probe of 0000:00:14.3 failed with error -5
The strange thing is that it load an Intel driver but the DS1815+ has an Marvell Alaska 88E1543-LKJ2 Chip for the ethernet.
Any info that may help, please !
-
Thank you for your suggestion but would it not be more quicker to install a new XPEnology?
-
Do you now how to replace the loader from 1.02a to 1.02b on ESXi ?
Or do you recommend a new install?
-
Hi ya all,
I'm new to ESXi and XPEnology and mabe someone here can help me out with my problem.
I have the problem that none of my harddisks are vissable in XPEnology Storage Manager.
The SATA controller is setup as passthrough in ESXi 6.5
This is my setup:
2x Xeon L5640 @ 2.27GHz 64GB 1333MHz RAM 2x 250GB SanDisk NGFF SSD
LSI SAS9201-16i 16-Port SAS/SATA controller (the card is set passthrough in ESXi)
Software = ESXi 6.1 Update-1
XPEnology 6.1 DS3615xs 6.1 Jun's Mod V1.02-alpha
Is there something I have to do to make XPEnology recognise all de harddisks that are connected to the SATA controller?
Could it be that it is driver related, however I have read that my SATA controller 9201-16i is compatible http://xpenology.me/compatible/
Any help on this is greatly appriciated.
Thanks in advance!
Login & Password for DS1815+ connect via serial console ?
in Software Modding
Posted
After thoroughly inspecting the motherboard, I found a component around the Marvell chip that has partly come loose.
The component description says "CE5"
After a re-soldering, the device works again.
Now the NIC boot looks like this:
[ 26.221643] Intel(R) Gigabit Ethernet Network Driver - version 5.3.5.3
[ 26.228957] Copyright (c) 2007-2015 Intel Corporation.
[ 27.588010] igb 0000:00:14.0: added PHC on eth0
[ 27.593104] igb 0000:00:14.0: Intel(R) Gigabit Ethernet Network Connection
[ 27.600815] igb 0000:00:14.0: eth0: (PCIe:integrated:integrated)
[ 27.607667] igb 0000:00:14.0 eth0: MAC: 00:a0:c9:00:00:00
[ 27.613793] igb 0000:00:14.0: eth0: PBA No: 002100-000
[ 27.620377] igb 0000:00:14.0: LRO is disabled
[ 27.625257] igb 0000:00:14.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 28.986059] igb 0000:00:14.1: added PHC on eth1
[ 28.991141] igb 0000:00:14.1: Intel(R) Gigabit Ethernet Network Connection
[ 28.998899] igb 0000:00:14.1: eth1: (PCIe:integrated:integrated)
[ 29.005727] igb 0000:00:14.1 eth1: MAC: 00:a0:c9:00:00:01
[ 29.011858] igb 0000:00:14.1: eth1: PBA No: 002100-000
[ 29.018457] igb 0000:00:14.1: LRO is disabled
[ 29.023330] igb 0000:00:14.1: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 30.385164] igb 0000:00:14.2: added PHC on eth2
[ 30.390255] igb 0000:00:14.2: Intel(R) Gigabit Ethernet Network Connection
[ 30.397964] igb 0000:00:14.2: eth2: (PCIe:integrated:integrated)
[ 30.404797] igb 0000:00:14.2 eth2: MAC: 00:a0:c9:00:00:02
[ 30.410922] igb 0000:00:14.2: eth2: PBA No: 002100-000
[ 30.417495] igb 0000:00:14.2: LRO is disabled
[ 30.422374] igb 0000:00:14.2: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[ 31.783311] igb 0000:00:14.3: added PHC on eth3
[ 31.788409] igb 0000:00:14.3: Intel(R) Gigabit Ethernet Network Connection
[ 31.796115] igb 0000:00:14.3: eth3: (PCIe:integrated:integrated)
[ 31.802940] igb 0000:00:14.3 eth3: MAC: 00:a0:c9:00:00:03
[ 31.809058] igb 0000:00:14.3: eth3: PBA No: 002100-000
[ 31.815634] igb 0000:00:14.3: LRO is disabled
[ 31.820510] igb 0000:00:14.3: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)