fonix232
-
Posts
324 -
Joined
-
Last visited
-
Days Won
1
Posts posted by fonix232
-
-
Is not working in Virtualbox x86..After format and install DSM, display error 22 and no boot.
Error 22 means the boot disk (GRUB) is damaged.
-
Now, that's strange.
I have 4.2 3202 on 4 HDDs and took one of them today for service and before wiping i saw that there were about 4 partitions on it but the one for the system is quite small, nevertheless, not 300GB
Neither are, but I still can't really add it as a partition, tried it and it got wiped :\
-
DSM is installing on all HDDs in the defined RAID or just on one HDD if you don't have a RAID matrix defined.
I tried to install it on a flash but i couldn't and i didn't tried alot.
I think it could be done with VirtualBox and some commandline but it's not really recommended because of many things.
I get that first part, and it is understandable, but still it eats up all the 300GB, making it unusable. And as I said, it has no errors whatsoever, but apparently the filesystem is not created.
-
What are you trying to do? To update from the flash dongle or to install DSM on it?
I want to install it on the flash drive, as I don't have a small enough spare hard drive to jam it into the case (and I don't want to waste my 300GB one on a simple 500mb install
) -
I have perl installed via the Official Synology package server.
You can try a manual install with the latest file from: http://ukdl.synology.com/download/packages/ You should take bromolow if i'm not wrong.
Cheers
PS: you will have to perform manual updates if the official package center is not available, but i think you figured this out by yourself
By now the official server is up, and figured out that Perl requires 4.2, but modified the package a bit and now it's installed!
Really final thing is to figure out how to install this on my 8GB USB flash. Installer goes through fine, but apparently it does not save the update file on the disk...
-
Thank you very much. One more question: where the hell can I find the "Perl" package (non-ipkg)? Many apps need that, but I simply cannot find it in any package server...
-
have you tried build 3202?
The only problem i had is the "additional" hardware i have like PCI-SATA-ESATA RAID CONTROLLER (not really a branded one) and a GIGABIT USB3.0 Network Card. The rest of the system works let's say... native.
I tried all 4.2 builds, so far none worked. All got stuck at the "Booting kernel." part of GRUB, so apparently there's something in the additional hardware kernel what makes it boot.
About hardware incompatibility: Synology detected neither my WLAN PCI card /Linksys WMP300N), nor my TV card (some Asus stuff without model marking, so it cannot be that mainstream to be supported by the linux kernel, or was simply not compiled into). Otherwise, it detected the mobo's ICH7 controller, three hard drives are working right now (quite annoying that I can't create an additional partition on the original drive, as it is 300GB, and I don't think Synology needs that amount of space, so it should be possible to use it for e.g. user home folder storage, location for the web host services, etc.).
EDIT:
After two restarts, and by installing the ipkg bootstrap, it seems to be working. The Synology server reports a busy status, but custom servers work. Now I only need a list of usable servers
-
So, I got a new toy, a "shiny" HP m7000. Celeron D 346, 2gigs of RAM, a 300GB builtin HDD (plus my two 1TB ones), and ofc no onboard graphics.
Fortunately the network card is supported by the e100 package, so I could successfully boot and install build 2668++, the "more hardware" version. Everything is fine, except that I get an error any time I try to use the Package Center. The "Connection Error" stays even if I add custom package sources, so it's not related to the Synology servers.
Did anyone encounter this same problem? If yes, how did you solve it? I installed Synology mainly for the easy extra software installation, and now that it is gone, it is not appealing at all. I want my packages back
-
What build used
DSM 3.2 build 2031
Please detail. Download link, exact steps, etc., it is all important.
-
Could you please share the exact build and kernel you used? Although my goal would be rather 4.1 and 4.2, a booting 3.2 would be a step forward on my P4 machine
-
That's the 4.1 source, it will probably not work with a 4.2 base system.
Probably why I got the version errors when I tried. Sorry about that.
Associated to one of the links posted above I can see this repository: https://github.com/Vincentxiaojie/xpenology (which is different than the URL for the tools)
Is this the same?
Yes it is, you can see it on the top:
Vincentxiaojie / xpenologyforked from andy928/xpenology
-
Hi folks!
I have a P4 with IDE HDD (really
) running freenas. I don't really like freenas and XPEnology seems to be a really good solution.Do you think my config will work with XPEnology? I did not have the information of the board (I think it's an Intel) yet but I think I can get it.
What do you think?
Thanks!
yaaa4
I'm trying to do something similar, though I have a RAID array of two SATA 1TB hard drives hooked up on an IBM 8183 (ThinkCentre S50), with a USB drive hosting OMV at the moment.
Little successes of mine include making the 4.1 kernel compile for x86, and basically that. It hangs on "Booting kernel..", and no matter what tags, flags, options I add to GRUB, it just simply won't go any further.
-
Hello,
I am sorry i didn't explain myself correctly. I am looking for the XPEnology files (and not the Synology files).
Thank you
Marc
Then maybe this (from the post above this one)...
That's the 4.1 source, it will probably not work with a 4.2 base system.
-
Hi Folks,
I need your help. I started to install the XPEnology DS3612xs DSM 4.1 build 2668++ (more hardware) version. However, in my haste, I forgot to un-plug my USB 1TB drive. When I realised this it was too late. Now it's formatted my partitions I had. I am desperately trying to recover my files. Apart from running a partition scan, does anyone know whether there's an easier method? I'm not sure what the setup would have done but I'm hoping those that are farmiliar with the installation process may be able to help me out.
Thanks in advance.
If you had Windows-supported partitions, you can try many of the Partition Recovery tools. I myself usually use Easeus Partition Recovery, for a few reasons:
- Free (both personal and commercial use)
- Unlike their Data Recovery tool, it can recover lost partitions, write partition table back, etc.
- Supports a lot of formats (NTFS/FAT, HFS/HFSX/HFS+, Ext2/3/4), the ones you usually use
- Does not need a WinPE boot disk
Although I usually use it on Windows deleted partitions (such as soft-formatted external hard drives, etc.), you might have some luck with it.
-
I recompiled the kernel with DSM 4.2 toolchain (adding sata_via support for a VIA VT6421 PCI SATA card). Everything seemed to go well - I was able to start the PC with modified USB-key, but after some 25 seconds, it sent the kill signal and the PC went off.
I've got error messages, stating:
loop: version magic '3.2.30 SMP mod_unload ' should be '3.2.11 SMP mod_unload '
The system is going down NOW!
I suspect this discrepancy being the cause for the kernel panic.
Any idea for a workaround, how to get things running?
Regards
It is apparently a version mismatch with some modules. It seems like if you had a newer version module (3.2.30) on an older kernel (3.2.11), and it fails to load the SMP module. Did you replace both the zImage and all the kernel modules?
Thank you for this project. do you free to show us how to build a SynoBoot.img and add more hardware support?As far as my research goes, SynoBoot.img is a simple DD dump of a custom-made GRUB boot USB.
It contains two partitions:
1. A small, 16MB partition for kernel zImage, minimal initfs rd.gz, and GRUB config
2. A bigger partition, around 200MB,contains the same zImage, rd.gz, PLUS the DMS filesystems (checksum files, hda1, etc.)
Creating a working boot drive should be fairly easy, even by hand.
Create an empty 256MB file
dd if=/dev/zero of=./boot.img bs=1M count=256
Then create an according loop mount, and attach this file
mknod /dev/loop[NUM] b 7 [NUM] losetup /dev/loop[NUM] boot.img
After this, you can use fdisk to create the two partitions, then use grub-install to install grub on the device (don't forget to mount the first partition, create a boot folder, and target grub-install to that folder. It will be overwritten, but otherwise it fails to install). FS format should be ext2.
When all is done, pop an existing SynoBoot drive in your PC, and copy the contents, then you can modify it.
When all done, do an umount boot.img, and dd it onto the flash drive. Then double-check it, set a bootable flag, and you're done!
I've began working on a kitchen for editing these firmwares (and compiling kernel, patching, etc.), but given that I can't really boot any kernels as of now, it is quite hard to test. So either hardware donation (anything small that can boot up Synology), or some help with the i386 kernel support can come handy!
-
I have the same problem with 4.1 build 2668+, though I built my own kernel for i386 support.
It seems to be that it either fails to load a module thus hangs, or the initscript does something it shouldn't do on the hardware.
Maybe someone has an idea what's happening?
-
Instead of editing, I'll add new posts of progress.
So, after some hackery, figured out a few things.
- The synoconfigs/x86 config file SUCKS. It won't compile, it is old, needs a lot of update. Grew tired, grabbed the x86_64, removed 64bit support and added 32bit.
- My network card needed the Intel e100 driver, and it should work now
- After a minimal patching around in the kernel tree, x86 now can be compiled easily. Will do a pull request later, but I cannot be arsed right now.
Using 4.1 x86_64 toolchain, x64 base OS, x86_64 modified config, base is 4.1 build 2668+
The root of the problem is the arch/x86/kernel/sys_i386_32.c file. While the sys_x86_64.c is nice and up-to-date, i386 received no love at all, is not working, compile dies. Given that my C skills are near nonexistent, I needed some time to figure it out.
First try was to make a copy of the 64bit version, remove 64bit stuff, and compile. While it did get through the initial problem, it caused another. In particular, both the 64 and 32 bit files were referenced, and as they were the same, there were colliding definitions of functions. So it had to go.
Second try was successful. Replaced the SYNO function in 32.c with the one in 64.c, and added the sys_mmap declaration too, from the same place. Now it compiles perfectly, without a hiccup!
So made a flash drive, replaced the zImage, and the modules in rd.gz. Had to move and resize the partitions though, as my new modules were a bit oversized. So a request to the guy who makes the synoboot.img - pretty please, make the grub boot partition a tad bit bigger! Let's have a standard 256MB image, 64MB for the boot partition, 192 for the system, and it should work!
So, replaced zImage and stuff, let's see this puppy. Smashed my drive into a port, booted from it. HAH! No more incompatible kernel message, it loads the zImage, then boots. At least it says so, because nothing happens, network does not come on, and it just hangs there. There is no network connection, so it does not get to load the compiled-in kernel modules, meaning it is definitely not one of the extra *.ko files.
If anyone has any kind of suggestion, please do share!
-
I suppose you used a screen with the PC, so please, could you tell us what was written there? Did it hang at the "Booting kernel." message, or did it go further, display any error message, or something? That would help a lot!
-
Hi, i have problem on installation of xpenology system, my material is
core 2 duo E6550 & Asus P5E3 deluxe wifi i write img disk (just .img file in the rar) with Win32DiskImager, the system started but it block in Loading the kernel ...
with the ver 4.2 i have error message (cheksum invalid) and with 4.1 no error message but the os not start (block in loading kernel)
thx for help me
I believe it actually should stop there. If you read the instructions carefully, you notice that first time boot is kernel-only, so that you kinda "emulate" an empty Synology NAS, then use their Synology Assistant to install the full software.
What you should basically do is to let it sit on the "Loading kernel..." message, go back to the computer you are installing from, and follow the steps detailed in the first post.
-
Unlikely that measurement was complete, from the wall, or with three drives attached - which use that much power alone. You could save a bit of power with SSDs - but you would lose storage. An atom-based motherboard would save a chunk of power at the cost of CPU strength - which little is needed for a pure storage medium.
Well, I prefer my "storage" full-blown - download client, web host, LDAP server, VPN server, network media player (DLNA, cataloging of the server contents, etc.).
Right now it is solved on a P4 platform with 1GB RAM, an IDE drive for OS (OMV with Plex for the media part), and my 1TB SATA drive for storage. Hardly optimal, but as soon as I can get XPEnology boot on this old piece of junk, it will get better.
As for the power usage, IF you are stupid enough to set the disks to fast sleep (5min idle), it can cut on the power usage. But of course it all depends on how often do you access it, how much data transfer occurs, and so on.
Back on topic, best would be a Mini or NanoITX board, with the proper case, Intel 1155 socket, 2-4 gigs of RAM, and of course, the hard drives.
-
I'm looking to build a low power system can anyone suggest a motherboard that is very low power to use for this
...what fonix232 said.
I just built a system. Gigabyte GA-H77N-WIFI mini-ITX, 8GB RAM, i3-3220T, three drives active and it measures 40W at idle from the plug.
40W is still quite high in idle, there was a guy who made it down to around 6W with an i5 3rd gen.
-
I'm looking to build a low power system can anyone suggest a motherboard that is very low power to use for this
Depends on what you want to build.
- What is the size and socket? Do you want Mini-ITX, Nano-ITX, or something else?
- What is low-power by your definition? 150W? 50W? 20W? All can be done. Also, which mode should be low-power? Idle or active use?
-
Hey guys!
I would need some help. Got a shiny old IBM desktop (Thinkcentre 8183) from my neighbour who decided to replace his old IT stuff with new gear, and decided, why not make a home NAS out of it, just for the heck of the thing?
So scavenging began. First thing I did was to get rid of the built-in floppy and CD drives, and to extend the memory to 1GB. Then I put my one of my 1TB data drives in there (SATA2 Samsung), plus kept the old 40GB IDE drive for the OS.
First played around with FreeNAS. It was great, but not Linux, unknown system, low support for things I need.
Then came OMV. It is great, but needs a lot more feature, more stability, and less resource-eating. Overall it was a good experience, but not exactly what I was looking for. I needed more, and less. More on the user interface end, and less on the backend.
After looking around, I found out about Synology, and their NAS systems. Shiny UI, lot of extensibility with features I want (torrent server, NAS function, media streaming, etc.), and seemingly easy installation.
First problem was, that this old P4 is not 64-bit enabled. So I searched, and found a REALLY old build for the DS411+, and it was 32bit. Flash to a flash drive, insert it, boot. Finally, no warning about the kernel being x86_64, while the hardware is i686 only. Network vender MACs seem to be in order too, so lets see what happens and how. Started up the Synology Assistant, and it began the search. Nothing found, so I looked a bit more into it, and turns out, the computer is not even connected to the network!
So booted back to Ubuntu, and checked the NIC. Of course it is a frakking old Intel 82562EZ 10/100, one that is not supported by default! So let's see: I have to recompile the kernel, so why not use 4.1 then. Grabbed the kernel source, the suggested toolchain, and began compiling. Got the modules (no synoboot.ko though? O.o), did all the changes said on the wiki, pushed it to my boot pendrive, and rebooted.
Of course, stupidity over everything, forgot to check the toolchain's version, and grabbed the x64 one. Of course even after setting up the x86 config and using that, it did not work.
So right now I'm back to the drawing board, and trying to compile some code on this ancient box, what will probably take hours. Concurrently working on the 4.1 and 4.2 trees, so maybe I can give birth to one working kernel and module combo.
I will check back later on, providing some more info about my success/failure, but I have a few questions too:
- Is the mentioned NIC in any way supported? Ubuntu 12.10 has working network with linux-3.5.x kernel, so it should be there by default, and the only module it uses for networking is the Intel e100 one, yet with that enabled the old kernel did not work (I presume it was enabled as so far all the kernel sources I checked had the e100 enabled by default, except NightHawk's tree).
- Is there any way to install the whole system, with synoboot, etc., into one flash drive? Following the tutorial, it said I have to use another drive as the boot drive would be overwritten if it is selected for installation. I would rather not sacrifice two of my flash drives, and I do not wish to have a third, IDE drive in my server (want to add my second 1TB data drive, to create a RAID0 array for more storage, and get rid of the IDE drive).
EDIT1:
Tried compiling Andy's 4.1 and NightHawk's 4.2 kernels, with the x86 synoconfig and enabled all Intel drivers.
Results:
- 4.1 kernel, 4.1 toolchain, x86 config -- Dies on bzImage
Cause:
Error in arch/x86/kernel/sys_i386_32.c, function sys_SYNOmmap On line 51, implicit declaration of function 'sys_mmap2'
- 4.2 kernel, 4.2 toolchain, x86 config -- Dies on bzImage
Cause:
Error in kernel/built-in.o, function kernel_power_off (.text+0x1c48e) undefined reference to syno_schedule_power_on_prepare
If anyone has any idea how to fix it, please do share! No, it is not a problem with added modules, tried with a clean x86 defconfig, and same problem. BUT, with an x86_64 config (4.2 case), it skips that, and seemingly compiles properly. Still have to do the modules, but will report back how's it going.
EDIT2:
Okay, the x86-64 config (without the "64 bit kernel" flag) failed too.
- 4.2 kernel source, 4.2 toolchain, x86-64 config -- Dies on bzImage
It goes through the built-in.o problem, but I get a new one:
Cause:
Error in drivers/ata/sata_mv.o, function syno_sata_mv_gpio_write sata_mv.c (.text+0x3a10): multiple definition of syno_sata_mv_gpio_write drivers/ata/libata.o(.text+0xa80) first definied here Warning: size of symbol 'syno_sata_mv_gpio_write' changed from 2 in drivers/ata/libata.o to 143 in drivers/ata/sata_mv.o
XPEnology DS3612xs DSM 4.1 build 2668++ (more hardware)
in DSM 5.2 and earlier (Legacy)
Posted
It still doesn't have the extra drivers (does not boot on my hardware, while 2668++ does, I suppose it needs some extra parts like the ICH7 controller, etc.), so it is a no-go. But if someone could grab the kernel, and change the config to include those, we would be able to use it. Unfortunately the 2668++ config is not in the kernel (why enable /proc/config.gz, right?? That's it about GPL....), so we can't duplicate the changes easily, but maybe Andy can help us out a bit?
Of course I would like to have 4.2 on my device too, but I don't want to erase my nearly 300GB data on the disks just for updating, especially as my connection is extremely slow (20Mbit).