Jump to content
XPEnology Community

Diverge

Member
  • Posts

    355
  • Joined

  • Last visited

Everything posted by Diverge

  1. That test image is for a 5.1 fix to initial XPEnology. As far as I know 5.0 w/ nanaoboot had no issue. If you use that image you'd be upgrading your system from 5.0 to 5.1, and will be offered to migrate your data (if it can find it) or format your drives to build a new array...
  2. I went through a similar situation a couple years ago, except my box crashed during expanding, and wiped out my partition tables. After I fixed the partition tables (took lots of research, using another linux system w/ testdisk), I could not get DSM to recognize the array - it would show as crashed in DSM, but via console my volume1 was there, along with all my data. I eventually just backed up all my data to another drive and started over. I know synology has a way of fixing crashed arrays so they are recognized in DSM, but I'm not sure exactly what they do. This probably doesn't help you much, but I would check via console/shell and see if your volume is there, even though DSM marks it as crashed. And if that doesn't work, mount the array in linux, and see if you can get your data that way. If you're determined to fix DSM and your array, and figure out a way, I'd be curious on how you did it.
  3. If you're running baremetal (not virtualized), and booting off a usb stick, just write the new boot image to your stick like you did for your current version. It should boot like nothing happened, then go to the disk Storage Manager>Volume>Manage>expand volume with allocated disk space. It should happen pretty quick (I did this as well). It should all be pretty easy and straight forward, as written above, assuming you didn't mess up your array by removing the disk and booting into a degraded array.
  4. Sounds like your onboard NIC isn't supported. Find out the chip used, and try to confirm if others had success with same NIC.
  5. But only alternative to RDM solution is Raid controller with VT-D? this for Smart and etc... You only need an HBA card (I recommend LSI 9201-8i - OEM only, can be found on ebay for ~$75, works great with ESXI). But if you want drive temps in DSM you need to passthrough a controller (VTd), or bare metal. DSM doesn't use smartctrl (smartmontools) to read drive temps, it uses synodisk (their own utility), and synodisk doesn't like RDM drives - it won't report the temps (at least when I used RDM in the past). smarctrl will read the temps of RDM drives, but that's not of much help if DSM uses synodisk.
  6. I've had this happen before. I wrote a little script to restart the network interface via DSM shell. I don't recall the exact script offhand, but you can basically check the network status, and if it fails, run the following: /etc/rc.network restart if passes, do nothing. You can setup a DSM task to run every X minutes, hours, ect.
  7. i3's don't support VTd, so if you're going the esxi route, you won't be able to pass hardware to any VM's. If you want VTd, you'll have to go w/ i5+.
  8. Intel DQ77KB, i7 3770T, 16GB ram, LSI 9201-8i. WMC VM is just server part. Playback on Xbox 360 WMC Extender (client part). Sent from my Nexus 6 using Tapatalk
  9. It all depends on what you want out of your hardware, or knowing what you want, and using capable hardware. example; My NAS is more of a mini-server for me. I use performance, but low power Intel CPUs. (Type T w/ 45W), and supporting hardware that is all compatible with VTd (direct IO), to pass through LSI controller for XPEnology raid array... this way DSM has direct access to hard drives, and they are only for DSM. My NAS is file storage, and Plex server that is capable of transcoding any media without breaking a sweat.. and handles all my media (NZBget, Sonarr, couchpotato, ect). It's also VPN access to my LAN from my mobile phone Then I have other VM's on the same machine; Windows 8.1 for Windows Media Center (to watch cable TV via cablecard and Xbox 360... you don't need to activate it to use it for WMC extender/server). I also have a linux VM for just playing around with linux, capable of compiling android source, ect, ect. Storage looks like this: 128GB SSD for my VM's. All physical hard drives for DSM array. DSM iSCSI LUNs to give additional storage to my other VMs (like WMC's live TV buffer, and DVR'd shows).
  10. I'm pretty positive the problem is from log files filling up the DSM partition. I know older gnoboots had this issue, because there were logs of debug errors. I think eventually gnoboot changed it so the errors aren't written to disk, and just ignored. Are you using an old boot image? Also, the DSM is mirrored to the first partition of every disk... So if you manually try to fix on other Linux OS, you may need to do each disks partition. I'm not 100% positive though. Best bet is try to get access using DSM via terminal. Sent from my Nexus 6 using Tapatalk
  11. Hook a monitor to your box, or check the console if you're using VM's. There's also SSH, if you enabled it, and telnet (which I think is enabled by default). user: root password: your_admin_password I think I recall reading about this issue in the past, and pretty sure it's fixable. You should be able to search for it. Here's one thread about it: http://forum.synology.com/enu/viewtopic ... 19&t=77121
  12. With that test image I was able to create a 3 disk array, and then add a 4th disk. Everything worked as expected for both SHR and Raid 5.
  13. Do you have IT mode firmware on it? Cause that's what you'll want if you want DSM to control and manage the array. I have no personal experience with that card, but my 2 different LSI cards work with no issues and use same driver. Sent from my Nexus 6 using Tapatalk
  14. It would have only been useful to you if you had an HBA card to passthrough (like LSI Raid/HBA card running in IT mode).
  15. This test img seems to work correctly for expanding. Previous condition of my test array was that disks were added, but volume group needed to be expanded/extended. With new image I booted into DSM, then Storage Manager > Volume > Manage (TAB) > expand volume with unallocated disk space. Array was resized in less than a minute /etc/synoinfo.cfg was at default settings... they also changed back to stock, but I think /etc.defaults/synoinfo.cfg rewrites changes at boot... which is probably expected behavior
  16. Changes don't stick... something is writing them back to stock. DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup' supportraidgroup="no" DS_Test> cat /etc/synoinfo.conf>/etc/synoinfo.conf.bak | sed -i -e 's/supportraidgroup="no"/supportraidgroup="yes"/' /etc/synoinfo.conf DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup' supportraidgroup="yes" upon reboot: BusyBox v1.16.1 (2015-01-07 14:56:36 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. DS_Test> cat /etc/synoinfo.conf |grep 'supportraidgroup' supportraidgroup="no" DS_Test> backup file there though: DS_Test> cat /etc/synoinfo.conf.bak |grep 'supportraidgroup' supportraidgroup="no" DS_Test> edit: array expansion failed for both raid 5 and SHR.. it adds disk to the array, but doesn't expand the volume.
  17. I use local_ip:32400/web/index.html#!/dashboard. I think Plex requires it being linked to plex account... In the past it didn't, but after they put a lot of work into the webclient I think it might be a requirement now. I'm doing exactly what you want. I use Synology VPN server. I connect to it with OpenVPN client on my Android Device. I can then go to local IP of plex server and see my media, or see who's currently watching stuff (as I share with family and a couple friends). But I also have my plex server linked to plex account... so that may be reason it not working for you.
  18. I know the feeling of losing all my data, it has happened to me in past. DSM decided to delete the partition tables of my array after failed expansion.... Took a lot of research, work, to reconstruct the partition tables with testdisk, then rebuild array in Linux, then backup data.... Now I don't take such risks unless I have my data backed up. But what you experienced is common issue after small update... No worries with that, just don't jump right in to latest update without knowing if someone tested it, unless you have backup. For example, my DSM 5 system has update 5 available... Haven't seen it mentioned or tested by anyone, and waiting on my 8TB backup HD to ship, since current backup HD is full. So I won't update until I create new VM for testing, or my backup HD ships, or someone else tests update 5. Sent from my Nexus 6 using Tapatalk
  19. Power completely down (not reboot), and then boot system if you haven't. There is issue after upgrading, where DSM drops your array on 1st boot after upgrade.
  20. Personally I'd go with an LSI controller. They are very common, and widely supported. Plus if you ever want to play with ESXI and have a cpu that does VTd, you can use direct IO. On ebay you can find a really cheap OEM version that you really can't buy from a store LSI 9201-8I. I own one and use it in one of my systems; works great. http://www.ebay.com/itm/LSI-Internal-SA ... 1821812462
  21. Are you using Plex app clients, or web client? If you're using app clients then the server must be connected to your plex account, with established connection to Plex in order for clients to work correctly. If your Plex Server is not connected to Plex account, you should be able to access your content via web plex client via VPN into lan, and using Plex server IP (I do this all the time).
  22. I'll try after my current test of expanding SHR array. It added disk to array, but didn't expand and option was grayed out. Just have to reboot and then check option and it will likely be clickable.. but my guess is will fail at expanding. Edit: will be a day or 2 until I get back to this. Currently doing tests to get Asrock to fix bios issue w/ PCIe SSD for E3C224D4I-14S motherboard (ESXI won't detect drive, but will boot preintalled OS... but once booted, no access to drive - works fine on Intel system).
  23. I'll test SHR next. Right now I am testing Raid 5. I'm starting with a 3 disk array, then adding a 4th disk to expand the array; that part is done. Now it's expanding the volume (had to reboot after expanding array - option was grayed out)... I'll post an update when it's done... it might be a while though. edit: apparently expanding volumes is broken. Sometime when I click button nothing happens, other times it says it is expanding, but it's really not.... DSM thinks it is (while never increasing %), but cat /proc/mdstat says otherwise.
  24. Explained here: viewtopic.php?f=2&t=5026&start=510#p31696
×
×
  • Create New...