Posts by Spy Alelo

I don't know, that really looks like a hardware problem to me. You could try removing the CPU and clean the contact pads with 100% isopropyl alcohol or some other weak solvent, and try reinstalling it. If you accidentally touched the CPU underneath when installing it, over time you may build up a little bit of corrosion on the pad contacts and can lead to problems later. This is assuming that all your hardware is 100% okay. You can also reseat the memory DIMMS and any other peripherals you have to make sure.

Quote from irwazza

What version of Norton ghost do you use?

I've used Ghost 11.5. I am not sure at what version they are at right now, never bothered upgrading from there.

Quote from tekkb

Does Ghost support Ext4??? I don't see it mentioned on their website.

They did support ext3 and they do have a version of Ghost that runs on Linux, but that was a while back. I am pretty sure they handle EXT4 (not that it makes that big of a difference) and it works real well. You can use the Windows version of Ghost too to clone EXT drives, makes no difference.

Format from SSD or HDD will be the same, you can clone it just fine. For TRIM support, you just need at least kernel 3.2 and some changes to your fstab. Here's a link with more info about that: https://wiki.debian.org/SSDOptimization.

The new drive can actually be smaller, but the rule is that it has to be big enough to accommodate the data that the original is currently using. For example, if your original drive is 250GB and only 10GB are in use, any SSD of 16GB or above will work just fine. Utilities such as Norton Ghost recognizes these differences and resizes each partition by percentage, or prompts you to assign new partition sizing before the cloning begins.

Is up to you if you want to start from scratch, but there's really no reason to do that. I've moved from HDD to SSD for several systems anywhere from Debian, to Windows and even OSX. With the right tool, you'll be just fine.

Don't overcomplicate your troubleshooting. Usually when a system experiences hard-locks for no apparent reason and at random, the first thing you need to check is for RAM problems. Prepare yourself a disc or USB drive with memtest86+ or any other memory tester and let it run its course to see if there are any issues. It can take up to 24 hours to do a through test.

If there are no problems with the RAM, the other thing to look into is into a power supply defect and NOT lack of power. 7 modern hard drives the most that they will consume at full load together would be around 75 watts, if that. The most a power-hungry i7 CPU would would consume would be 120W. Your whole system with that i3 processor and drives would not even touch 150W on full load if you are just using its onboard video chip. That doesn't mean that you don't have a power supply issue! Like I said, it could be defective if the memory tests pass.

If you are sure that your power supply is good or you replace it and the issue persists, next thing down the line is the SATA cable for the OS drive, or the OS drive itself.

Thermal issues are a thing of the past if your CPU is being cooled adequately. They can tolerate upwards of 100C with no ill effects, and you just mentioned that your case will not go above 30C internally which makes me doubt it even more.

Motherboard would be last. Motherboard brand DOES matter when it comes to durability and overall stability. Using a cheap $40 board like ECS (do they still exist?) or BIOSTAR that came as part of a CPU bundle deal is not the best alternative for a server. Risking a pointless debate by others about brand X being better than Y, I will share with you the best boards I've seen suitable for 24x7 use with little to absolutely no issues:

SuperMicro
Intel branded boards, not just Intel-based
Modern high end MSI boards (they got better in the last few years)

For power supplies on the consumer end, SeaSonic is the absolute best in durability and there's no debating that. That durability also comes with a somewhat high price tag.

I typically wouldn't use anything else for server use on the cheaper side of things. To those that disagree, keep in mind that I am not talking about which board over-clocks best or which is faster, or which one has more features. This is just from experience working on data centers where servers have to meet a minimum uptime of 99% and durability is expected of at least 3 years. Good luck!

Well I just noticed a pattern on your logs:

Dec 24 17:23:06 SJOMV afpd[27537]: afp_alarm: child timed out, entering disconnected state


Dec 24 17:23:06 SJOMV afpd[27537]: dsi_disconnect: entering disconnected state


Dec 24 17:23:06 SJOMV afpd[27537]: dsi_wrtreply: Bad file descriptor


Dec 24 17:23:06 SJOMV afpd[27537]: dsi_disconnect: entering disconnected state


Dec 24 17:23:06 SJOMV afpd[27537]: dsi_disconnect: entering disconnected state


Dec 24 17:23:06 SJOMV afpd[24808]: AFP3.3 Login by Wastl


Dec 24 17:23:06 SJOMV afpd[24808]: afp_disconnect: trying primary reconnect


