hansel

I'm using a USB 3.0 flash drive on my N40L internal USB 2.0 port without issues.

If locally, you can use a IP sniffer app on your subnet to find the correct IP address. One other method is to logon to your router and find the address by listing all DHCP connected devices.

I don't think there is a DSM check on an existing/legit serialnumber. Is there? Anyway, I just used the same serial as my previous XPEnology, DSM 5.2 installation. And updated the whole lot.

Serial can be found in your DSM info center. Not sure where to find it when unable to login. MAC of your NAS-nic.

My fault. Jun's official v.1.01 loader. Just edited my post. Thanks.

Mine was succesfully updated to 9. Just booted it again without errors. To give more details about my setup, to help troubleshooting, here are my specifications: Bare metal installation, Jun's official v.1.01 loader Motherboard specs: type: ASUS AT5NM10T-I ATOM D525 CPU onboard, Intel NM10 Express Chipset, 2x SO-DIMM, DDR3 800, Realtek 8111E LAN

Same here. I powered off the system hours after starting the installation. GUI just wouldn't come up. After reboot the system does come back on. Info Center

Got this today.. Nothing found on the Synology page under "What's New" link. Weird.

I upgraded my HP Microserver N40L with three HDDs plus one SSD to DSM 6 without issues a few days ago. Nice! It was on Update 7 at the time. I just installed Update 8 from the GUI without any issues. I tailed the synosys.log while doing:

Being a leecher, just registered to say thanks too! N36L (AMD) with two 0.5TB HDD up to 6.0.2 update 7, all packages now updated too. Changed the PID, VID, SN en MAC as well as the AMD default="3" in grub.cfg on the USB after the dd to /dev/sdc. It didn't seem to function, as it still defaulted to 0, as where the AMD is 3 imho? Hooked up a keyboard and a monitor, manually selected the AMD boot option, booted, installed, miraculously, after the first reboot grub was updated on the USB? Anyway, got a working 6.0.2 update 7 now! Did you alter the default Sata mapping in grub file? If yes, to what?

Can you tell me what (with 2 SATA disks attached on your N54L) value you used for "SataPortMap=xx"? Did you set it via the Append command or directly in the .CFG file on the ISO?

@Vodka2014 Did you leave all your disks connected during upgrade? How is your raid configured? And what option did you choose in migration wizard?

two sata controllers, correct. From https://www.asus.com/Motherboards/AT5NM10I/specifications/ Storage - Southbridge 2 xSATA 3 Gb/s ports support AHCI mode I shutdown the system yesterday. Booted it yesterday by editing grub command appending the SataPortMap=10 value. Just now, I boot the system again without editing the grub commands. Doest that mean it makes use of the "normal" value stored in the image?

I had SataPortMap=1 set but that didn't work. SATA0 is being used by the one HD. Verstuurd met Tapatalk

Done. Installed as per Tutorial. Migrated from 5.2 to 6.0.2. And downloaded update 5 via DSM GUI. Nice! Now onto testing the upcoming days/weeks.

You mean this part? : Because I altered the SataPortMap value already to reflect my system; SataPortMap=1 Edit: I changed SataPortMap=1 to SataPortMap=10 with the append grub command. (Figuring SATA0 port has 1 drive, SATA1 port has 0) Now I see this message when connecting: This is the normal Migration message? Or is this install as in re-install? Edit: Clicking "Install" answered my question

Thank you. There was this BIOS option which simulates a removable drive to be Auto/FDD/HD etc. I forced it be HD and now it succesfully boots the loader. The system shows up in Synology Assistant as "Migratable". Now there is the following messages when connecting: In this system there are 2 SATA ports. The first one has 1 HD connected. Do I have to change "SataPortMap=" value? SATA ports are in AHCI mode.

But I can succesfully boot from the XPEnoboot 5.2 image on the same disk. Is that legacy? Bios boot menu order is not an issue. That setting has been there for ages. Maybe the motherboard doesn't support UEFI? Could that be? The motherboard is from Asus, type AT5NM10-I (https://www.asus.com/Motherboards/AT5NM10I/). It has the following specs: - Intel BGA559 Platform - Intel® NM10 chipset I always used this machine for testing XPEnology DSM updates. When all went well, the "production" machine was ready for upgrading. A HP Microserver N40L. I rather test this upgrade on the test server before moving on to the N40L.

I must be doing something wrong. All I see is a blinking cursor during boot. Nothing happens. I did the whole setup as described in this tutorial. I got no errors or other issues. Changed grub.cfg with the correct VID/PID/sn/MAC. I thought maybe the problem is with writing to the USB stick. I have tried with tools Win32DI/Rufus/UNetbootin and with 4 different USB flash drives. All with same result. My 4th flash drive was the original with 5.2 boot on it. After this one failed too I wrote the backed up image with Win32DI again (XPenoboot from Trantor I believe) and booted fine into 5.2. What is so different with this new bootloader that I just won't succeed?? My test system is a bare metal Atom D525 based board.

