Jump to content
XPEnology Community

DSM 6.1.x Loader


jun

Recommended Posts

I noticed something strange after upgrading to DSM6. The volume / disk group name changed to reuse_1. This only shows in the DS Finder app, not through the web interface.

Yes. On my two servers is the same record "reuse_1" in the DSFinder. Strange that so?

 

Well before upgrading to DSM 6 it was written "Volume 1". So I just wonder why that changed and if it has any implications on the volume.

Link to comment
Share on other sites

Reformat your volume in brtfs after the upgrade.

Ouch... all my data in the old version will be deleted, right? :sad:

Copy your data to another system or other drives. If you don't have, recommend purchasing drives. It's good to have spare copies.

Sent from my SM-N930T using Tapatalk

I back up my documents, photos, music and family videos to BluRay occasionally too..

I have on an external USB3 disk for backups as well..

 

Once I think this 'hack' is stable on my server, I'll begin to use it (it'll have 4x 3TB drives when I move my other 2 disks into it).. To be honest, it seems fine as it is (and it's only pulling about 35Watts). :smile:

My 216J synology will then be relegated to my backup device. I'll put an old 1TB drive in it and use it as a security camera drive. A second 5TB drive will be for backups across the LAN. Hoping you can have 2 independent disks in it (haven't checked that yet).

 

#H

Link to comment
Share on other sites

I love popping into fantastic news and really looking forward to testing this out on my system.

 

My current specs are;

 

P8Z68-V/GEN3 Motherboard

i7-2600k CPU @ 3.4Ghz

16GB RAM

2 x PERC H310 crossflashed to LSI-9211-8i IT Mode

7 x WD Red 3TB

All in a Rosewill 4U 15 bay chassis.

 

Congratulations on the great work, I will be here on the edge of my F5 key haha.

Link to comment
Share on other sites

Can anybody confirm if the Marvell 88SE9215 chipset is supported with this loader? I just did a migrate from 5.2 on my 8-disk box and it only sees 4 of my disks. I'm guessing this is a driver that needs to be added in and I jumped the gun. Can anybody confirm this? I've never compiled a driver so if anybody has any tips or guides on what, if anything, I can do I would greatly appreciate it!

 

Marvell 88SE9235 is working fine, take care you've to update the .cfg file in order to support number of disks you've connected :idea:

Link to comment
Share on other sites

I was wondering how to change vid/pid. I'm facing same issue. :cry:

 

i used a ubuntu live for this.

you will find a grub.cfg file in folder grub on one of the partitions. edit vid/pid and it will install.

jun describes how to find vid/pid of your usb device on first page.

 

Sorry to be bit stupid, but how you was able to update the grub.cfg ?

 

I managed to work as baremetal but not in Esxi

 

I tried to boot on an Ubuntu live in a VM I mapped the synoboot.vmdk file, but Ubuntu shows me an empty volume of 20 Mb ... :sad:

 

Thanks for your support !

Edited by Guest
Link to comment
Share on other sites

Can anybody confirm if the Marvell 88SE9215 chipset is supported with this loader? I just did a migrate from 5.2 on my 8-disk box and it only sees 4 of my disks. I'm guessing this is a driver that needs to be added in and I jumped the gun. Can anybody confirm this? I've never compiled a driver so if anybody has any tips or guides on what, if anything, I can do I would greatly appreciate it!

 

Marvell 88SE9235 is working fine, take care you've to update the .cfg file in order to support number of disks you've connected :idea:

 

‪Very interesting. When I had originally specified my disk count "SataPorts=8" I was getting the error stating 4 disks were missing. I'm running the legacy bios (hybrid uefi) booter posted a couple pages back. There was a note that mentioned something like "if booting legacy, SataPorts amendment is not necessary." So when I removed that line it was able to boot up without an error...but it also booted up without four of my disks being detected.‬

 

‪DSM 6 installed quickly and I was able to log in normally after it completed but was greeted with "volume crashed" and only four disks showing.‬

 

‪Any ideas? So glad to know it's not a driver issue!‬

Link to comment
Share on other sites

You may use this command and see what your drive status is. SSH in, then try "dmesg | grep -i sata" .. Shown below is what is displayed on my motherboard with 4 drives ..

 

root@Test-NAS48:~# dmesg | grep -i sata
[    0.000000] ACPI: SSDT 00000000da855160 0036D (v01 SataRe SataTabl 00001000 INTL 20091112)
[    1.714738] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[    1.735885] ata1: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06100 irq 43
[    1.735888] ata2: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06180 irq 43
[    1.735891] ata3: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06200 irq 43
[    1.735893] ata4: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06280 irq 43
[    1.735896] ata5: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06300 irq 43
[    1.735898] ata6: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06380 irq 43
[    2.040861] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.385017] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.891275] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.228402] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.565556] ata5: SATA link down (SStatus 0 SControl 300)
[    3.870696] ata6: SATA link down (SStatus 0 SControl 300)

 

