Jump to content
XPEnology Community

Bobbenoster

Transition Member
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Bobbenoster

  1. I'd recommend not just straight port forwarding. Give yourself a little extra safety by using a reverse proxy in between to filter traffic based on the address (ie only direct the port forward to the Nas if it's coming as a request for middleearth.mydomain.com). Changing the port will misdirect some script kiddies but it will still be found on a port scan and hackers will then keep poking at that port until they find a vulnerability.
  2. relays were mentioned in the original post so I believe the idea is a physical trigger of the power button at a scheduled time (presumably only if the machine is not already on) with some kind of communication (I'd venture serial comms) to the esp chip to set the automatic startup time...
  3. Same here... Have some esp8266 boards... If you tell me what you are looking for them I can gauge how far I would be out of my depth...
  4. hmmm well no I didn't think I had a big issue... knew it had to be something with the sata config in grub. But I'll sprinkle some WTF on my issue... so drive 1 and drive 5 (pretty sure that's the 3rd port as there's only 4 ports... but hey) are both old seagate 500gb drives. different models though. drive 1 has bad sectors and about 10k hours, drive 5 has no bad sectors and < 10k hours. both show as "critical". I'm guessing drive 5 just isn't on the list of drives that synology is ok with... it bluntly refuses to use that drive. plugged in a 15yo laptop drive (hitachi 100gb 7200rpm) in it's place and dsm is just fine with using that. so on the initial install it really doesn't like seeing bad drives... or only 1 bad drive? this being a test bench it only gets the dodgy leftovers. but hey, so far i'm impressed. it sees 6 cores, sees all 16gb ram and i've installed a whole lot of apps. not seeing it go all weird on me (i haven't checked too many logs, only the dsm logs in the control panel). so cheers to @pocopico and @ThorGroup and @IG-88 and @Peter Suh and all the other active guys on this thread and forum...you're doing amazing stuff! (sorry for all the names I left out, there's some true legends in this thread - taking on all the weird reports and questions on here, making sense of them and somehow having the patience to answer them all, even the repeats!)
  5. update more... after reboot plugged in all the drives again... sataportmap back to 6, hotplug 1... the 2nd drive is now back... the 3rd drive shows up in slot 5 and is flagged as critical... now this drive has zero bad sectors... has the lowest number of powered on hours... comes back with a clean smart test... drive 1 on the other hand has 336 bad sectors yet is marked as healthy, hours also slightly higher than drive 3 aka 5. could this mean that something in redpill is mixing up the smart test results?
  6. update... so setting sataportmap to 1 allows me to install... also set hotplug to 1 (some part of my broken brain recalls that being mentioned)
  7. So I tried to upgrade my test box from 3615xs running 7.0.1 to 3622xs+ running 7.1... Platform is a 3rd gen i5... now before the upgrade I always had a message saying the 3rd disk had errors and the port was disabled. post upgrade (loader only, dsm not installed yet) I get a message stating disk 3 and 4 have errors and the ports have been disabled... now there's only 1 sata drive connected, booting from usb... but the web assistant refuses to continue. setup set sataportmap to 6 and diskidxmap to 00 output on telnet: SynologyNAS> fdisk -l Disk /dev/sda: 466 GB, 500107862016 bytes, 976773168 sectors 60801 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect /dev/sda3 587,111,37 1023,254,63 9437184 976568351 967131168 461G fd Linux raid autodetect Disk /dev/synoboot: 14 GB, 15382609920 bytes, 30044160 sectors 14670 cylinders, 64 heads, 32 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table I guess the first check before the upgrade should have been to see if the 3rd disk actually had errors:-P
  8. So I'm late to this party... but flashed the tiny core loader to a flash drive and went through the "process". this has been the fastest i've ever brought up an xpenology box... my only challenge was that for some reason my bios had the sata controller set to IDE rather than AHCI... changed that and redid the satamap... and blam... it just works... setup is a 3615xs on i5 3470, 12gb ram... there's 3 disks in the machine (1 upsets synology because bad sectors) and a gt520 graphics card. that said, i'd be happy to test things on there now that i know it works (my main xpenology box is staying untouched on 6.2.3 for another while)
  9. Interesting... 6.2.2 definitely wanted the extras Sent from my SM-A705FN using Tapatalk
  10. The extra file adds drivers that mean (within reason) you can actually update to 6.2.3
  11. Did you create your USB with an extra file? I've only done microserver g7 builds... 1 with a HP nc360t NIC... The other two run onboard NIC, 1 has the stock loader - stuck on 6.1.x, the other runs a loader with an extra file added and runs on 6.2.3
×
×
  • Create New...