Benoire
-
Posts
239 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Benoire
-
-
15 minutes ago, flyride said:
When you say "not verify" can you be specific as to what the error message is? Are you familiar with FixSynoboot?
haha oops, I forgot to install this! I'm looking at moving from my baremetal install to esxi hosted for reasons and haven't played with the esxi hosted version for years... the working test had the fix installed but didn't have changes to the sata args... Thank you for reminding me all working now
-
On 12/17/2020 at 6:19 AM, flyride said:
DiskIdxMap=0C00 ought to fix your drive numbering problem then. You should use a SATA controller for disk #2, not PVSCSI.
So I did this and it hid the drive as expected but attempting to update to the latest DSM 6.2.3-25426 update 3 causes the pat file to not verify; no matter what I do I cannot update a new installation of DSM to update 3... The only one that will is the bog standard ESXi install approach that leaves drive 1 of the 12 occupied by the 50MB boot drive.
Any way around this?
-
On 10/20/2018 at 3:36 AM, flyride said:
In addition to bricked boxes due to inattentive upgrades, there seems to be a surge of questions regarding how to select a DSM platform, version and loader.
I created this table to help navigate the options and current state of the loaders. While situations rapidly change, this should be correct as of the listed date.
6.x Loaders and Platforms as of 20 Oct 2018 Loader Platform DSM version Kernel DSM /dev/dri support DSM NVMe cache support Boot method NIC 6.2.1+ CPU Requirement 1.03b DS3615 or
DS36176.2+ 3.10 No No Legacy BIOS only Intel (baremetal)
e1000e (ESXi)Sandy bridge equivalent or later I'm running my baremetal on a Westmere Xeon L5630 using the 1.03b loader on 6.2; westmere was the generation before Sandy Bridge.
-
I'm currently thinking about virtualising my server again as I've been using VMM and its pretty poor compared to ESXi. I edited the grub.cfg to boot from ESXi effectively and created the vmdks. The loader works and I can install DSM to the test drive I created, however it is shown starting at drive bay 9. This appears to be because you have to boot the loader using SATA not parallel and so it counts any sata ports in ESXi as available.
My sataportmap config was set to 88 as that is currently what the baremetal is using the 2 LSI cards but I wonder if it should in fact be sataportmap = 088 as that would give the first controller 0 ports and then allow my SAS HBAs to take the first set of slots, would that work? I'm in a test environment so can play around lots but would like to resolve this prior to the weekend.
Any thoughts are appreciated.
Chris
-
Hi
Posted this in the general questions of post installation but perhaps it is better here:
I've got the latest boot image and DSM running on my Supermicro X8DTL-iF setup. I'm trying to trim my power consumption and have decided to gut my R710's of their memory to support the all in one approach. I had 32GB of DDR3 RDIMMs installed in a 2 x 16GB config, with a single spare memory slot, this worked well and had no issues. I took another matching 16GB stick and put it in the spare slot but upon rebooting, DSM is still only showing 32GB of Ram which is confirmed using TOP in the CLI. Does the 3615xs image max out at 32GB like the actual proper unit; I wouldn't have thought so but I've never tried to take it further.
Anyone got any thoughts?
Thanks,
Chris
-
Hi
I've got the latest boot image and DSM running on my Supermicro X8DTL-iF setup. I'm trying to trim my power consumption and have decided to gut my R710's of their memory to support the all in one approach. I had 32GB of DDR3 RDIMMs installed in a 2 x 16GB config, with a single spare memory slot, this worked well and had no issues. I took another matching 16GB stick and put it in the spare slot but upon rebooting, DSM is still only showing 32GB of Ram which is confirmed using TOP in the CLI. Does the 3615xs image max out at 32GB like the actual proper unit; I wouldn't have thought so but I've never tried to take it further.
Anyone got any thoughts?
Thanks,
Chris
-
So you don't need a valid synology serial number to use plex hw transcoding if the cpu is supported?
-
8 hours ago, toker said:
I am running DSM 6.2 with LSI 9207-8i
I have modified the drive mapping / enumeration configuration on the LSI HBA from 'Auto' to 'Narrow' using 'lsiutil.efi' under Option 13.
My drive enumeration on the LSI HBA is correct when connected to SAS Backplanes but not when directly connected to SATA Drives using a break-out cable.
The numbering is in reverse order from the break-out cable when connect directly to a SATA drive, my cable is labelled P0 - P3 (P3 is now Slot0, P2 is Slot1, P1 is Slot2 & P0 is Slot3)
LSI HBA Configuration
Before
SATA Maximum Queue Depth: [0 to 127, default is 32] Device Missing Report Delay: [0 to 2047, default is 0] Device Missing I/O Delay: [0 to 255, default is 0] PhyNum Link MinRate MaxRate Initiator Target Port 0 Enabled 1.5 6.0 Enabled Disabled Auto 1 Enabled 1.5 6.0 Enabled Disabled Auto 2 Enabled 1.5 6.0 Enabled Disabled Auto 3 Enabled 1.5 6.0 Enabled Disabled Auto 4 Enabled 1.5 6.0 Enabled Disabled Auto 5 Enabled 1.5 6.0 Enabled Disabled Auto 6 Enabled 1.5 6.0 Enabled Disabled Auto 7 Enabled 1.5 6.0 Enabled Disabled Auto Select a Phy: [0-7, 8=AllPhys, RETURN to quit] 0 Link: [0=Disabled, 1=Enabled, default is 1] MinRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 0] MaxRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 1] Initiator: [0=Disabled, 1=Enabled, default is 1] Target: [0=Disabled, 1=Enabled, default is 0] Port: [0 to 7 for manual config, 8 for auto config, default is 8]
After - LSIUTIL - Option 13 - Port configuration: [1=Auto, 2=Narrow, 3=Wide, or RETURN to not change](Drive# matches physical slot#, abeit in reverse order - P3 is Slot0, P2 is Slot1, P1 is Slot2 & P0 is Slot3)
SATA Maximum Queue Depth: [0 to 127, default is 32] Device Missing Report Delay: [0 to 2047, default is 0] Device Missing I/O Delay: [0 to 255, default is 0] PhyNum Link MinRate MaxRate Initiator Target Port 0 Enabled 1.5 6.0 Enabled Disabled 0 1 Enabled 1.5 6.0 Enabled Disabled 1 2 Enabled 1.5 6.0 Enabled Disabled 2 3 Enabled 1.5 6.0 Enabled Disabled 3 4 Enabled 1.5 6.0 Enabled Disabled 4 5 Enabled 1.5 6.0 Enabled Disabled 5 6 Enabled 1.5 6.0 Enabled Disabled 6 7 Enabled 1.5 6.0 Enabled Disabled 7 Select a Phy: [0-7, 8=AllPhys, RETURN to quit] 0 Link: [0=Disabled, 1=Enabled, default is 1] MinRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 0] MaxRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 1] Initiator: [0=Disabled, 1=Enabled, default is 1] Target: [0=Disabled, 1=Enabled, default is 0] Port: [0 to 7 for manual config, 8 for auto config, default is 8]New LSI Custom Mappings:
(Drive# matches physical slot#, P0 is now Slot0, P1 is Slot1, P2 is Slot2 & P3 is Slot3)
SATA Maximum Queue Depth: [0 to 127, default is 32] Device Missing Report Delay: [0 to 2047, default is 0] Device Missing I/O Delay: [0 to 255, default is 0] PhyNum Link MinRate MaxRate Initiator Target Port 0 Enabled 1.5 6.0 Enabled Disabled 7 1 Enabled 1.5 6.0 Enabled Disabled 6 2 Enabled 1.5 6.0 Enabled Disabled 5 3 Enabled 1.5 6.0 Enabled Disabled 4 4 Enabled 1.5 6.0 Enabled Disabled 3 5 Enabled 1.5 6.0 Enabled Disabled 2 6 Enabled 1.5 6.0 Enabled Disabled 1 7 Enabled 1.5 6.0 Enabled Disabled 0 Select a Phy: [0-7, 8=AllPhys, RETURN to quit] 0 Link: [0=Disabled, 1=Enabled, default is 1] MinRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 0] MaxRate: [0=1.5 Gbps, 1=6.0 Gbps, default is 1] Initiator: [0=Disabled, 1=Enabled, default is 1] Target: [0=Disabled, 1=Enabled, default is 0] Port: [0 to 7 for manual config, 8 for auto config, default is 8]My DSM 6.2
Drives 1- 4 connected Onboard Intel SATA Controller
Drives 5 - 7 connected LSI 9207-8i (I only have 3 drives connected currently)
- Before LSI HBA modification - any drive on the LSI HBA would be automatically assigned the next free Drive# no matter which Physical Slot the drive was installed)
- After LSI HBA modification the drives are assigned the drive# which matches physical slot#
Cool, I've got a Supermicro 16 bay chassis with backplane and 2 x lsi cards. Will see how this works out!
-
Hi
I'm running DSM6.2 using the 3615xs loader with 2 LSI 9211-8i's in IT mode giving me access to the full 12 drives supported out of the box by the DSM version. Being a SAS card, we lack the enumeration of the official boxes with SAS HBAs leading to discs being shown in the wrong bays (e.g. DSM bay 7 = bay 12 physica).
I'm not in need of SAS drive usage and wonder whether I can actually get proper drive bay enumeration with a SATA only card(s) that can give me a total of 12 ports. The motherboard is an X8DTL by supermicro and has only SATA2 so would rather use an addin card.
Are there any SATA cards that are a) supported by the latest loaders and b) enumerate drives in the correct order they are connected? I use a spreadsheet at the moment, but it would just be easier!
Thoughts or just barking up the wrong tree?
Thanks,
Chris
-
On 8/24/2018 at 9:48 PM, bearcat said:
Unless its changed, the loader is simply a way to get the DSM version running on your own hardware. The 361x versions are 12 bay devices and will always update like that unless there is something in the loader like the 918+ does to get it to 12 bays. If you expand, via the config, the bays to 16 the config will always be overwritten on an upgrade and drop back to 12 and if you have more than 12 disks it will cause array issues as it won't load all disks. I was rather hoping that instead of this constant editing of the config we could have another image based on the 16 bay devices; this could either be a 16 bay 361x vesion or the true synology ones.
Yes, perhaps I'm being lazy but I also don't want to put my array at risk on updates beyond what I normally have with the loaders.
-
2
-
-
@jun Appreciate the hard work in this as well as your time and effort. Are you able to create versions of the loader for other units? Is the workaround similar between the 918, 15 and 17 units or is it different? If its the same, are you able to produce a loader to emulate a RackStation RS2818RP+ ? I've got a SM 16 bay chassis currently configured with only 12 bays connected and it would be pretty awesome to have access to all the bays, however I don't have the necessary skills to disect your work!
Cheers
Chris
-
So I took the plunge and attempted to migrate my 3615 based setup to the latest image. Copied the details from the old USB stick for PiD/VID and serial/MAC setup, created the new image and booted up. Interestingly if you're using LACP to bond ethernet together then you have to unbond at the switch to migrate as it won't do anything until then. Once its reset, you then have to apply the bond again otherwise DSM cannot be found. Only way for this not to work is if you reinstall completely in which case DSM won't have a bonded config.
All appears to be working now, will see how it goes!
-
On 8/5/2018 at 12:34 PM, jun said:
Hi, options not available in vanilla DSM are hidden in /proc/cmdline
here is a example of disk order related options: SasIdxMap=0 DiskIdxMap=080C SataPortMap=4
it should works like this: DiskIdxMap make first sata controller start from disk 8, second from disk 12 etc,
SataPortMap limit the number of disks a sata controller can have(vmware's virtual sata controller have 32 ports!)
then SasIdxMap make SAS controller start from disk 0, as a plus, this option should give you a stable SAS disk nameSorry to come back to this; I'm using two SAS HBAs and not native SATA. Should I be using SataPortMap at all here and let SASIDX do something? Previously, I've used sataportmap 88 to represent both controllers having 8 ports but ideally, I'd like to try and get the drives listed in the right order with the SAS hba's if possible.
Thanks!
-
6 hours ago, jun said:
Hi, options not available in vanilla DSM are hidden in /proc/cmdline
here is a example of disk order related options: SasIdxMap=0 DiskIdxMap=080C SataPortMap=4
it should works like this: DiskIdxMap make first sata controller start from disk 8, second from disk 12 etc,
SataPortMap limit the number of disks a sata controller can have(vmware's virtual sata controller have 32 ports!)
then SasIdxMap make SAS controller start from disk 0, as a plus, this option should give you a stable SAS disk name@jun if using the SASIDXmAP command, will this order the disks according to their connected positions instead of which one is detected first at boot up? By this I mean, presently disk 1 may be in slot 1 of the enclosure with an LSI 9211-8i (IT) HBA but in DSM it could be disk 6... Does this fix that and I insert a disk in to slot 8, it will show it even if its the only disk?
-
Does anybody know if Jun will be looking at an upgraded loader for the DS3615xs? My cpu is too old to run the 918+ loader.
-
2
-
-
Hello
I've been toying around with VMM on a spare machine and have got the cluster to work by setting the NIC MAC to the real mac address, but I've hit an error where by the virtual machine will not start with the error: "Failed to power on the virtual machine " name of my VM" on the host " name of my NAS" due to insufficient RAM on the host".
The test machine is a Westmere based Intel Xeon L5630 chip on a Supermicro X8DTL-iF with 8GB Ram. Virtualisation is enabled in the Bios /VT-D/V-TX) and the machine is booting fine... but trying to create any VM in VMM displays the above error. The VMs all have less than 4GB of ram assigned so its not a real ram issue.
Anyone use westmere based chips with VMM? Any pointers?
Thanks,
Chris
-
So I changed the mac addresses to the real mac of the NICs and VMM now works fine.
-
1
-
-
Did anyone resolve this? I'm moving from esxi hosted to baremetal but would like VMM to enable local hosting of certain VMs that are integral to the safe shutdown of my homelab... I'm just playing with this and I'm getting teh same outputs; that it fails to get the first MAC. I was using a generated MAC for the four NICs, but should I use the actual MAC of the quad 1GBe network card? Do I need a corresponding serial and if so, how do you generate it based on the MAC rather than the other way around?
Thanks!
Chris
-
Cool and that was the plan, I have the image setup and a spare drive, will migrate across and then that should work. The entire vSphere ESXi machine is going to be baremetal and I've run these cards in Xpenology/DSM before so should be fine.
-
Hi
I'm in the process of moving back to baremetal but I've hit a snag with reboots and shutdowns - the system won't actually do anything when requested by DSM.... Instead, I have to go through the IPMI interface to undertake the request. The motherboard was used with ESXi 6.5 up until recently and that was fine but its never had DSM on it before.
Are there any issue with Supermicro X8 class motherboards and reboots/shutdowns?
Thanks,
Chris
-
@sbv3000 thanks and resureccting this! I've created the USB and it running on a spare machine with a different HDD so its now at the latest level that my vDSM is. The new baremetal setup is using a quad 1GBe NIC on a supermicro motherboard, the USB grub is setup to use four NICs with MAC addresses linked to the serial. My vDSM is configured with only 1 NIC, is there going to be any issues with the current setup if I move from virtual with 1 NIC to baremetal with 4 NIC? Do I need to use the reinstall option or just let it boot up?
-
Thanks,
1) I've got an intel quad port so will use that, and disable the supermicro onboard NICs as I won't need them.
2) I'm on full passthrough of the drive controllers so DSM is on real HDDs, I moved the other way and essentially created a new loader VM disk but I presume I would need to build USB stick with the PID/VID setup and the MAC addresses of the NICs (as above)? Do this and then select reinstall option?
3) Its a rebranded APC, just reasonable power capacity and rack mounted. The management card does SNMP so that should be fine to do this. What functions do you have over SNMP?
-
I currently utilise Xpenology in an ESXi environment and I am wishing to move to a baremetal for various reasons. I have a number of questions:
1) I intend to increase the number of NICs available using Intel 1GBe cards. Is there a maximum number of NICs that DSM supports? My install currently has 1 stupidly and I want to push to 4.
2) If I move my current VM to baremetal, how can I initiate the loader to re-detect the hardware, presume I use the reinstall option in the loader on boot and then re-install DSM?
3) Does Xpenology/DSM work with UPS's to shutdown? I use a 1920w Dell UPS with management card and I want to ensure that I can shut down the machine when power becomes critical.
Thanks,
Chris
-
On 28/09/2017 at 9:34 AM, IG-88 said:
would be interesting to know how a original 3615/3617 box handles the two optional 12slot extensions
they wil be attached by esata and multiplexer but the config has max.12 drives in it
(maybe a process will change that if a external unit is detected?)
and as the design is for 36 drives already as the name "36xx" implies they must be capale of more then 24 drives
I believe the ports on this are infiniband connections which will be attached differently to sata, but I'm not sure how.
Updating an older Synology DS running Intel x64 cpu using the loaders?
in The Noob Lounge
Posted
Hello people!
I used the various loaders for many years until I purchased a DS1821+ in 2021 which has served me well. With the changes to Google Workspace for backing up my data to the cloud I am going to purchase another device I use to backup to that is remote to the house as here in NZ we have fibre to the home with the base package being 300/100 so decent level performance for backing up but also the ability to collect the backup unit if I need to locally restore via my Lan for full speed performance.
In NZ there are a number of older DS units such as the DS415+ with drives going fairly cheaply which seemed to be perfect for backup target and while they are coming EOL for updates I remembered about this site and wondered whether the latest loaders would allow the DS to boot up to a newer version if / when I needed to upgrade beyond the official updates? I'd imagine that getting the loader on to the unit would be the harder task though?
Anyone got any thoughts and/or done this before?
Thanks,
Chris