It shows I have 4 drives online running at 3 Gbps. The motherboard has 6 satas port but I am only using 4. The command should give you a little more info to troubleshoot the problem.

Link to comment
Share on other sites

Hi, i've tried the boot image on several bare metal systems. The image is the dual UEFI/Legacy on page 10. It works only on recent system, precisely only on motherboard with AHCI capability, is this normal? On recent PC with AHCI everything works well: BTRFS, snapshot, docker, ecc... on system without AHCI it say "no disk found on your ds3615xs"

 

I'm planning to build a DSM6 with an HP Microserver Gen8 but i hav not a unit to try before buy. Someone already tried this build? (bare metal of course)

 

Thanks

Link to comment
Share on other sites

Hi, i've tried the boot image on several bare metal systems. The image is the dual UEFI/Legacy on page 10. It works only on recent system, precisely only on motherboard with AHCI capability, is this normal? On recent PC with AHCI everything works well: BTRFS, snapshot, docker, ecc... on system without AHCI it say "no disk found on your ds3615xs"

 

I'm planning to build a DSM6 with an HP Microserver Gen8 but i hav not a unit to try before buy. Someone already tried this build? (bare metal of course)

 

Thanks

Hi, i have a G8 with xpenology installed, but i'm using 5.2 version and runs like a charm, i would like to install 6.0 but i gave to backup my stuff before try upgrade.

Link to comment
Share on other sites

Anyone got DLNA working yet?

Maybe I just need to be patient and let my TV find the box.. I've reduced the advertisement down to 600 (from the default) and the media is all indexed..

 

edit.. Solved. Was a TV problem. Now confirmed working fine on 6.0.2! :smile:

 

#H

Edited by Guest
Link to comment
Share on other sites

You may use this command and see what your drive status is. SSH in, then try "dmesg | grep -i sata" .. Shown below is what is displayed on my motherboard with 4 drives ..

 

root@Test-NAS48:~# dmesg | grep -i sata
[    0.000000] ACPI: SSDT 00000000da855160 0036D (v01 SataRe SataTabl 00001000 INTL 20091112)
[    1.714738] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
[    1.735885] ata1: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06100 irq 43
[    1.735888] ata2: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06180 irq 43
[    1.735891] ata3: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06200 irq 43
[    1.735893] ata4: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06280 irq 43
[    1.735896] ata5: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06300 irq 43
[    1.735898] ata6: SATA max UDMA/133 abar m2048@0xf7e06000 port 0xf7e06380 irq 43
[    2.040861] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.385017] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.891275] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.228402] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.565556] ata5: SATA link down (SStatus 0 SControl 300)
[    3.870696] ata6: SATA link down (SStatus 0 SControl 300)

 

It shows I have 4 drives online running at 3 Gbps. The motherboard has 6 satas port but I am only using 4. The command should give you a little more info to troubleshoot the problem.

 

I ran the command and it only shows four of my drives:

[    0.000000] Sata Port Map: 8
[    3.023055] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 4 ports 6 Gbps 0xf impl SATA mode
[    3.080735] ata1: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff100 irq 50
[    3.080740] ata2: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff180 irq 50
[    3.080742] ata3: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff200 irq 50
[    3.080745] ata4: SATA max UDMA/133 abar m2048@0xfe4ff000 port 0xfe4ff280 irq 50
[    3.540025] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.542020] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.543024] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.543040] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

 

Storage Manager only detects 4 disks as well, which is why it is displaying my volume as Crashed currently. Any ideas? I added the line "SataPortMap=8" into the grub.cnf and this is the same result as it was without the line added.

Link to comment
Share on other sites

Last update, and it's a happy one. I switched my RAID mode in the BIOS from legacy to AHCI and voila, my drives are all present and the RAID set has been successfully reassembled. This is a successful upgrade, bare metal, from XPE 5.2 to 6. Note: My BIOS RAID mode was originally set to legacy due to that being the only mode that all eight drives would properly detect in v5.2. Now, switched over to AHCI, everything appears to be in great shape!

Link to comment
Share on other sites

Last update, and it's a happy one. I switched my RAID mode in the BIOS from legacy to AHCI and voila, my drives are all present and the RAID set has been successfully reassembled. This is a successful upgrade, bare metal, from XPE 5.2 to 6. Note: My BIOS RAID mode was originally set to legacy due to that being the only mode that all eight drives would properly detect in v5.2. Now, switched over to AHCI, everything appears to be in great shape!

 

