Schmill

Members
  • Content Count

    141
  • 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. Yeah very relieved at that! My panic was ransomware or something equally bad. Must admit, I'm not entirely sure what the "data scrubbing" is, is it an integrity check / scandisk type thing?
  2. It seems maybe it was doing days scrubbing on the volume; just happens it decided to do it at boot and made the poor N54L so busy that the system didn't seem to come up. A good exercise in days recovery from the SHR volume though, so there's that at least
  3. Thanks for the reply, no nothing in the logs. It's not immediately after boot, it's once the local screen says that the kernel is booting, then everything goes nuts. I've managed to mount the volume under systemrescuecd (using the same instructions) and copying files off via ethernet. Slow going but seems ok Once it's done my main files I'll try booting it again...
  4. So to all intents my Xpenology box was running fine, but this morning I couldn't get any mobile apps to connect to one of the user accounts, it kept saying session timed out, login. Using my admin account worked fine, and so I logged in and did a restart on the box. Now starting up I can hear the drives absolutely thrashing and the system hasn't appeared back on the network. I must admit, I've panicked somewhat since I don't know what is going on on the disks I'm loath to just "leave it". I'm running SHR, is there some way I can check the disks outside of Synology to make s
  5. Hi, I am looking for some pointers for diagnostics please. Microserver was running DSM 5.1 so updated to 5.2-5967 and all was well. From there followed the tutorial to update to 6.1.4, then 6.1.7, and finally 6.1.7 update 3. Again all was well, tried some reboots everything worked. About 2 hrs later the DSM disappeared from the network, no web ui, no ssh. Finally pulled the power and restarted it, still doesn't appear nor does find.synology.com see it (not that I thought it would). So where do I go from here? I note that Juns loade
  6. 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.
  7. 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
  8. 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?
  9. 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 (w
  10. 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 softwa
  11. 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.
  12. 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!
  13. 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
  14. - 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
  15. 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 ?