Jump to content
XPEnology Community

Symbiot78

Member
 View Profile  See their activity

  • Posts

    30

  • Joined

  • Last visited

 Content Type 

Posts posted by Symbiot78

    virtualbox: dsm5 using nanoboot - issue with boot

    in Archives

    Posted

    sooo. .. I think I got it working...

    Annoyingly I do not know quite how..

    What I did was... try multiple versions of nanoboot..

    Then I tried the synoboot.img from this site.. still didn't work..

     

    Then I deleted all vdi files, vmdk's etc. that I tested..

     

    I then booted with nanoboot *4528

    and installed version 4528 from xpenology.nl

     

    This combo.. which I've tried before.. seems to work.

    Harddisk in Vbox is 50 Gb Sata.

    virtualbox: dsm5 using nanoboot - issue with boot

    in Archives

    Posted

    I may have found my problem..

     

    I allocated 4Gb for the syno host disk.. and this seems to have been the problem.

    I just tried allocating 200Gb (dynamically assigned) to a second disk and now it is formatting/installing... I don't really want to use 200gb nor do I want the disk to be dynamically resized but...

    will update on progress..

    virtualbox: dsm5 using nanoboot - issue with boot

    in Archives

    Posted

    Hi guys..

     

    thanks for the suggestions...

     

    so removing all ide/sata/scsi disks (only cd with nanoboot attached)

    gives me an error on the webif... no harddrives found.. so there is a difference..

     

    attaching a sata controller & satadisk.. (not ssd)

    webif recognizes 1 disk, but during initialization it fails.

     

    attaching a disk onto the ide controller where the nanoboot iso is mounted..

    error 21..

     

    scsi gives me an error 38..

    virtualbox: dsm5 using nanoboot - issue with boot

    in Archives

    Posted · Edited by Guest

    Hi

     

    I setup a VB and want to run xpenology dsm.

     

    I am using bootimage: Nanoboot-5.0.3.2 DSM 5.0-4528 X64

     

    and using dsm file: DSM 5.0-4528 (Main)

     

    both downloaded from : http://www.xpenology.nl/xpenology-software/

     

    When I boot with nanoboot and select install/upgrade the image boots but it seems to be stuck..

     

     

    image:

     

    kdl7hk.png

     

     

    I can access the webif via syno assistant but when I try to use the .pat file I get an error...

     

    What am I doing wrong?

    moving disks with raid5 from MB to raid ctrl

    in Archives

    Posted

    Hi

     

    I've got a 4 disk Raid5 running on xpenology. All disks are plugged into my motherboard (mb has 4x sata)

    I am thinking that I'd gain some speed moving the 4 disks to my dawicontrol raid-controller.. which is already sitting in my server.. but just not in use..

     

    1. would I gain anything?

    2. how will the raid5 filesystem react to being moved from what I assume is software raid to hardware raid?

    3. is it important that disk1 is plugged into port 1 of the raidcontroller (etc)

     

    Hope you guys can give some advice :smile:

    [HELP] - dsm5 - erratic network performance

    in Archives

    Posted

    it seems to be the read speed of the harddrives.

    it ranges from 30kb/s to 15mb/s sometimes higher..

    If I start a copy of many/larger files it will start in the mb/s then drop to kb/s then eventually.. after around 10-30mins.. the xpenology box will die and I can no longer get in contact with it without turning off the main power for the server and back on again.

    [HELP] - dsm5 - erratic network performance

    in Archives

    Posted

    Hi

     

    I've just installed the dsm5 beta xpenology.

     

    When copying/moving files between the xpenology install and my standard synology 412+ I get really erratic performance. speed goes up and down. mostly down.

    I am running raid5 on both boxes and both have 4x3Tb disks.

     

    Same if I mount the xpenology as network drive on my windows PC.

    Browsing to the drive and opening a video file for instance.. is almost impossible ... it hangs and hangs and hangs..

     

    I've tried the xpenology before and had no issues..

     

    I had the same result on the newest 4.3 from xpenology.

     

    Any ideas?

    Drivers requests for DSM 5.2

    in DSM 5.2 and earlier (Legacy)

    Posted

    Symbiot78 wrote:

    Am I correct when reading the changelog that you didn't add support for the dawicontroller yet?

     

     

    No sorry, can you repost me the driver link.

     

    I have a raidcontroller from Dawicontrol.. ds-624e.. it uses a Marvell 9230 chip.

    Any chance for support on this?

     

    Just found this for your controller:

    http://ubuntu.5.x6.nabble.com/3-8-y-z-e ... 50287.html

    http://www.spinics.net/lists/linux-ide/msg46859.html

     

    I will patch the kernel with their informations in order to handle Marvell 9230 chip.

     

    Hi Trantor..

     

    All I have is this..

    I tried adding the driver with:

     

    echo 1b4b 9230 > /sys/bus/pci/drivers/ahci/new_id

     

    which worked.. I think...

     

    but as you commented.. it's not reboot proof.. :-|

    Drivers requests for DSM 5.2

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi Trantor..

     

    Perfect...

     

    I don't know if I did anything yesterday... I did fiddle around alot trying in complete noob style to figure out how to add the driver...

    but.. today when I logged in to xpenology dsm .. the disks were present..

     

    Dunno how.. or if it just kindda came online..

     

    the only thing that I did really was try this:

     

    Hello,

     

    The Marvell 9230 controller should be loaded via the Linux AHCI driver.

     

    Can you run the following command and check to see if the controller is listed.

     

    sudo lspci | grep -i Marvell

    Output:

    05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 08)

    07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)

     

    If you see something similar to the above, run this command here:

     

    sudo echo 1b4b 9230 > /sys/bus/pci/drivers/ahci/new_id

     

    The two values listed above are the vendor and product id for the controller and there is a space between those two values. After running the above command, run the below.

     

    dmesg |grep sd

     

    Check to see if any new disks are detected.

     

    which I did .. i didn't find the exact phrasing: SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 08)

    but something like 88SE9172 and I tried adding it with the echo 1b4b etc etc..

     

    but after I rebooted.. nothing showed in dsm..

     

    So maybe something is already present that recognizes the controller.. but I think.. if you can find something proper.. then that would be a lot more reliable..

     

    Thanks for your great work!

    Drivers requests for DSM 5.2

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi Trantor..

     

    Perfect...

     

    I don't know if I did anything yesterday... I did fiddle around alot trying in complete noob style to figure out how to add the driver...

    but.. today when I logged in to xpenology dsm .. the disks were present..

     

    Dunno how.. or if it just kindda came online..

     

    the only thing that I did really was try this:

     

    Hello,

     

    The Marvell 9230 controller should be loaded via the Linux AHCI driver.

     

    Can you run the following command and check to see if the controller is listed.

     

    sudo lspci | grep -i Marvell

    Output:

    05:00.0 SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 08)

    07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)

     

    If you see something similar to the above, run this command here:

     

    sudo echo 1b4b 9230 > /sys/bus/pci/drivers/ahci/new_id

     

    The two values listed above are the vendor and product id for the controller and there is a space between those two values. After running the above command, run the below.

     

    dmesg |grep sd

     

    Check to see if any new disks are detected.

     

    which I did .. i didn't find the exact phrasing: SATA controller: Marvell Technology Group Ltd. Device 9230 (rev 08)

    but something like 88SE9172 and I tried adding it with the echo 1b4b etc etc..

     

    but after I rebooted.. nothing showed in dsm..

     

    So maybe something is already present that recognizes the controller.. but I think.. if you can find something proper.. then that would be a lot more reliable..

     

    Thanks for your great work!

×
×
  • Create New...