htpcdude

You may find that the BIOS on the Supermicro motherboards are incompatible with DSM. Search the forum for BIOS reset issue.

I had the same problem going from Nanoboot to XPEnoboot on one of my motherboards. I got it working by going into the BIOS, Boot, USB Mass Storage Emulation Type and changed the setting from "Auto" to "All Fixed Disc"

I got motion working on mine. I was wondering what web cam you are using and what resolution/framerate you are using. Thanks,

So MotionPie is the only thing running on your Raspberry Pi. Did you look into installing motion on top of Raspbian (Debian Wheezy)? This would allow the Raspberry Pi to do other things.

Then your USB ports are working. Are you using Nanoboot?

If you plug in a USB keyboard and connect video, does the keyboard work via the console (log in)?

You will find the answer if you search J1800 viewtopic.php?f=2&t=4033&p=24084&hilit=j1800#p24084

I do not think you can use USB drives in raid

I run mine off of a Dell E6400 laptop. You will find the eSATA of the laptop is not port multiplier friendly. It will only see one drive in an eSATA JBOD enclosure. You can use an eSATA RAID enclosure. I took out my CD-ROM and installed a hard drive SATA bay to have a total of two 2.5" drives in my Xpenology.

Solved by aas123plo. viewtopic.php?f=2&t=4033 Specifically Chipset, South Bridge, USB Configuration, XHCI Mode to Enabled

Thank you. I had the same problem on the GA-J1800-D2H. I was changing all different settings when I saw my usb working. I wanted to confirm so I reset my BIOS to defaults and did a fresh install. Of course I was so confident of what I was doing so I didn't write down my settings. Two weeks later and my USB ports were still not working until your post.

And it is trivial to recreate the USB boot drive

Why are you telling him it can't be done when fma965 has posted a guide? http://cyanlabs.net/Thread-Install-Nano ... h-USB-ESXi Have you tried to follow the guide and confirm it doesn't work?

Since I posted saying this was doable, I feel obligated to make some additional comments. You are right, it seems this is only possible with an IDE (PATA) device. The DOM (Disk On Module) devices people are using are IDE DOMs not SATA DOMs. XPEnology on ESXi hosts are also booting from a virtual disk running off of a virtual IDE controller.

This is doable although I have never tried it. You'll can search for posts on XPEnology on ESXi hosts, as they use a virtual disk device to boot. Or search for posts where people are using a DOM instead of a USB flash drive. The answer is in the forums but you have to do the detective work in finding it.

Please google 'amps to watts.' P(W) = I(A) × V(V), Power in Watts = Current in Amps X Voltage in Volts So your 20v 3.25 amp brick puts out 65 Watts. You need a more powerful AC adapter, probably 90 Watts at least.

I had the same thoughts until I realized I can buy a pico power supply which has the DC power input and plugs into any standard motherboard.

There is no need to discuss this back and forth. It's very easy to figure this out yabba235, install a brand new Nanoboot system on spare hardware and look for evidence. I have 3 Nanoboot systems and none of them have these files in root. 2 were upgraded from Trantor, I don't remember about the third as I've tested everything on that system. The sky is not falling.

Is it possible for you to go back to gnoBoot temporarily just as a test? If you can and WOL is working, then run lspci -v to see which kernal mode driver is being loaded for the NIC. This should tell you which NIC driver you should be using in Nanoboot. insmod this NIC driver and rmmod the other two. Also, have you confirmed that Synology Assistant shows the actual MAC addresses of your units? If not, add to kernel /zImage line mac1=xxxxxxxxxxxx

Correct. The DQ35JOE went into production with Trantor's 4.3. I cannot guarantee you will have no problems with it. There are some features of DSM I never use nor tested, such as iSCSI and high availability. I tested all the DSM 5 releases on my Gigabyte GA-H87M-HD3 and an Intel DQ35MPE. The DQ35MPE is very similar to the DQ35JOE, they even use the same BIOS. But do not get the DQ35MPE, it has a chipset bug which doesn't like the partition table DSM puts on the hard drives. There is a work around so I still use it for testing purposes. It also does not have the BIOS reset issue.

If I recall correctly, started with Trantor's 4.2 builds on the Supermicro PDSME+, didn't work. Then tried various ASUS motherboards, some had BIOS reset issues. Found one that didn't and had decent lower power draw but NIC was only 100mbps. Did some research, gambled on buying the DQ35JOE and decided to use it. At this point I was using a Trantor's 4.3 release. DSM 5.0 was announced. After a lot of testing with Trantor's 5.0 beta, gnoBoot's and then Nanoboot's releases, decided on Nanoboot. Upgraded the DQ35JOE system to Nanoboot's DSM 5 about 2 weeks ago.

