flyride
Moderator-
Posts
2,438 -
Joined
-
Last visited
-
Days Won
127
Everything posted by flyride
-
Ok, this confirms you have a simple RAID6 and btrfs. The link cited https://xpenology.com/forum/topic/14337-volume-crash-after-4-months-of-stability/?do=findComment&comment=107979 is a reasonable one to follow. You can ignore any instructions involving lvm (lvdisplay/pvdisplay/vgchange) and just focus on the filesystem mounting and/or repair commands. The link above is to the post that you should start with.
-
Doesn't look like you're using an lv, just a plain RAID6. You need to know if you are using btrfs or ext4. Post the output of cat /etc/fstab
-
Only possible cache would be SSD cache so this should not be necessary. But probably the best conservative move. This is the wrong place to ask this question FWIW
-
Let's simplify. If it won't boot, it's because of one of the following: USB key corruption/damage DSM boot partition unavailable Hardware failure You say your device is headless. Does that mean it doesn't have a keyboard and video port? If it has them, connect them and see if your hardware is even powering up If the hardware is working, launch Synology Assistant or find.synology.com and see whether it is booting to a damaged state. If so, report back. If no boot is occurring at all, you probably have a failure of the USB. Burn a new, clean loader USB with DS918+ configured exactly as you have now (updating VID/PID if necessary). Synology Assistant should find it and offer to Recover and you should be back up and running.
-
DS3617xs adds NVMe support in DSM version 7.0.1. The way Synology does it is via the NVMe-capable M2D20. I would think that the patch approach would work for normal NVMe cards as well, but that remains to be verified.
-
Vulnerability. What should current xpen users do?
flyride replied to asheenlevrai's topic in Developer Discussion Room
^^^^^ This There have always been privilege escalation hacks to DSM, these are just the ones they are telling you about. -
Important Note For the following models, DSM 7.1 will be the last upgradable version. XS Series: RS3413xs+, RS10613xs+, RS3614xs+, RS3614xs, RS3614RPxs, RC18015xs+, DS3615xs
-
Don't expose DSM directly to the Internet
-
Tutorial/Reference: 6.x Loaders and Platforms
flyride replied to flyride's topic in Tutorials and Guides
Post your question here or here or here -
USB Drives as Internal Drives in XPEnology DSM 7
flyride replied to tintun2022's topic in The Noob Lounge
Internalportcfg set in user_config.json? Update that instead. -
Develop and refine the DS3622xs+ loader
flyride replied to yanjun's topic in Developer Discussion Room
My understanding is that a SHR volume cannot be expanded beyond 108TB. In order to create a >108TB volume, the following characteristics must be met: Supported device for 200TB volumes >= 32GB RAM RAID5 or RAID6 array (not SHR, assume RAID10 and RAIDF1 are also compatible) I have not personally verified this, and I only found one reference to SHR/200TB mutual exclusivity: -
Develop and refine the DS3622xs+ loader
flyride replied to yanjun's topic in Developer Discussion Room
"supportraidgroup": "no" "supportssdcache": "no" "support_disk_compatibility": "no" https://xpenology.com/forum/topic/54545-dsm-7-and-storage-poolarray-functionality/ https://xpenology.com/forum/topic/56872-develop-and-refine-the-ds3622xs-loader/?do=findComment&comment=266161 -
It's not just kernel support that is missing, but there are a number of NVMe tools that are also part of DSM that are not present on DS3615xs. Interestingly enough, DS3617xs 7.0.1 seems to have native NVMe support, presumably to support the M2D20
-
Develop and refine the DS3622xs+ loader
flyride replied to yanjun's topic in Developer Discussion Room
The default behavior of DSM is to RAID1 over all available devices for /dev/md0 (Linux OS) and /dev/md1 (Linux swap). I assume we all know this but just to clarify. -
Ok. I will repackage the information in this thread and hopefully it will be clear. DS3615xs does not support native NVMe. At all. M.2 is actually PCIe in a small form factor. All PCIe to M.2 adapter does is link one connector to the other. It has no ability to make the M.2 device accessible to DS3615xs. The only way I know of to access an NVMe device with DS3615xs is to use a hypervisor to spoof it in as a SATA device - i.e. VMDK or RDM mapping. I would not recommend using VMDK or RDM mapping for DSM cache but you may find that it works. Both approaches are used successfully for Storage Pool array devices.
-
Develop and refine the DS3622xs+ loader
flyride replied to yanjun's topic in Developer Discussion Room
This is showing the result state, not how it got there. It would appear that the /dev/md0 array (/root partition for Linux) has been corrupted. When /dev/md0 cannot be mounted, there is no DSM, and it will offer to install which is consistent with your report. As to why it happened, I have no idea. Diagnostically, I would probably choose to evaluate the state of the arrays before clicking "Repair" and then, see what it was actually doing during recovery (i.e. before and after cat /proc/mdstat). But this doesn't help you much with the system as it is. I hope you can reinstall or backrev and your data arrays are intact. For me, redpill testing is nowhere near extensive enough for me to go to "production" but I realize the definition varies for different people. -
Develop and refine the DS3622xs+ loader
flyride replied to yanjun's topic in Developer Discussion Room
There is an easier way to do this. Edit /etc.defaults/synoinfo.conf and change support_disk_compatibility="yes" to "no" and reboot. Then all drives can be used without error messages. Seems like it would be a good option to push with redpill. -
Maybe. Redpill is alpha/experimental. Not recommended unless you are willing to troubleshoot extensively, risk and lose data.
-
You keep asking the same question. The answers have been posted in this thread multiple times.
-
Not sure what this means. Regardless of RAID or SHR, you cannot remove/replace two drives at a time or you will lose the array. Also, if you plan to replace all the drives you have with larger, identical ones, the space will be expanded regardless of whether you are running RAID or SHR. SHR can be easily added if you continue to look on the forum for the configuration file information No. Haswell or later is required.
-
6.2.3-25426 Update 3 is the last version that is functional with Jun's loaders 1.03b and 1.04b
-
Not to nit but the rploader definition for the broadwell NK platform is "broadwellink" and Syno refers it to "broadwellnk" (without the "i") Obviously it's coded to pick up the correct platform but it should probably be fixed to avoid confusion and future error.
-
Someone with Proxmox experience needs to answer that. But if it is actually being bottlenecked by SATA 1.5 you should see a max of about 120MBps. Again this is all virtualized right? So the SATA specs may not mean anything as it is emulated in the first place. What's the actual performance of your underlying storage?
-
Cannot speak to Proxmox, but if I inspect my DSM 6.2.3 running on ESXi, I get no SATA connection speed status on virtual disks, but valid 6.0 Gbps for physical. Virtual disk is being presented as a SATA device for compatibility purposes, yet the device in question operates at full speed (>1GBps in the case of this NVMe backed store). Why don't you test your virtual disk and see if you get >150MBps and if you do, clearly are not limited by whatever you find in dmesg. root@nas:~# smartctl -d sat -i /dev/sda smartctl 6.5 (build date Mar 12 2020) [x86_64-linux-3.10.105] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: VMware Virtual SATA Hard Drive Serial Number: 10000000000000000001 LU WWN Device Id: 5 000c29 bafa731d8 Firmware Version: 00000001 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA/ATAPI-6 T13/1410D revision 0 Local Time is: Mon Feb 14 12:28:40 2022 PST SMART support is: Unavailable - device lacks SMART capability. root@nas:~# smartctl -d sat -i /dev/sdh smartctl 6.5 (build date Mar 12 2020) [x86_64-linux-3.10.105] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: SAMSUNG MZ7LM3T8HCJM-00003 Serial Number: [redacted] LU WWN Device Id: 5 002538 c0009dd5d Firmware Version: GXT3003Q User Capacity: 3,840,755,982,336 bytes [3.84 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Feb 14 12:30:43 2022 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@nas:~#
-
Tutorial: How to access DSM's Data & System partitions
flyride replied to Polanskiman's topic in Tutorials and Guides
Generally you are better off troubleshooting arrays and volumes within DSM if it will boot. If you can't even get DSM to boot, then going through the motions on Linux is a last resort.