Dec 24 17:23:06 SJOMV afpd[15073]: Reconnect: transfering session to child[27537]


Dec 24 17:23:06 SJOMV afpd[15073]: Reconnect: killing new session child[24808] after transfer


Dec 24 17:23:06 SJOMV afpd[27537]: afp_dsi_transfer_session: succesfull primary reconnect


Dec 24 17:23:13 SJOMV afpd[24808]: afp_disconnect: primary reconnect succeeded


Dec 24 17:23:55 SJOMV afpd[19174]: afp_alarm: child timed out, entering disconnected state


Dec 24 17:23:55 SJOMV afpd[19174]: dsi_disconnect: entering disconnected state


Dec 24 17:23:55 SJOMV afpd[19174]: dsi_disconnect: entering disconnected state


Dec 24 17:23:55 SJOMV afpd[24858]: AFP3.3 Login by Wastl


Dec 24 17:23:55 SJOMV afpd[24858]: afp_disconnect: trying primary reconnect


Dec 24 17:23:55 SJOMV afpd[15073]: Reconnect: transfering session to child[19174]


Dec 24 17:23:55 SJOMV afpd[15073]: Reconnect: killing new session child[24858] after transfer


Dec 24 17:23:55 SJOMV afpd[19174]: afp_dsi_transfer_session: succesfull primary reconnect


Dec 24 17:23:57 SJOMV afpd[24858]: afp_disconnect: primary reconnect succeeded

And this:

Dec 23 08:51:20 SJOMV afpd[9187]: AFP3.3 Login by Alois


Dec 23 08:51:20 SJOMV afpd[9187]: afp_zzz: entering normal sleep


Dec 23 08:53:22 SJOMV afpd[9187]: AFP logout by Alois


Dec 23 08:53:22 SJOMV afpd[9187]: AFP statistics: 1479.59 KB read, 55168.04 KB written


Dec 23 08:53:22 SJOMV afpd[9187]: done


Dec 23 08:57:05 SJOMV afpd[9608]: AFP3.3 Login by Wastl


Dec 23 08:59:28 SJOMV afpd[9608]: AFP logout by Wastl


Dec 23 08:59:28 SJOMV afpd[9608]: AFP statistics: 65768.39 KB read, 88139.68 KB written


Dec 23 08:59:28 SJOMV afpd[9608]: done


Dec 23 09:51:15 SJOMV afpd[13599]: AFP3.3 Login by Alois


Dec 23 09:51:22 SJOMV afpd[13599]: afp_zzz: entering normal sleep


Dec 23 09:53:17 SJOMV afpd[13599]: AFP logout by Alois


Dec 23 09:53:17 SJOMV afpd[13599]: AFP statistics: 1257.24 KB read, 55155.51 KB written


Dec 23 09:53:17 SJOMV afpd[13599]: done


Dec 23 09:57:05 SJOMV afpd[14018]: AFP3.3 Login by Wastl


Dec 23 09:58:29 SJOMV afpd[14018]: AFP logout by Wastl

It is very odd, but it could be a Time Machine job gone wrong attempting again and again to finish or start. I've seen this kind of behavior before with Snow Leopard and even Lion. All I did was remove the old backups from the NAS and redo them from scratch. Let me know how that goes.

Well I sort of steered away from the subject, sorry about that. It is odd that you have that problem though. I do have mine with AFP and I am getting full 120MB/s speeds and I didn't have to do anything special to achieve that. My only suggestion is to turn off Service Discovery from the Network section on OMV for everything but AFP. Also make sure that the name represented in that section is the same you use in the description section for SMB. That way, OSX will know is the same server and only present you with the AFP mount options. My only theory is that you may be using a service that may not actually be AFP, even if it works. I had a hard time telling the services apart until I turned off discovery on everything but AFP.

Most SSDs are under-provisioned already for that kind of stuff. A good example would be Corsair with 120GB of capacity, but the actual NAND is 128GB. Same with Intel, I have a 240GB one that in reality has 256GB worth of NAND. There's no need to limit the capacity yourself in any way or fashion. In fact, some manufacturers even include utilities to unlock the rest of the storage. Not that you really should though.

Quote from PAPPL

Solved: http://forums.openmediavault.org/viewtopic.php?f=11&t=1417

