jagwaugh

And the wierd thing is, if you do sfdisk -M /dev/hdx it replies "hdX already is DOS" or words to that effect. I still think the problem is a latency issue with the md not being ready by the time the GUI tries to write to them.

" <?xml version="1.0"?> List of the virtual disks used in the package Logical networks used in the package Logical network used by this appliance. A virtual machine The kind of installed guest operating system Other_64 Linux_64 Virtual hardware requirements for a virtual machine Virtual Hardware Family 0 DEVDSM51 virtualbox-2.2 1 virtual CPU Number of virtual CPUs 1 virtual CPU 1 3 1 MegaBytes 2048 MB of memory Memory Size 2048 MB of memory 2 4 2048 0 ideController0 IDE Controller ideController0 3 PIIX3 5 1 ideController1 IDE Controller ideController1 4 PIIX3 5 0 sataController0 SATA Controller sataController0 5 AHCI 20 0 usb USB Controller usb 6 23 3 false sound Sound Card sound 7 ensoniq1371 35 0 disk1 Disk Image disk1 /disk/vmdisk1 8 5 17 1 disk2 Disk Image disk2 /disk/vmdisk2 9 5 17 2 disk3 Disk Image disk3 /disk/vmdisk3 10 5 17 3 disk4 Disk Image disk4 /disk/vmdisk4 11 5 17 true Ethernet adapter on 'Bridged' Bridged Ethernet adapter on 'Bridged' 12 E1000 10 Complete VirtualBox machine configuration in VirtualBox format "

tulco, Falls Du keine Daten auf die WD platten hast die Du behalten willst... geht probieren über studieren. Ich benutze Nanoboot 5.0.3.2, hab den .iso auf eine CD gebrannt & Boote von diesen. Gnoboot hat mehr modules "built in", aber für eine 0815 Mobo sollte Nanoboot reichen. Falls Nanoboot etwas an deiner Mobo nicht unterstutzt, probiere Gnoboot. Eigentlich spielt es keine Rolle ob Du Gnoboot oder Nanoboot nimmst (angenommen dass deine Hardware erkannt wird), beide sind lediglich eine art Bootloader der am Schluss die Synology OS startet. (Die echten Synology Bootloader ist in einen Flash Speicher abgelegt, was bei einen "normalen" PC fehlt, daher braucht man den xpenology). Andrew

DarkSnoop, Are you trying to login to the GUI or SSH? Does DSAssistant show your 54NL with the same name/ip as it was in your old install, or is it "Diskstation" & dhcp? Andrew

Chege, This is a red herring - What the release notes say is: 18.Storage Manager (for RS10613xs+, RS3413xs+, RS3614xs, RS3614RPxs, RS3614xs+ only) •You can now create volumes up to 200 TB large. •You can create RAID groups and RAID arrays. A RAID Group for Multiple Volumes or iSCSI LUNs (Block-Level) that use RAID 5 or RAID 6 may contain multiple RAID Arrays. •Synology Hybrid RAID is no longer supported As I read it SHR is supported EXCEPT FOR the models listed. With my 3612xs VM I can add disks to the existing SHR, and also create a new seperate volume with RAID. Looking at the release notes I notice that the "Storage Analyzer" is not there on my VM, was the storage analyzer dropped between 4977 and 4977 U1, or did something go wrong during my installation? Andrew

Hmn.... but the volume on my DSM51 _IS_ SHR!.... so it _is_ supported!. My 4 md devices are also built from /dev/sdX. I'm just going to try a test, I'll att another 4 disks to the VM and see if they are detected, and what kind of volume it creates. biab

synospace is apparently only for manipulating the volumes. The problem with trying to get the beta51 installed is that it doesn't create the volume (except as I documented above), so if, after the reboot, you have no md2, then you haven't got any volumes. I tried for a long time to get md2 (which is normally constructed from the sdX5 partitions) up. I think I must have tried every variant of mdadm -assemble -create -destroy -build or what have you, I also tried mounting the disks under a different vm and recovering the raid, It seems that if md2 isn't up, clean, and synced before you do the shutdown at the end of the upgrade/install of DSM51 then it never will be. I have installed DSM51 on various VMs using the procedure above, and it does come up with the volume working, so whatever it is, it isn't some module that is missing, or new check that synology has built in to make xpenology impossible, but plain and simple a question of timing. What I did notice when trying to resuscitate the md2 was that although md0 & md1 were built from sdX1 and sdX2, what the mdadm did find in the ondisk structures was hdx... not sure if this is a latencey issue with udev detection still starting or not, frankly I don't now enough about linux to say.

Heisst das das du vmware installiert hast an deinen Host, oder hast di ein von den fertigen vmdks gedownloadet, oder hast du im Virtualbox die disks als .vmdk erstellt?

Is your xpenology server bare metal? If yes, just install vboxheadless and phpvirtualbox see viewtopic.php?f=15&t=3497&hilit=vbox#p20949 Then you can create a VM with Ubuntu for compiling & use "Shared Folders" to mount something like /volume1/kerneltransfer to easily transfer stuff from the guest to the host and vice versa.

I tried that in a vm, but there wasn't enough space - I guess if you put the downloads & such somewhere on volume1 you might make it work.

so here is the wierd thing: I just added an IDE adapter & an IDE drive to a VM. when I restarted the machine it shows up as /dev/sdm. I then did sfdisk -M0 /dev/sdm Which sets it to Dos Style Partition. Then it shows up in the GUI as eSata, but unformatted, so I formatted it as ext4. Now it appears as satashare1-1 in filestation, and I can read and write to it. Is this somehow peculiar to virtualbox?