I guess this is the preferred (at least easy/lazy) way: 1. install https://xpenology.us/package-source/mar ... -installer 2. install https://xpenology.us/package-source/mar ... age/ipkgui Than I installed stunnel. Nice!

Just installed DSM 5.2 XPEnology on my HP Microserver N40L, bare metal. I need stunnel to make ssh tunnel connections from various application to usenet. I see stunnel being part of Optware http://ipkg.nslu2-linux.org/feeds/. Is ipkg still the preferable way to install packges which aren't ported to Synology? All guides that I saw are pretty old (pre DSM 5.0).

I apologize, English is not my native tongue. I did mean "really", I'm not trying to be sarcastic or something. I just didn't know Synoloy/Xpenology installed OS on all drives. I find that strange and surprising. I have one 2.5 inch sata drive (position 6, in optical drive bay) meant for system OS and one 3.5 inch sata drive (position 1) meant for data. When everything is up and runnig I'm adding a second identical 3.5 sata data disc for RAID 1 configuration. So when I install the third drive for RAID 1 configuration, partitions on the already installed 3.5 data disc get replaced or changed?

Does Synology install OS to every harddrive? Really? How come in DSM both my volumes show 'Hybrid RAID (SHR) (Without data protection).' If Synology makes two partitions on disk if there is only one disk available, data protection is available. Correct?

I installed 4.3 build 3810++ (repack v1.0) on my N40L with succes. I upgraded the standard 250GB with a WD 500GB 3.0Gbps disc and installed DSM succesfully. After that I installed one 1TB disc for data. My dmesg shows: [ 3.680064] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.686615] ata1.00: ATA-7: SAMSUNG HD103SI, 1AG01113, max UDMA7 [ 3.686662] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 3.693319] ata1.00: configured for UDMA/133 [ 3.745945] scsi 0:0:0:0: Direct-Access SAMSUNG HD103SI 1AG0 PQ: 0 ANSI: 5 ... [ 3.996071] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.996737] ata6.00: ATA-9: WDC WD5000LPVT-00FMCT0, 01.01A01, max UDMA/133 [ 3.996785] ata6.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 3.997460] ata6.00: configured for UDMA/133 [ 4.256631] scsi 5:0:0:0: Direct-Access WDC WD5000LPVT-00FMCT0 01.0 PQ: 0 ANSI: 5 This all makes sense. I have two volumes in DSM webadmin environment. Both show as Hybrid RAID (SHR) (Without data protection). But I don't understand this part of my dmesg: [ 5.936187] md: Waiting for all devices to be available before autodetect [ 5.936233] md: If you don't use raid, use raid=noautodetect [ 5.936680] md: Autodetecting RAID arrays. [ 5.987362] md: invalid raid superblock magic on sda5 [ 5.987408] md: sda5 does not have a valid v0.90 superblock, not importing! [ 6.026641] md: invalid raid superblock magic on sdf5 [ 6.026687] md: sdf5 does not have a valid v0.90 superblock, not importing! [ 6.026747] md: Scanned 6 and added 4 devices. [ 6.026786] md: autorun ... [ 6.026824] md: considering sda1 ... [ 6.026872] md: adding sda1 ... [ 6.026913] md: sda2 has different UUID to sda1 [ 6.026956] md: adding sdf1 ... [ 6.026997] md: sdf2 has different UUID to sda1 [ 6.027062] md: created md0 [ 6.027100] md: bind [ 6.027159] md: bind [ 6.027209] md: running: [ 6.027524] bio: create slab at 1 [ 6.027739] md/raid1:md0: active with 2 out of 12 mirrors [ 6.027822] md0: detected capacity change from 0 to 2549940224 [ 6.027957] md: considering sda2 ... [ 6.028020] md: adding sda2 ... [ 6.028063] md: adding sdf2 ... [ 6.028473] md: created md1 [ 6.028514] md: bind [ 6.028563] md: bind [ 6.028617] md: running: [ 6.029143] md/raid1:md1: active with 2 out of 12 mirrors [ 6.029226] md1: detected capacity change from 0 to 2147418112 [ 6.029363] md: ... autorun DONE. [ 6.050623] md1: unknown partition table [ 6.051047] RAMDISK: gzip image found at block 0 [ 6.284247] VFS: Mounted root (ext2 filesystem) on device 1:0. There are: unknown partitions, superblock and UUID messages that I don't like. Should I worry and try to fix before I add another 1TB for data redundancy?

Which file did you change to set these parameters? Not sure about the N54L, but my N40L does have an eSata port on the back. Why did you disable it?