quicksilver

Hello, Did you ever resolve this problem? Thanks Chris

crap... migration will not run... back to trying to get into the logs or backing everything up and installing a fresh system.

I completely agree. It's got to be the logs and they likely filled up while the rebuild was occurring. I wish that I had checked /root and /logs before attempting a reboot. At least I WAS logged in. Live and learn. I'm using Nanoboot with DSM 5. I think that it's the latest one before everything changed to XPEnoboot. I'm now extracting files that will be difficult to replace from the Array using an Ubuntu CD and mdadm. Currently it says 13 hours to go... if I have not figured out how to get logged back in to clear /logs by then I'll try a reinstall. That should clear out the logs. I suspect that the login problem is due to the system trying to log my login and failing so it's all a bit of a catch 22. If I could get to a single user instance of DSM it would be easy but I've tried adjusting the kernel line in grub but whatever I changed it to I only ever got a login prompt. Thanks again for the responses.

It's an interesting post but does not say what do do if I cannot get myself logged in. It does say: I think that I'll try a reinstall

Hi Diverge, Thanks for the response. Neither telnet nor ssh, nor the console will let me in using root, admin or any other username/password combination. All were working but now everything says access denied. I'm checking out the Synology post now.

I found another guide here that was somewhat helpful: http://phenomenology/forum/viewtopic.ph ... 262#p32262 I've now tried SystemRescueCD. It also allows me to get to /volume1 but not root. SystemRescueCD puts volume1 in /dev/dm-0 so: mkdir /v1_recovery mount /dev/dm-0 /v1_recovery or.. mount /dev/mapper/vg1000-lv /v1_recovery Provides access to the Synology volume in /v1_recovery Pretty cool actually an makes it really easy to pull the data out. I've also tried: As suggested in the other post but when I try to mount /dev/md0 I get: mount: /dev/md0: can't read superblock I would really love to repair root. trying to find out why it can not read the superblock now. Any/all suggestions welcome. I've also been considering an upgrade to XPEnoboot anyway. Is a reinstall safe with DSM in semi-broken state?

SystemRescueCD put this in /dev/dm-0 mkdir /v1_recovery mount /dev/dm-0 /v1_recovery or.. mount /dev/mapper/vg1000-lv /v1_recovery Provides access to the Synology volume in /v1_recovery Pretty cool actually an makes it really easy to pull the data out but I would really love to repair root. trying to find out why it can not read the superblock now. Any/all suggestions welcome.

Hmmm.. I'm getting an error during mount. mount: /dev/md0: can't read superblock I've been considering an upgrade to XPEnoboot anyway. Is a reinstall safe with DSM in semi-broken state? Thanks Chris

Hello, Interesting tip. Hopefully it will help me out too. While doing a rebuild /root got to 100% full. See here: viewtopic.php?f=2&t=5292 I've managed to get to volume1 but can not get to root. I've tried your suggestion but I do not seem to have /dev/md0. I'm using Ubuntu 14.04 Live CD and will try SystemRescueCD next. Hopefully it will allow me to mount /root. Chris

well... I've managed to get into the volumes by booting to a Ubuntu Live CD, opening a terminal and issuing the following commands: sudo -i apt-get install mdadm lvm2 mdadm –Asf && vgchange -ay or mdadm --assemble --scan Note: specify 'no configuration' for postfix, which seems to be a dependency for mdadm. I can now see my main volume so at the very least I can recover, but this does not get me into the root partition, which is what is full... Perhaps this will prove useful to anyone who needs to access their Synology data from another system but it get me any closer to recovering... Perhaps someone here will know how to get into root.

Hello, Something has happened to by NanoBoot diskstation while replacing a bad disk. I'm getting a message saying: Partition layout is not Diskstation style and sed: couldn't flush /tmpRoot/etc/....: No space left on device ... I get a login prompt and the webgui seems to be there but it will not accept my login. Does anyone here know how to boot DSM/NanoBoot into single user mode so that I can check /root. Thanks

@sancome... Dude.... wow. Great news! I had almost given up hope. Thanks to you and the team for all the hard work and dedication!

Tried the updgade yesterday... everything went perfectly. Bluetooth even worked first time. Long live Nanoboot!

I would love to know this too. It would be nice to have bluetooth audio working with nanoboot. I've not tested yet but see nothing about bluetooth USB support in this thread.

I've got a Synology 1511+ with all the current updates, an N40L with update 2 (but not 4482), an N54L (without update 2 or 4482) and some time to help test and/or provide info from an actual Synology if that will help.

Dadudeondacouch, Where did you add this script and where did you find it? I would like to hide the boot USB / SD card (in my case) too. I've done a quick search in the forums for boot unmount USB but did not see anything. Perhaps this is documented in one of the PC setup guides? Thanks Quick

Setting eth0_wol_options="g" seems to force it to appear to be on but I still cannot use the DSM gui to change it and when off it will not wake from sleep using a magic packet sent from somewhere else on the network. Even after a reboot the change in configuration does not see m to take. Thanks for suggesting Chris

