Schmill

Members
  • Content Count

    136
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Schmill

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Much appreciated Polanskiman, really appreciate the work you've done putting it all together, I was just being overly cautious perhaps. I've now upgraded to 6.1.7 up3 and all seems well (fingers crossed!) Must admit, even after reading it all I didn't realise that updating to 6.2 was possible at all (without the Intel NIC), so that is worth knowing - cheers! Sometimes I think the issue is that there is SO much info around, determining what is still relevant is tricky sometimes.
  2. Anyone able to give any pointers in the right direction please? I want to update from 5.2, but don't want to trash my server if at all possible
  3. To be honest, I think it would be a lot better if SMR drives were outlived, but it seems not... This is what I bought, and SMR is the only thing I can think of to cause such a significant slowdown: https://www.amazon.co.uk/Seagate-Expansion-External-PlayStation-STEB6000403/dp/B07C7V494X Any PMR external desktop drives of ~6TB that you'd recommend as a replacement?
  4. Thanks for the reply IG-88, is this PMR area 'visible', or is it (as I expect) hidden by the drive and only accessible / managable by it? I am using the default "Backup & Replication" utility on the Synology software, but don't know what it uses underneath. The backup is of the entire server, so there is a mixture of large media files, as well as smaller (and plentiful!) files like mp3s, documents, and jpg photos. I too thought that as a backup it would be ok, since the SMR wouldn't be having to do its re-write behaviour, but it seems that is not the case. Bursty writes (with associated idle times) seems file, but the constant (sequential?) writing of an large file-by-file backup seems to give it a real headache... I did read several reviews before purchase, and all seemed to indicate that it was good for backup, bad for daily usage, but I'm wondering if by "backup" they actually meant copying a few files to it for "archive" every so often, rather than a true "tape-like" bulk backup.
  5. Ok, first things first, I know SMR drives aren't intended for daily use etc. due to the way that they record data, but all that I'd read seemed to say that they were well suited as backup drives. So I have a Seagate Expansion Desktop 6TB drive (USB3 connected, and externally powered) running through a USB3 card to backup my DSM 5.2 system... but it is horrendously slow. As in I started the backup over 38 hours ago, and so far it has managed to backup (DATA backup, not LUN) just 585 GB. I am using an N54L as my hardware platform - but is there any issue with the 5.2 software using SMR drives? It works fine with other USB3 drives (so I know its not the interface card), but I suspect that they are PMR, so does the OS having any issues with SMR, or is it literally going to be down to the drive itself? (In which case I'll have to return it and purchase a much more expensive alternative ) Thanks for any info!
  6. It seems more and more that attacks are targetting home / small-office NAS setups. In light of this (and https://www.synology.com/de-de/security/advisory/Synology_SA_19_37 ) , has there been any movement on this? I like being able to eject my backup media after the backup completes, but would also like to be able to re-insert (?) it just before the next backup is due to start.
  7. In light of this post: https://xpenology.com/forum/announcement/23-multiple-vulnerabilities-dos-attacks/ The Synology page states: As it only lists 6.2, does that mean that 6.1 is not affected? I am interested to know, since it seems with N54L "original hardware" (i.e. onboard NIC) we are stuck at 6.1.x - so is this an issue for us? Thanks!
  8. I've been running an N54L as a DS3615xs on 5.2 5967 Update 9 using SHR for quite some time, since when I was looking before the upgrades to 6.anything seemed flakey at best. Now I'm looking to update, but I'm not sure what 'end goal' I should be aiming for, or if I have to take an intermediate steps along the way? From what I can make out, the post below will allow me to upgrade from my 5.2 to 6.1.7 relatively pain-free? However, I'm not sure if then I should be upgrading again, or indeed (if that is the case) whether I should be going straight from 5.2 to something later than 6.1.7? 6.1.7 seemed to be the most stable, but then I wasn't sure about this: https://www.synology.com/de-de/security/advisory/Synology_SA_19_37 Do need to go to 6.2 for cybersecurity reasons? Thanks for any pointers that can be given - I've been away for far too long!
  9. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 5.2-5967 Update 8 - Loader version and model: XPEnoboot 5.2-5967.1 DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Microserver N54L
  10. Great thread, I am running (and have been for quite some time) DSM 5.2-5967 Update 6 , and got tripped up by this latest Plex update too. I guess there will now be a whole bunch of us looking to update to DSM 6 ?
  11. Hi all, what bootloader are people running with this latest update please?
  12. OK cheers, on the Tapatalk app there is no link in your first post, but the Amazon link does show. Thanks again! Sent from my MotoG3 using Tapatalk
  13. "this one" ? Sent from my MotoG3 using Tapatalk
  14. Hi all, I have a USB3.0 PCI E card in my N54L, and I find the performance a bit flakey, (which isn't great as it feeds my external drives used for backups!); also it is no longer available. I am looking to get a card for my parents N54L, and may look to replace mine at the same time, sooo... are there any cards that anyone would recommend (that are currently available), do I need to look for any particular chipset, or should I just be able to pickup any USB 3.0 PCI E (low profile) adaptor card from ebay and it should work? Thanks!
  15. Are you sure that is the case? I thought the whole worry of Synolocker was the fact that it infected and ran on the DSM directly, so would have access to everything that the NAS had access to.