Does DSM support IDE drives at all? I haven't got an IDE disk other than the cdrom, which I boot my bare metal from, and adding an ide to a VM doesn't get recognised, but I'm not sure if this is due to the VM, the nanoboot, or just that DSM doesn't "do" IDE. Andrew (preparing to hide my head in shame)

Ok, the synospace shows no trace of a volume at all. Apparently that is all that synospace manupulates. Back to step 8, during the install, md0, md1, and md3 were present, BUT DID YOU WAIT FOR THEM TO REBUILD/SYNC - this takes a Loooong time, you can speed it up by entering: sysctl -w dev.raid.speed_limit_min=200000 sysctl -w dev.raid.speed_limit_max=5000000 but even then it will take something close to a day with 4Tb Disks (depending on cpu, ram and disk controller) I was working in a VM with only 4x 32GB "disks" and it still took something like 3 hours. The key, I think, is that you DO NOT shutdown/restart during the install UNTIL THE ARRAY IS COMPLETELY FINISHED BUILDING AND SYNCING. Every attempt I made with the vm failed until I waited for the array to be completely assembled and synced, once I did, it worked fine (& I have now done it a few times, so it probably wasn't just chance) Andrew

How are you transferring the files? SMB, rsync, scp? I hear a faint little bell in the back of my head... something about one of these not handling files larger than 2Gb, can't remember details, need more coffee...

I followed http://xpenology.com/wiki/en/building_xpenology the menuconfig, modules, and bzimage worked (with minor warnings), but being a noob myself, I got, and stayed, stumped by Step3 where you apparently need to modify synobios.ko: either I haven't understood what to do, or the values he mentions to modify are no longer the same. I am still faffling around with this step. I was building in a VM with the latest Ubuntu 64bit Server. Andrew

also, what does "/usr/syno/sbin/synospace --enum -a" tell you? I just discovered "synospace" over the weekend it seems to be synologys interface for blockdevices/arrays/volumes.

Did you check that the raid was built and synced (cat /proc/mdstat) at step 8 before continuing? As far as I understand, synology doesn't use mdadm.conf, but they store the equivalent information somewhere else & the install program apparently only writes this info to the configuration AFTER the array is built and synced. This is why mdadm --assemble --scan doesn't work: there is no mdadm.conf, and mdadm can't make sense of the on disk structure. What do "cat /proc/partitions" and "cat/proc/mdstat" tell you with the machine in its current state?

Hmn.... Vireschutz? Steht etwas in Windows Eventlog? Bei mir war der install innert 40 sec durch. Entferne deine .vdi & erzeuge eine neue? Vielleicht hat den .vdi irgenwelche übrigbleibsel im partition von vorigen Versuche?

So, jetzt grad hab ich schnell ein vm eingerichtet auf meinen win8.1. Other Linux 64 bit, boot vom NB_x64_5032_DSM_50-4493_Xpenology_nl.iso, 32Gb dynamic vdi, bridged network. Beim ersten boot hatte ich auch den"execution error" kurz vor der login prompt. Assistant hat es gefunden & problemlos installiert. d.h. es sollte eigentlich gehen bei dir. Hast du irgendwas geändert im vbox config?

Aha... Bei mir ist der Host meine Xpenology Box (phpvirtulbox), also headless. Hab nicht daran gedacht das deine Konfig anders ist. Also, jetzt in nanoboot menu, tab drucken & loglevel vom 0 auf 7 setzen (gibt mehr info im console während der boot). Konnte es sein das deinen Net problem enstanden ist grad weil alles auf der gleichen stack ablauft?

My bet is that a new 1Tb SATA disk will be about the price of an adapter, But yes, that would probably work.

Wenn du die VM startest, wird im "Display" am Virtualbox Host Gui blau. Doppelclick darauf & windows fragt ob du es offnen oder speichern willst. Speichern & dann Oeffnen. Ich benutze win8... der bordmittel rdp hab ich noch nicht zum laufen gebracht.

Wenn Du im Virtualbox, Display, Remote Display, enable Server enablt hast dann erscheint im Display der remote port der RDP sitzung wenn der machine lauft in Blau, doppelklick, open, jetzt oeffnet eine rdp sitzung zum Console der VM.

Der SSH session geht nür wenn die DSM schon mal eingerichtet war. Root pw ist gleich wie Admin. Beim frisch/neuinstallation war der root password eine wert der vom heutigen Datum abgeleitet war, aber die haben es offensichtlich geändert, bei mir funktioniert es nicht mehr. Wenns eine neuinstallation ist, probiere mit den Virtualboxrdp console die "Install" option im Boot menu (muss aber schnell sein bevor der menu schon startet). Falls es schon vorbei ist, RDP & Virtualbox Fenster nebeneinanderstellen, reset im virtualbox, fensterwechseln & Tab drücken.

Tust du vom Web GUI oder vom Assistant der upgrade starten? Assistant, oder? Mit DHCP oder Fix IP? Ich hab beim GUI installieren ein par mal solche früh abbruch gesehen, seither benutze ich immer der Assistant & es klappt immer (naja, bricht später ab manchmal) Dazu ändere ich die netwerk einstellung nie während ein install/upgrade. Ich hab auch den verdacht das der install manchmal abbricht wenn man im explorer ein altes GUI noch offen hat. Bei einen upgrade mach ich zuerst ein ssh session auf, dann per assistant der upgrade einleiten.