Just in case anyone out there is interested... I've just managed to successfully upgrade an N40L from the Nighthawk build (DSM 4.2 3202) to the Trantor 1.2 build (DSM 4.2 3211). I guess that I did this because I wanted all my DiskStations to be at the same revision and I guess because I was curious if it would work and I just happened to have a spare machine to test it on. I DO NOT recommend that you try this yourself without first backing up your data and take absolutely no responsibility for it going wrong . Software RAID can be extremely difficult to recover if broken. Backup your data before trying. I started with a fresh machine and fresh drives (fully zeroed) that had TheBay BIOS installed (see previous post) and had been built as per the guide on page 21 of the '[sOLVED] HP Proliant N40L MicroServer native support' thread (because all my other DiskStations were built this way). I did not install iPKG or adjust the eSATA port configuration or install teh updated USB support libraries (because I wanted to see if the Trantor build could solve this problem itself) but did install several packages (AudioStation, DownloadStation, etc) and pre-loaded a couple terabytes of data onto the box (mostly media). After I had a fully configured DSM 4.2 3202 box I grit my teeth and tried the upgrade. 1) I created a new SD card using 'synoboot-trantor-4.2-3211-v1.2.img' and set the grub config file to match the test DiskStation so that the MAC address would be the same on the new machine. 2) I powered down the test DiskStation and rebooted using the new SD card 3) Once booted I used Synology Assistant to locate the DiskStation and opened up the install page. Note that the 'Status' should say 'Migratable'. 4) I selected Migration on the 'Installation Type' screen and then 'Install from my computer' using the 'XPEnology_trantor_v1.2_DSM_DS3612xs_3211.pat' file. 5) once started the first part of the upgrade went smoothly and the DiskStation rebooted. 6) the initial reboot took quite a bit longer than usual but I had a screen attached and at no point did the process stop in any way. 7) After several minutes I had a system running Trantor 1.2. All the initial packages were there and all the media that I had copied onto the test box was there. USB works perfectly... My keyboard and test Bluetooth adapter both function perfectly. So... an upgrade does work... I take absolutely no responsibility for lost data or a broken Microserver and STRONGLY urge you to backup your system before trying this... but that said... it does seem to work... Next I am going to use this box to backup my other 3202 boxes and attempt the upgrades on them... after this test however... I'm feeling pretty optimistic. Now back to trig to get WOL working using the suggestions posted earlier. Chris

Just in case anyone else is wondering or worried... I have successfully installed v1.2 on an N36L, N40L and and N54L with 4 and 5 x 1.5GB, 2GB and 4GB drves (various combinations) and 2GB -> 8GB RAM and various USB Bluetooth adapters. With the exception of WOL (which I think that I can solve using info from some of the previous posts) and auto spindown and NFS (which I've not yet tested but did managed to fix on the the Nighthawk build)... Everything seems to be working very well. 1) Install 'The Bay' firmware on the Microserver. See here - http://www.avforums.com/forums/networki ... pport.html . It allows you to create a bootable USB stick that reflashes BIOS for you. 2) Adjust the BIOS settings to set all drive ports to AHCI 3) Create the USB or SD card image of - 'synoboot-trantor-4.2-3211-v1.2.img'... I use an SD card because it makes it easy to write protect the boot image. from this forum 4) Adjust the grub config file as per the previous few posts in this thread (yes... you should read them) so that you get the correct MAC address when the system boots. 5) Reboot (with the SD card inserred into the internal USB port and with the MicroServer attached to your network) 6) Use Synology Assistant to locate the new DiskStation 7) Use Synology Assistant to install 'XPEnology_trantor_v1.2_DSM_DS3612xs_3211.pat' I suggest that, for the extra couple dollars it will cost, use a decent SD card reader and SD card. I use Transcend SD card readers (RDF5) and descent SDHC Class 10 cards from SanDisk but this is likely overkill. I've done this so many times now I've got the whole process down to minutes and each time it's resulted in a perfect NAS box. It really is very easy. All Hail Trantor! Chris

I wondered why WOL from control panel was not working. Are you saying that I should make sure that it IS there? Testing now. Mac and serial number is working fine now but no joy at all with WOL. DSMs control panel shows that I have 1 LAN adapter and it seems to work but when I try to activate WOL DSM tells me that it 'Failed to set up Wake on LAN". The line currently reads: kernel /zImage root=/dev/md0 ihd_num=0 netif_num=1 syno_hw_version=DS3612xs mac1=3C4A9279C468 sn=B7J4N07343

I wondered why WOL from control panel was not working. Are you saying that I should make sure that it IS there. Testing now. Thanks!

Thanks for that too. I did have the default serial number in there but chopped it out while debugging. I've recently been testing the notify via Instant Message (Skype) function in DSM and have seen a few messages that definitely did not come from my machines. My best guess is that the relay service is using the serial number of the box to relay specifically to me and someone else is using the same (default) serial number. So it may in deed matter.

Thanks for the help! I'll give that a try now. Chris

Hello, I am using the Trantor 1.2 build with an HP MicroServer N34L. I've tried modifying the grub file that comes with the 1.2 build as per the instructions here but when I do Synology Assistant seems to think that I have a RackStation and the web interface no longer works (and the box shows as migratable) Removing the comment in front of hw_model seems to bring it back to life but DSM does not contain the MAC address that I have set. This is what I have: #serial --unit=0 --speed=115200 #terminal serial default 0 timeout 3 fallback 0 #title DSM 4.2-3211++ Repack v1.2 title SYNOLOGY root (hd0,0) #vender /vender show #hw_model kernel /zImage root=/dev/md0 ihd_num=0 netif_num=1 syno_hw_version=RS3612xs mac1=3C4A9277BA7C initrd /rd.gz Note that I have changed netif_num to 1 (from 4); commented out hw_model and vender /vender show; and change the title. Can anyone see where I might have blown it? Does anyone know why the mac address grub changes on v1.2 changes by box to a RackStation? Thanks for the help. Chris

I think all drivers are included but you maybe need to tweak synoinfo.cfg (esata, usb, internalport) to reflect your hardware. Has anyone managed to test this on an HP Microserver (N40L and / or N54L)? Thanks Chris