Jump to content
XPEnology Community

mcdull

Member
 View Profile  See their activity

  • Posts

    252

  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Posts posted by mcdull

    [SOLVED] Install on vmware ESXI

    in DSM 5.2 and earlier (Legacy)

    Posted

    I have one more question,

    After using the 1.1 image, I have call trace every time I got server started.

     

    [   47.371813] Pid: 11634, comm: openvpn Tainted: P           O 3.2.40 #30 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform
[   47.372125] RIP: 0010:[]  [] tun_chr_open+0x40/0x53 [tun]
[   47.372321] RSP: 0000:ffff8800680d1cb8  EFLAGS: 00010282
[   47.372429] RAX: 0000000000000000 RBX: ffff88007ba2e7c0 RCX: 00000000000000ff
[   47.372556] RDX: ffff8800680aba80 RSI: 00000000000000d0 RDI: 0000000000000202
[   47.372683] RBP: ffffffff81654240 R08: ffff88007f239f00 R09: ffff88007bcd1009
[   47.372810] R10: 00000048ffffff9c R11: 00000000080cb818 R12: ffff88007ba2e7c0
[   47.372937] R13: 0000000000000000 R14: ffff88007eeba870 R15: ffff88007eeb5080
[   47.373065] FS:  0000000000000000(0000) GS:ffff88007f700000(0063) knlGS:00000000f72d01c0
[   47.373222] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[   47.373335] CR2: 0000000000000028 CR3: 0000000077f90000 CR4: 00000000000006e0
[   47.373505] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   47.373653] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   47.373782] Process openvpn (pid: 11634, threadinfo ffff8800680d0000, task ffff8800682813d0)
[   47.373987] Stack:
[   47.374099]  ffffffffa05ad2b0 ffffffff81220d02 0000000000000000 ffff88007f33ed40
[   47.374409]  0000000000000000 ffff88007eeba870 ffff88007ba2e7c0 ffffffff810c9a3d
[   47.374720]  0000000000000000 000000c8810cfdce ffff88007ba2e7c0 ffff88007eeba870
[   47.374996] Call Trace:
[   47.375078]  [] ? misc_open+0x10d/0x170
[   47.375204]  [] ? chrdev_open+0x11a/0x139
[   47.375332]  [] ? chrdev_show+0x5e/0x5e
[   47.375442]  [] ? __dentry_open+0x13e/0x231
[   47.375558]  [] ? do_last+0x549/0x574
[   47.375668]  [] ? path_openat+0xd3/0x2e3
[   47.375781]  [] ? do_filp_open+0x28/0x56
[   47.375893]  [] ? mntput_no_expire+0x24/0xd4
[   47.376008]  [] ? do_sys_open+0x60/0xee
[   47.376118]  [] ? ia32_do_call+0x13/0x13
[   47.376229] Code: 48 89 c2 b8 f4 ff ff ff 48 85 d2 74 2f c7 02 00 00 00 00 48 c7 42 08 00 00 00 00 65 48 8b 04 25 40 b7 00 00 48 8b 80 f0 03 00 00 <48> 8b 40 28 48 89 42 10 48 89 93 98 00 00 00 31 c0 5b c3 48 83
[   47.378649] RIP  [] tun_chr_open+0x40/0x53 [tun]
[   47.378803]  RSP 
[   47.378891] CR2: 0000000000000028
[   47.379014] ---[ end trace 3ae4591e608c3e06 ]---

     

    I think it is related to openvpn but I have tried to uninstall the vpn server with no luck. Thanks for your help.

    What if SMART is not supported?

    in Packages & DSM Features

    Posted

    confirmed the smartd working under DSM. I received an email today.

     

    This email was generated by the smartd daemon running on:

     

    host name: vDSM

    DNS domain: [unknown]

    NIS domain: (none)

     

    The following warning/error was logged by the smartd daemon:

     

    Device: /dev/sdd [sAT], Temperature 35 Celsius reached critical limit of 35 Celsius (Min/Max ??/35!)

     

     

    For details see host's SYSLOG (default: /var/log/messages).

     

    You can also use the smartctl utility for further investigation.

    No additional email messages about this problem will be sent.

    Idiots guide to DSM, questions

    in Archives

    Posted

    Yes I downloaded and ran the Synology Assistant for windows. It showed me my Diskstation. When I selected install, I was greeted with an error 38 and an invitation to contact Synology Tech support. A quick search of this forum showed that a code 38 is common and hardware related. I tried a virtual hard drive as recommend and then passed through a LSI 1068e HBA both of which failed.

    I wanted to try out the Synology system because a couple of years ago I was thinking of buying one of their NAS units, until I saw the price. I new that I could build a far better hardware system from server quality components than what they supplied for about the same price. That's what I did. I have since found that the most secure file system that I could use was ZFS, especially since I was about to try every available operating system that works with ZFS. I am able to, and have taken all of my disks of data and moved them as I pleased to any number of computers that run ZFS and did not lose anything. Try that with RAID. The only thing that I really thought would be good to try with DSM was the ability to expand the disk pool as existing HD space was used up. Can't do that with ZFS. Going to Synology's web site I see that they say this can be done, but do not recommend doing so. There goes the best feature of SHR. Now one is running RAID with all its risks, especially Raid 5. By the way, for those running ESXi VM's, RDM's work very well but compared to hot swapping hard drives, it sucks!

    This has been fun, it's part of the hobby. What I had finally settled on, about 6 months ago, as far as an operating system goes is OmniOS with napp-it as the NAS GUI running in a VM on an ESXi 5.1 host. It's all free and reliable, my data has value to me and is as secure as I can make it.

    So enjoy the computer hobby, learn and have fun and thanks for your help.

     

     

    Sorry that I didnt gone through you complete story.

    But I am on the same config and did make it work.

     

    error 38 means the DSM cannot find your hdd.. just that simple.

    you need a boot vmdk (that you cannot install anything on it).

    And afterward, you need to put some other disk for it to install.

    I did experience the same problem of having error 38. I must say that the vmdk is not as good as the ova template package available here. you may try that one first.

    That is a template ova contains a 0.3MB grub boot partition and a data vmdk. The DSM system is already installed as well.

    Idiots guide to DSM, questions

    in Archives

    Posted

    >What I had done was to download everything I needed before I knew how things fit together

     

    so did you download the synology assistant? it should be installed under a windows pc. Available in synology download site.

    Just connect to the discovered DMS station and you are good to install the PAT file.

    What if SMART is not supported?

    in Packages & DSM Features

    Posted

    Ok.. I finally got some error report after waiting some hours.

     

    ===== Email content ======

    The following warning/error was logged by the smartd daemon:

    Device: /dev/sdd [sAT], Failed SMART usage Attribute: 184 End-to-End_Error.

    For details see host's SYSLOG (default: /var/log/messages).

    You can also use the smartctl utility for further investigation.

    No additional email messages about this problem will be sent.

    ========================

     

    I got this error from a Seagate Drive.. but the drive seems running okay..

    Not sure of what the error is about.. ( A internal cache parity issue, but seems common on seagate drive)

     

    And all temperature warning.

     

    BTW, I am not sure if those SMART information from RDM are static (meaning that will not update) or not.

    My drive are always in standby mode from smartctl. I can never wake them but of course they are active.

    The up time does not change either. Hope someone would help to figure it out.

    What if SMART is not supported?

    in Packages & DSM Features

    Posted

    I installed nailx to sucessfully send mail from smartd. And appearently it sent the Test message successfully.

    however, I lowered the temperature threashold to 2,20,23 and it still not sending out any warning email to me.

    I doubt if it is continues monitoring or the smartd is not functionly correctly.

    /dev/sdc -d sat -a -n standby,3 -W 2,20,23 -s S/../.././10 \

    -m xxx@xxx.com -M test

     

    this is the conf file being used in one of my disk.

    What if SMART is not supported?

    in Packages & DSM Features

    Posted

    By wild guess, the DSM may feed the smartctl with -d scsi parameter where most smart data are lost here:-

     

    DiskStation> smartctl -a /dev/sdd -d scsi

    smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.40] (local build)

    Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

     

    User Capacity: 3,000,592,982,016 bytes [3.00 TB]

    Logical block size: 512 bytes

    Serial number:

    Device type: disk

    Local Time is: Tue Dec 24 11:06:18 2013 CST

    Device does not support SMART

     

    Current Drive Temperature:

     

    Error Counter logging not supported

     

    [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']

    Device does not support Self Test logging

     

    Very similar to what I can see from the GUI interface, are there any means to force the smartctl to override the -d parameter?

    using smartctl -a /dev/sdd -d sat is perfectly fine.

    recompile it?

    What if SMART is not supported?

    in Packages & DSM Features

    Posted

    Of course it's a software issue. There's a miss in virtual scsi controller driver, preventing SMART data to reach DSM.

     

    So I prefer making my own solution rather than waiting for someone to code a proper driver for it. Moreover, SMART is just raw data and should be processed a bit smarter to really anticipate hdd problems. SMART status flag may cry when it's to late...

     

    I think you mis-understood my question. The virtual scsi controller passes ALL SMART data to DSM but the DSM just cannot handle it. I am not sure if it is the protocol or parameter issue.

    for example, in the DSM box inside an ESXi with a physical harddisk RDM to DSM..

     

    DiskStation> smartctl --all /dev/sdd

    smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.40] (local build)

    Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

     

    === START OF INFORMATION SECTION ===

    Model Family: Hitachi Deskstar 7K3000

    Device Model: Hitachi HDS723030ALA640

    Serial Number:

    LU WWN Device Id: 5 000cca 225c186bb

    Firmware Version: MKAOA3B0

    User Capacity: 3,000,592,982,016 bytes [3.00 TB]

    Sector Size: 512 bytes logical/physical

    Device is: In smartctl database [for details use: -P show]

    ATA Version is: 8

    ATA Standard is: ATA-8-ACS revision 4

    Local Time is: Tue Dec 24 10:27:56 2013 CST

    SMART support is: Available - device has SMART capability.

    SMART support is: Enabled

     

    === Detail are all listed below ===

     

    The problem is how DSM can make use of these data, it shouldnt be that difficult as the smartctl already read all parameter.

    In fact, in the DSM page, the smart status for all RDM drive are showing Normal. But when I clicked into Smart info, it was telling not supported.

    available volume size is insufficient

    in Archives

    Posted

    I have created a volume but wanted to restructure my raid layout.

    Then I created another volume and move most of my share folder to the new volume.

    However, when moving the largest share folder the captioned error occurred.

    "Operation failed because available volume size is insufficient"

    The folder is around 1.6TB in size and my new volume has 2.3TB free space.

    I have no idea on why it happen. Before I try to manually moving the file in ssh I would like to see if someone knows the problem first.

     

    Thanks a lot.

    Receiving Alert Message from other DSM users

    in Archives

    Posted

    I read somewhere that there is no need to modify serial / MAC if you have only 1 DSM and not requiring WOL.

    So I installed the package with default settings.

    However, when I set the DS CAM, I already received some motion detection alert from other DSM devices, even though I disabled all my Camera.

    I also receive some alert email that were totally non-sense to me. Like hdd overheat (where I uses ESXi so no SMART status could be detected).

     

    Is this something like notification center that will remeber some of the key for broadcasting DSM system message?

    How can I prevent? thanks alot.

    [SOLVED] Install on vmware ESXI

    in DSM 5.2 and earlier (Legacy)

    Posted

    I have spent lots of time in making RDM to work on my ESXi box but in vain.

    After reviewing the website, almost all resources uses the VMware Paravirtual SCSI (PVSCSI) Type.

    That casue my Synology to shutdown right after initialize.

    I finally managed to map the RDM using LSI Logic SAS as the controller type and the performance is satisfactory.

     

    If all does matter, I tried to change the HDD type to IDE first and found it regconized by DSM 4.3. And then changed it to SCSI with LSI Logic SAS as controller.

    At this point of moment, I only have 1 disc using RDM for testing and built a SHR (single drive) and iSCSI LUN + target on top of it. And this LUN were redirect back to used by the ESXi host. Everything seems fine at this moment.

×
×
  • Create New...