Glad to hear you solved your problem. I did look up the specs on the 88SE9215 and I see it only has 4 ports. So my next question was going to be, how were you able to connect 8 drives to it. The 4 on the motherboard answers my question. Anyway, I found out the hard way the Legacy Bios boot image would only recognize AHCI setup in the bios. I started with IDE and no drives were recognized.

 

I do see in your attachment that 3 of the drives seemed to be set at 1.5 Gbps vs 6.0 Gbps.

Link to comment
Share on other sites

I do see in your attachment that 3 of the drives seemed to be set at 1.5 Gbps vs 6.0 Gbps.

Yeah, I've got 7 *old* repurposed enterprise 1TB drives and one 1TB WD Blue (the 6gbps drive). These drives perform wonderfully for me and are so fast that my only bottleneck is the 1GB pipe it is connected to.

 

My current report shows:

 

[    3.477028] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.478032] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.479021] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.480026] ata6: SATA link down (SStatus 4 SControl 300)
[    3.480053] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.670030] ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.670061] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.671019] ata11: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.672016] ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

 

I'm curious what ata6 is though. I just left the house so I can't verify, but I'm wondering if eSATA got re-enabled in the BIOS. That would explain why my drives are numbered 1,2,3,4,9,10,11,12 again...super annoying for OCD but I'm glad it's functioning again. Last time the drives showed in this order eSATA was enabled and for some reason DSM is reserving 5,6,7,8 for that port. Disabling eSATA and switching the RAID mode to legacy was what got my drives listed in a 1-8 order last time.

Link to comment
Share on other sites

Hi, i've tried the boot image on several bare metal systems. The image is the dual UEFI/Legacy on page 10. It works only on recent system, precisely only on motherboard with AHCI capability, is this normal? On recent PC with AHCI everything works well: BTRFS, snapshot, docker, ecc... on system without AHCI it say "no disk found on your ds3615xs"

 

I'm planning to build a DSM6 with an HP Microserver Gen8 but i hav not a unit to try before buy. Someone already tried this build? (bare metal of course)

 

Thanks

Hi, i have a G8 with xpenology installed, but i'm using 5.2 version and runs like a charm, i would like to install 6.0 but i gave to backup my stuff before try upgrade.

 

Hi Aigor, good to know, in italy the price of microserver with 4gb ram is 190€, not a big investment, but if i can be sure it works before purchase i don't waste money :smile: let me know if you are planning to update in the near future. Thanks

Link to comment
Share on other sites

It is probably an esata port being recognized. It does show nothing connected to the port .. another command you can use to show more information on your drives is ...

 

smartctl -d ata -i /dev/sd(N) .. where N is a letter for each of your disks. They get remapped from ata1, ata2, ata3, etc. to sda, sdb, sdc, etc.

 

root@Test-NAS48:~# smartctl -d ata -i /dev/sdb
smartctl 6.5 (build date Aug  2 2016) [x86_64-linux-3.10.77] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Samsung SpinPoint M8 (AF)
Device Model:     ST1000LM024 HN-M101MBB
Serial Number:    S2TPJACC846912
LU WWN Device Id: 5 0004cf 208441a59
Firmware Version: 2AR10001
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Oct  5 16:36:18 2016 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

 

I am testing using 2.5 in drives vs 3.5

Link to comment
Share on other sites

Thanks for feedback jun. I changed the console output on the following service only ... /usr/share/init/syno_poweroff_task.conf:console output ... from "console output" to "console none". After reboot the error of "improper shutdown" is gone.

 

I feel like I'm missing something very simple...would you tell just how you made this change?

Link to comment
Share on other sites

I tried the ovf (both v10 and v11) in esxi 6.0u2 on a gen8 microserver; I can install and create volumes but fail to add an existing RDM. I tried using vsphere and the embeded client, error in both.

I need to use the RDM's that I have now working in dsm 5. Do I need to do something to get this working or this is it for now ?

Link to comment
Share on other sites

Got this up and running on an older pc with the idea that I can move it to my parents house and have an off site backup of my ds1513+. One issue I ran into was the ds3615xs no longer supports shr in dsm 6.0 when making new volumes, and for me that has got me stuck in my tracks. I'm planning on using a pile of my old hdds to get my total space and they are of various sizes. As I understand this is a dynamic patcher correct? What is the likelihood that this would work on a system that still supports shr? I would use the corresponding pat and change sn and model number in grub.cfg of course. I was going to try this, but am currently still testing as it is for stability, and didn't feel like clearing the whole thing out in the middle of that and messing it up if it flat out won't work from the git go. Any thoughts or guidance would be super helpful. Thanks to all that have worked on this!

Link to comment
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.

×
×
  • Create New...