Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 05/04/2021 in all areas

  1. Tienes que configurar una IP diferente a cada una de las tarjetas de red de la Xpeno. Si te conectas a ella por la IP que tiene el cable con conexión de 10 Gb iras a esa velocidad si el MAC esta conectado al swith de 10g tambien, si por el contrario te conectas a la IP del cable de 1 Gb irás a esa velocidad. La configuración esta en Panel de Control - red - Interfaz de red (si no configuras ninguna ip fija, en esta pantalla puedes ver que ip tiene cada tarjeta y utilizar esas ips para conectarte a la Xpeno) doy por sentado que en tu xpeno tienes una targeta de red de 10 g y otra de 1 g.
    1 point
  2. @bearcat, I'm currently without access to my server, but next week I'll confirm it here so you can get these details.
    1 point
  3. Just an update. I had nothing special to do this weekind so I installed whsv1 on a spare hd and temp running around 120 F while transferring large files so it looks like it's running at the same temp as when the E5200 was installed. Just thought I would update in case anyone else wanted to use the 8200s cpu.
    1 point
  4. Great idea. Consider it my next challenge!
    1 point
  5. i maintain the alternative of using open medial vault, if dsm breaks i can boot up omv from a disk or usb and have network access to my files and if synology gets nasty i will just switch to omv (btrfs and SHR are no problem, just work when starting omv) Just a quick comment on this, if folks do feel the need to start reposturing themselves away from DSM because they are concerned with access to security patches or just have to have the "latest" on whatever platform they want, it would probably make sense to steer away from using SHR - yes it can be supported on OMV or plain old Linux, but it becomes very hard to administrate/fix/assess/maintain once DSM is gone. For me at least, Docker has freed me from value added services on DSM - those can run on a separate VM or wherever. There are only a couple of things that really, really keep me on DSM: btrfs. Synology's implementation is the only RAID5 solution that is "safe." btrfs offers dedup/CoW in a memory/compute footprint that is smaller than anything else available, including zfs. Snapshot management and replication. It's not perfect, but DSM makes these truly enterprise features available on (again) very low cost hardware. RAIDF1. This is the most elegant and unobtrusive solution to the SSD co-expiry problem that I've seen, and that includes enterprise solutions. Yes you can get btrfs, or snapshot management on other platforms. But not both together like DSM, and not with RAIDF1. I would love to see something compelling on the other open-source derived platforms that made me want to switch. having the maintained security updates might matter for some people if the make dsm accessible over internet (like photo station or nextcloud) i'm more on the side of using vpn to access dsm, makes a much smaller attack surface but will also shut out less IT centered people like family member's we will see what happens when dsm 7 is out for 1-3 month and i'm not even sure if 7.0 will really have something to offer, i haven't seen anything that triggers reflexes to make it a must have (at least for me) This is probably an opportunity for this community if 7.0 support doesn't present itself. As long as no Synology update is likely to overwrite them, coming up with a maintainable library of middleware/security updates might be a way to keep XPe going for quite some time. This is essentially what is happening now with the extended driver support via @IG-88's extra.lzma, @The Chief's patches for NVMe cache support and FixSynoboot. As far as 7.0 goes, btrfs capability (performance, native real-time dedup, etc) is purportedly enhanced. And given the btrfs is getting quasi-abandoned by everyone else in the industry, Synology may essentially be forking their own long-term development of btrfs as a primary contributor (which I guess you could consider both good and bad). So even if we maintain 6.2.3 as a long-term stable niche as above, getting support for 7.0 will likely continue to be of interest to many.
    1 point
  6. It seems to me a strange thing, mystifying… Try attached .so. libsynonvme.so.1
    1 point
  7. Хе, человек до точно того же додумался. Мне не нравится то, что оно утверждает, что nvme уже является членом массива. Надо подумать.
    1 point
  8. Ну не прям ваш, но такой же пример: https://www.reddit.com/r/synology/comments/a7o44l/guide_use_nvme_ssd_as_storage_volume_instead_of/ Прикрепил текст в виде фото, так как не пускал форум submit reply, считая, что я делюсь контактами
    1 point
×
×
  • Create New...