Jump to content
XPEnology Community

tsygam

Member
  • Posts

    40
  • Joined

  • Last visited

Posts posted by tsygam

  1. Только если можно, объясните зачем плодить сущности и ставить MySQL когда в DSM как служебная база есть Postgres и с ней все работает, или действительно есть веские причины?

     

    Я одинаково плохо (т е почти никак) знаю MySQL и Postgres и поэтому спрашиваю.

  2. c SQLLite не влетело. Забыл какая ошибка, но у вас на форуме она обсуждалась - не создавалась база.

     

    с Postgres, после распаковки в /volume2/Web/TorrentMonitor :

     

    DS> /usr/syno/pgsql/bin/createuser -P torrentmonitor -U postgres

    DS> /usr/syno/pgsql/bin/createdb -O torrentmonitor torrentmonitor -h localhost -U postgres

    DS> cat /volume2/Web/TorrentMonitor/db_schema/postgresql.sql | psql -h localhost torrentmonitor torrentmonitor

     

    все взлетело.

  3. Лучше использовать mysql, c sqlite возникнут проблемы при обновлении, я за 2 года использования обновлял его кучу раз.

     

    а почему не postgresql который уже есть в DSM? у меня взлетело легко.

     

    ps: спрашиваю т.к. не знаю, а не чтобы поспорить.

  4. Не смог подключиться к QuickConnect с ошибкой "Система не может выполнить запрошенную операцию в связи с неизвестной ошибкой".

    Перегенерил серийник и мак, зарегистрировал новый серийник, прописал мак в ESXi и серийник в syslinuix.cfg. Воз и ныне там.

    Всё остальное работает.

     

    была аналогичная проблема - указания mac в ESXi недостаточно

    впиши mac ещё в syslinuix.cfg

  5. I tried playing with link aggregation recently (i do not have Cisco and used asus rt-ac66 router for experiments) and paused for a while.

     

    my findings are:

    - probably there is no need to do bonding on virtual part (at least from the very beginning) as vmxnet3 driver is quite capable by itself - http://www.vmware.com/pdf/vsp_4_vmxnet3_perf.pdf

    - my jetway board has Intel's 82579lm and 82574l NICs (both are currently supported with ESXi 6, though with 5.5 i used community drivers). 82579lm is also used by Intel AMT which in turn used shared (with the host system) MAC of that NIC

    - ESXi management network is using 82574l MAC and this NIC is the first in failover order for mgmt network, while another one is the first for vM network

    - after enabling LACP (used VDS on ESXi side), on both sides, from roter's side I noticed that partner (ESXi side) was using 82579lm MAC (where AMT is) and I could not force it to use 82574l MAC and that lead to inability of ESXi host access

     

    at that point I paused for a while, to find out how can I switsh from shared MAC for AMT to a dedicated one. Per intel AMT documentation this is possible (in theory???)

     

    May be you are facing the same thing - bonded link is using MAC which is not the one used by mgmt network, so its MAC is not exposed and cannot get IP?

  6. You can pass through your UPS as well, further there is NUT client for esxi on some French site, just google for it, set NUT at DS as master and at esxi as slave.

    I have router plugged into the same ups as esxi, so for me nut master is on the router and both DS and esxi are slaves.

     

     

    Отправлено используя Tapatalk

  7. I was looking for an option to change from Intel chip based raid to adaptec based one and got an impression that it is not possible to change raid cards/chipsets for a different manufacturer. Raid cards/chipsets write metadata (each manufacturer uses its own format) to disks and different chip unlikely able to pick it up.

     

     

    Отправлено из моего iPhone используя Tapatalk

  8.  

    A. Has anyone experienced a drive failure? Did a simple swap of the drive solve the issue?

     

    B. When running xpenology as a VM, has anyone experienced a power failure? Was the system affected in any way? Were the data intact?

     

    C. If my HW crashes, will I be able to migrate my drives to a new xpenology box or synology without issues/losing data? I've read multiple times that "this should be possible", however I haven't seen a post by anyone who has actually done this.

     

    D. I've read a couple of posts about people having issues with their pool after expanding it. Does this generally work fine?

     

    E. Is there anything on the VMWare side of things that can cause issues?

     

    F. Just curious, has anybody been able to run their box without downtime for extended periods of time (years)?

     

    Hi, may be my experience will be of interest

     

    I have 8 bay U-NAS box:

     

    - MB Jetway nf9e-q77

    - 500 mb SATA drive for ESXI & datastore

    - Adaptec 7805

    - nanoboot + DSM 5 + ESXi 5.5

    - 3x3Tb WD Red in a RAID 5 + 1 disk as a hot spare

    - whole LUN passed to DSM as RDM where used for a single volume

     

    As to your specific questions:

     

    - I never had a drive failure as such

    - I had power failures due to my stupidity - while setting up Network UPS Tools as a server on the router and a client in ESXi, i realised too late that the box was plugged into the filter socket rather into battery backed up socket, so a dosen of power offs occured. No issues, exept for DSM crying that it experienced ubnormal shutdown.

    - no sure on drives migration, but as far as I remember I sucessfully mounted RDM in a different DSM VM and for sure several times under ubuntu and CentOS VMs.

    - expansion can be a bit difficult, see my post http://xpenology.com/forum/viewtopic.php?f=15&t=3339&start=40#p24563 and that thread itself, it is not that long.

    - SMART data passthrough can be an issue, I actually do not care - will set up some notification with ESXi/Adaptec's tools a bit later. After switching to nanoboot, I experianced DSM loosing any connection, though VM was running and after sending it to reboot from the console (VM tools were also off) it was running fine. I guess this is a nanoboot issue. will dig into when i get a chance

    - I have not run the box for years, but several months without reboots/offs

     

    If need more help, pls ask.

     

    BR

  9. Hi,

     

    I would like to share my short story:

     

    - nanoboot + DSM 5 + ESXi 5.5

    - Adaptec 7805

    - 3x3Tb WD Red in a RAID 5 + 1 disk as a hot spare

    - whole LUN passed to DSM as RDM where used for a single volume

     

    Decided to add 4th disk to RAID.

     

    This took about 3 (three!) weeks for Adaptec to complete the rebuilding task after which ESXi recognized increased RDM disk size after refresh from the storage pane in the vsphere client, DSM recognized new disk size after reboot.

     

    Obviously it was not possible to increase the volume size by DSM’s standard tools. I had an idea what to do, but made a quick search to confirm and found this wonderful blog: http://blog.azib.net/2013/12/how-i-upgr ... as-to.html with a very well structured comments.

     

    Having nothing to add in substance, I would point out that one should check disks/volumes/groups names (for my disk in question I had, /volume2, /dev/vg1001/lv, /dev/md3, and /dev/sdb5 which became /dev/sdb3 after allocation of all free space) and would like to stress that sectors should be used in parted rather than smth else (fire “unit s” in parted). To have all sizes at hand, fire a second terminal window for “parted /dev/sdb unit s print free”

     

    Actully this resizing in DSM does not take much time - i think less than an hour for me (apart from RAID rebuild at HW level) with a cofee break :smile:

     

    BR

  10. Hello!

    I've installed XPEnology gnoBoot on my HP Microserver G7 N54 over ESXi 5.

    All right, but my speed of copying on XPEnology is very slow (at beginning over 60 Mbs, after that it go lower to 5 Mbs). If I install XPEnology as real OS on my disk speed of copying files into Microserver over 110 Mbs.

    If you have got same scheme can you provide me your speed.

    At this moment I will try installing another hypervisor (Proxmox) and test XPEnology on it.

    Can it be some troubles with configuration of ESXi and problem can be solved by fixing it ?

    Thanks!

     

    have a look at ESXi thread - i think there was a discussion or several posts at least on pvscsi, RDM and pass-through speeds

  11. Hi there!

     

    can someone help understanding how volume numbers are assigned?

     

    I'm on ESXi, made gnoboot as IDE disk, second disk made as pvscsi, put rmmod=ata_piix. Then attached two RDM disks. One of these RDMs was created as DSM's SHR and another one is just basic ext4.

     

    mount shows:

     

    DS5> mount

    /dev/root on / type ext4 (defaults)

    none on /dev/pts type devpts (gid=4,mode=620)

    /sys on /sys type sysfs (0)

    /tmp on /tmp type tmpfs (0)

    /proc/bus/usb on /proc/bus/usb type usbfs (0)

    /dev/vg1000/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

    /dev/md4 on /volume3 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

    /dev/vg1002/lv on /volume4 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)

    DS5>

     

    why /dev/md4 is mounted on /volume3 and not on /volume2 and /dev/vg1002/lv on /volume4 rather than /volume3 ?

     

    BR

  12. mv /sbin/shutdown /sbin/shutdown_old

    vi /sbin/shutdown

     

    paste the following code:

    #!/bin/sh

     

    for var in "$@"

    do

    if [ "$var" = "-r" ]

    then

    reboot

    exit 0

    fi

    done

     

    poweroff

     

    Then change the permissions so teh script is executable.

    chmod 755 /sbin/shutdown

     

    This worked for me!

     

    worked for me too, though I did not have /sbin/shutdown to rename

     

    Many thanks!

  13. Check the logs to see if there is anything failing, or if the vmtools daemon can't start, etc.

    can you tell which logs should contain VMware tools entries and is there any tools specific logging which can be enabled?

    I don't have the time to research/debug what it is I've done to get my version working (I do remember spending a reasonable amount of time on it though). I've probably forgotten something somewhere. It may be a few days (weekend?) before I can get back to you on this.

     

    I will really appreciate your help and will wait patiently :smile:

×
×
  • Create New...