I believe, DSM of the earlier version does not suffer the same BIOS resetting problem as DSM 5.0. If you switch over to DSM 5.0, I think you will have the same BIOS resetting problem as I am. So, the bottom line is, to solve my problem, I need to use earlier version of DSM and not DSM 5.0 My initial exposure to Xpenology was with Trantor's 4.2 and 4.3 builds. I ran into the BIOS resetting issues on my hardware until I found compatible motherboards. DSM 5.0 had not even been announced at this point.

Hi htpcdude What can I say!!!! Firstly, a BIG THANK YOU to your advice and sharing your experience to me!!! Secondly, you are my life saver, after reading your advice, I think I sleep better now instead of think ways all day and night to fix this annoy problem. Thirdly, did someone from the team of developers, forget to write about this known issue in the FAQ section? Fourthly, there is a section in the forum discussing whether the DSM OS is compatible with 3rd branded motherboards, why there no WARNING note in regards to the BIOS reset problem? Please refer to: http://xpenology.com/forum/viewtopic.php?f=2&t=33 or perhaps this: http://xpenology.com/forum/viewtopic.php?f=2&t=854 Ok let's summarized what options I have got now that I read your advice loud and clear! Option 1: Buy a Intel branded motherboard (The DQ35xxx series) Option 2: Buy a Gigabyte GA-H87M-HD3 motherboard (not sure about there other models.) Option 3: Buy a Asus motherboard- any model and any platform: Intel or AMD. Option 4: Buy a UPS for supply power at 24/7 to XPEnologized Supermicro PDSME PC. For the time being, in my case, Option 1 to 3, any of these options mean that I need to buy: 1) New CPU 2) New DDR3 memory 3) New motherboard which I need to do some hard thinking before I proceed. So.... for your case, which Intel motherboard from the DQ35xxx series did you use which does not have the BIOS resetting issue??? Can you care to eloborate? Are you using this Intel motherboard Intel DQ35J0E motherboard, please refer to the link: http://www.newegg.com/Product/Product.aspx?Item=N82E16813121094 which has 6 SATA ports, which to me is more than enough to play with In that case, if it is still available on eBay, then I may buy it to try myself and I don't have to do anything else, except swapping the motherboard out the case. I may want to buy an Intel motherboard because of Intel NIC which performs better than other NICs, namely Realtek. Thank you again. Yes I am using a DQ35JOE. I don't use the power settings myself but have just confirmed that I can set a shutdown and wake up schedule that works without issue. I'm running Nanoboot-5.0.3.1 with Synology's DSM_DS3612xs_4493.pat updated to DSM 5.0-4493 Update 1. As I was writing my first response, it did occur to me what MikeRoxx said may work. I did not think of this when I was testing the Supermicro board and I've since bought other motherboards that work. My next Xpenology box will use the Gigabyte GA-H87M-HD3 but I would not recommend it. It has a Realtek 8111F NIC which gave me problems and took me a month to find the fix. I'm just waiting for 4TB hard drive prices to come down a little more.

BIOS reset issue is a BIOS hardware compatibility issue with DSM and your motherboard. It does not matter whether you are using Nanoboot, gnoBoot, or Trantor. It can happen even if you don't set a power schedule. Deep down, DSM wants to keep time in ZULU time (GMT), not your local time standard. It wants to write the ZULU time to your BIOS, just like Windows wants to write your local time to the BIOS. DSM expects certain hardware and will write to the BIOS the only way it knows how. If your BIOS is not compatible, this write will corrupt your BIOS settings, resulting in a BIOS reset. I've found DSM doesn't like the BIOS from Supermicro but is ok with ASUS. I have the PDSME+ and you will not get this board to work. With ASUS BIOS, I can set the shutdown time but setting a wake up time corrupts the BIOS. The best compatibility I've found so far is from Intel motherboards, specifically the DQ35xxx motherboards. I am able to schedule a wake up time with the Intel motherboards. I also have a Gigabyte GA-H87M-HD3 that doesn't have the BIOS reset issue. DSM probably also doesn't like UEFI.

Please stop referring to Nanoboot as Trantor Nanoboot. Nanoboot is made by Sancome https://translate.googleusercontent.com ... 7-ya4kumFw Trantor has been nice enough to host the files on his site because the hosting sites used by Sancome had been slow and problematic. Edit: I reread your posts. Are you asking to upgrade from Trantor DSM 5.0-4418 Beta to Trantor DSM 5.0-4493? You can't. Trantor has not released any update to DSM 5.0-4418 Beta. You can upgrade from Trantor DSM 5.0 4418 Beta to Nanoboot 5.0.3.1 DSM 5.0-4493