You have to take those settings with a grain of salt. You only want to adjust that for writing performance issues, should not affect reads from the NAS. For my setup, 256 pages was working okay but it wasn't best. I reduced it to 128 pages and I was able to get constant 120MB/s writes. That's with my current setup of x3 drives on RAID5. For a friend of mine, the 256 pages cache for stripe was best, and he has RAID6 with about 12 drives. Going under or above has serious side effects on the writing performance, I don't understand how people can adjust that at such an insane high level and expect good results. There's a reason for the Debian devs to be conservative about this setting.

For future reference, if you happen to use the onboard NIC on a new system while using the same OS install, you want to edit:

/etc/udev/rules.d/70-persistent-net.rules

Simply update the MAC address with the new one and shut down the system, do your upgrade. Otherwise you may not get the OMV GUI after the upgrade, since it will identify the new NIC and assign it as eth1 instead of eth0.

Consider a modestly sized, inexpensive SSD drive for the OS in the future once OMV 1.0 is released. You can go as little as 8GB if you like.

Even though Realtek chips usually work okay, I've never been able to saturate the link completely. The most I would get from them is typically around 500Mbits/s, or 60MBytes/s. With Intel chips, I am able to go at full speeds with hardly any CPU utilization. I am not sure if is an issue with the Realtek chips or drivers, but in all these years, Intel has never failed me. Just remember that in order to take advantage of the full speeds, the client NIC would have to be Intel as well, or at least a high quality chip other than Realtek.

Quote from WastlJ

I would absolutely test this thing. It could save a lot of money. Also looked a bit into it. But how do you want to get the pre boot screen to work?

>>Waiting for a dedicated thread Spy Alelo

Well that would be why an external, embedded computer would have to capture the video regardless of the server's state and one of those things that would need to be engineered. Perhaps using an FPGA to capture and compress the video. I am a bit afraid of starting a thread yet since I'll need some help with the design, soon enough though.

Is actually doable. Like I said earlier, something tiny like a Raspberry Pi, it can serve a webpage and completely manage the target server as an external device. The only thing to do internally is run the power and reset wires to it so it can control power and hard resets. I will definitely look into it, I might be able to come up with a prototype.

I absolutely agree. I can't say much about it, but I'll give you a hint for Intel systems: Intel ME. If we can tap the potential of Intel's Management Engine, we could at least have a solution for people using boards that include the ME features. I am not sure to what degree though, since you have to do crazy things such as JTAG programming on the fly and they are kind of strict on what works with it and what doesn't. There is also the possibility of simply tapping the actual hardware by using pin headers, and use an FPGA to take video signals and encode them digitally to be used over the network. That would work with anything.

Yeah, iLO is very proprietary, but also it is tied up at such a low level within the hardware, that you really don't want to mess with it. Plus since is independent of what you install, it doesn't really matter. What I would like to see, would be an OpenSource solution with open hardware for any type of computer. For example, a very small computer such as a Raspberry Pi that can take control of the hardware and pass on things such as KVM over the network. It can be challenging though, is not an easy task. But that's basically what iLO is: a self-contained computer that admins your server remotely and provide KVM over IP.

*Edit: Damn auto-correct on OSX

Yeah I don't know what happened to it. I was able to login a few days back, and a few days later, it was gone. No biggie though, at least I was able to use the same nick.

Quote from buranov

Good day!

I finally finished my NAS!
Platform: HP Micro G7 N54L
RAM: 8GB ECC
System disk: SSD mSATA KINGSTON SMS200S3/30G
Adapter for mSATA: Syba HDD SATA 6Gb/s + SSD mSATA Hybrid Drive PCI-Express x1 Card (SY-PEX40053)
Options for server: Micro Server Remote Access Car
HDD: 5 x 3.5" WD Red WD40EFRX 4TB + adapter for 3.5'' in 5.25''.

Result: I have great NAS 14.3TB (RAID5 software), remote manage (for full backup system) and very fast system (SSD).

OMV team, thank you very much!!! You are best!!!

Display More

Glad you like it! That's an awesome little server that you have, by the way. I work for HP in the R&D labs, and let me tell ya, that's one of our favorite designs. The best feature you have is the iLO management that is built-in, and is a very flexible little unit. Just make sure you keep up with the firmware updates on it, there was a lot of work and changes that we did over the time to improve the system overall.

Well guys, I'm back after some absence and for some reason my account got deleted so I had to recreate it. I'll try to dedicate some more time to help you guys out with whatever you encounter and hopefully I'll get back my mod rights. Happy to be back!