blue max
-
Posts
71 -
Joined
-
Last visited
-
Days Won
1
Posts posted by blue max
-
-
That's true sbv3000. Actually, even a genuine Synology box is going to be orphaned at some point too.
And I was running 5.2 until last week. It worked just fine, but I had that itch...
Thanks for posting. I feel better now!
-
With Jun now concentrating his efforts on the 918+ model, is this the end of updates for HP's Microservers?
I have two N54L's (stock) and a Gen8 (with Xeon 1265L v2) and both are running 6.2 U2 successfully. I understand I can add a nic card (ordered an HP NC360T to fit into one) and potentially upgrade to 6.2.1. Am also considering adding an INTEL X540-T2 if that works. Might as well get some additional benefits if I have to add a network card.
But my real question is this - Are the microservers now on borrowed time? I know they will probably continue to function as they currently are, but without security updates and fixes, they may become a liability over time.
Or is there some hope still? Just hoping the outlook is not so pessimistic.
-
-
SpoilerOn 11/20/2016 at 3:13 PM, Polanskiman said:
Download the loader, unzip it and put the image file (synoboot.img) directly on the desktop.
1 - If your flash drive is plugged, unplug it.
2 - Open terminal. Issue the following commands:
cd / cd ~/Desktop diskutil list
The last command should bring up the list of your drives. Below is what it shows on mine:
TlMBP:Desktop Tl$ cd / TlMBP:/ Tl$ cd ~/Desktop TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD UnencryptedNow plug your flash drive and issue the diskutil list command again:
TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD Unencrypted /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *31.0 GB disk2 1: DOS_FAT_32 41.1 MB disk2s1 2: DOS_FAT_32 49.4 MB disk2s2You can see my flash drive (31GB) now with the identifier disk2. Note that your flash drive identifier could be something else (disk3, disk4...) so don't just copy paste.
Now issue the following command:
sudo diskutil unmountDisk /dev/disk2
You might be asked for your password. Here is what I get:
TlMBP:Desktop Tl$ diskutil unmountDisk /dev/disk2 Unmount of all volumes on disk2 was successful
Then issue the following command. Same comment: BE SURE TO USE THE RIGHT IDENTIFIER. There is no turning back on this one. If you mistakenly use the identifier of some other disk, it will overwrite it with the image. SO BE VERY CAREFUL.
sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m
You should see this:
TlMBP:Desktop Tl$ sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m 50+0 records in 50+0 records out
You are done.
If you want to access the content of the drive you have to issue the following commands:
Verify again your flash drive identifier. YES AGAIN. You will need the disk partition identifier this time:
diskutil list
You should get this:TlMBP:Desktop Tl$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_CoreStorage 200.3 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 4: Apple_HFS Funky 298.8 GB disk0s4 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Yosemite *199.9 GB disk1 Logical Volume on disk0s2 CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD Unencrypted /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *31.0 GB disk2 1: EFI NO NAME 31.5 MB disk2s1 2: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 15.7 MB disk2s2 3: Bios Boot Partition 4.2 MB disk2s3Note the EFI NO NAME partition with the identifier disk2s1 of the flash drive. This is the one we want.
If you are on MAC OS El Capitan or earlier then issue the following:
mkdir /Volumes/efi
If you are on MAC OS Sierra then issue the following:mkdir /tmp/efi(Since Sierra, /Volumes is no longer world-writeable. One needs to be root to create folders in /Volumes)Followed by:
If you are on MAC OS El Capitan or earlier then issue the following:
sudo mount -t msdos /dev/disk2s1 /Volumes/efi
orIf you are on MAC OS Sierra then issue the following:sudo mount -t msdos /dev/disk2s1 /tmp/efiYour flash drive is now mounted. Edit what you need and eject when done. If you need to mount the flash drive again issue the last 2 commands. Always beware of the disk ID.
I'm very grateful for this and it has been so helpful. I do have an odd issue though. Sometimes I get as far as unmounting the usb stick and then issue the command to write the synoboot image. At this point occasionally it will work, but most of the time I get 'No such file or directory'. I'm not quite sure what makes it work any more. The file is definitely on the desktop, so it must be something to do with the directory I'm addressing. I know nothing of terminal commands, so would welcome any ideas please.
EDIT - I may have solved my issue myself. I issued the command 'clear' into the terminal window. Not sure if that was what made it work. Then I pasted the instructions into a plain text document. Then copied the instructions from that. But all working perfectly now. Left in case anyone else has the issue on a mac.
-
7 hours ago, luchuma said:
you made a mistake while creating usb loader
If that was addressed to me, can you elaborate please? I really don't know what I can have done wrong. I have done it a few times now, so don't think I've done anything other than the instructions.
-
System: HP microserver N54L.
I was on 6.1 and had to hit return on a keyboard to complete loading each time, so wanted to move to 6.2 in the hope that would solve the issue.
I installed 1.03b and synology assistant recognises it as migratable, but I can't connect to it! Very frustrating. It just times out. It has a 169 IP address, so is that a clue?
I don't get a chance to try to install 6.2. Any ideas anyone please?
-
15 minutes ago, Dfds said:
Just a thought but have you tried it without a keyboard attached? I only attach one to mine if I need to make any bios changes.
Yes, was what I thought too. But sadly not. Shows just how much I screwed it up !!!!!
-
24 minutes ago, Dfds said:
Removing all the other entries should mean that it doesn't require further input. Yes it's great that the N54 still works with Juns new loader as it's still a good little server.
Just tried and it didn't work. Actually, as I suspected. It wasn't that it made the wrong choice, just didn't make any choice! I don't have it connected up to a monitor and just hitting enter on the keyboard sends it on it's way. I used to have it sleep under 5.2 and only come on for an hour or so to backup my main server, so this is an expensive upgrade!
-
14 minutes ago, Dfds said:
Glad you're up & running again. To get around the issue you could edit the grub.cfg file on the USB stick & remove all but the 1st menuentry (the baremetal one). Also I don't know if you've seen but Jun has released a new loader for 6.2, it's still beta but it does work with the N54L as I've done a test install on my server.
Thank you so much. Though it sits on that one and just needs accepting, so wonder if that will help?
However, in for a penny etc and I may be adventurous and try 6.2 in a few days. Thanks for confirming, much appreciated. I had feared the old N54L days may have been numbered in terms of updating, so this is great news!
-
Update - managed to get DSM 6.1.7-15284 running on my N54L finally. Thanks to Dfds for his help.
It didn't go as smoothly as suggested, but with perseverance, I managed it. Couldn't tell you what worked eventually as it was very fraught.
However, the biggest oddity is that it won't boot up unless I attach a keyboard and hit enter. Seems it won't get past the asking which option to use to boot from. Any clues what I may be able to do about that?
-
Is 6.1.7 update 2 actually 6.2?
I thought it safe as it didn't appear to be 6.2, but can't access my nas again.
And this is the end of the line for the N54L? Very sad day.
-
So, I seemed to get it working, but initially it seemed to stick at the choices between a bare metal instal or the other two options in the bootloader (correct term?). Or bios. When I hit enter it continued. It forced reboot a couple of times when it seemed to be endlessly stuck and then it was complaining two drives were damaged but useable. But then I updated to 6.1.7 I think it was and finally update 2. Now I'm back to being unable to connect.
Have I broken it? At least until someone cracks 6.2 I guess. Why didn't I leave well alone!
I guess there's no way back now???
-
19 minutes ago, Dfds said:
@blue max The N54L will run 6.1 ok, I have one running 6.1.7 at present. Did you disable C1E support in the bios as it won't work unless you do.
Thank you for replying, but not sure what that is. I use that altered firmware that allows all sorts of other adjustments. Was it by 'the Bay'?
So, if I understand correctly, I need to boot up into the bios and make a change? I have never changed that, so assume it's on by default? Is there any way of checking through the Synology screen?
-
I know you guys must be sick of relative newbies, but I have a couple of HP N54L microservers running 5.2 famously. I suffered when I lost all my hard drives after a few days during one of my updates - and had updated my backup server too as it appeared to be OK. That will teach me! Anyway, I've stayed away for a while, but see that 6.1 seems well received now.
I've done all the steps and it doesn't seem to be recognised by Synology Assistant. Well, it can see it, but doesn't see it as migratable. Stick the old usb back in and all is good.
This is the same make and type of stick, just twice the capacity. USB 2.0. I tried using the mac instructions and on a pc with no difference.
I also tried with the previous version loader, with no difference.
Any suggestions please? I've been out of it for a while, so please make allowances.
Thank you all.
-
I will make this a tutorial on the site
.I would also appreciate this too Poechi.
Energy saving is one of the reasons for running a nas and this sounds like it could make quite a difference.
-
Try to save your changes as "default" settings.
Thank you for the idea. I'm a total pc virgin (mac user), so have very little clue about these things. You usually do the save and quit by pressing f10. How might you go about your suggestion please.
Thank you.
Graham
-
I've got two N54L's and both have the same Bios Mod.
One is successful and no problem. The other sticks during startup, but does not survive a restart.
I'm sure I have made the correct changes, but can anyone suggest what might be going wrong please?
To further explain - I do press f10 to save the changes. The hard drive in the optical bay is viewable and can be used. After a reboot, it is no longer seen.
Much appreciated.
-
To further this on. I tried putting volume 2 of my main nas into the backup nas, so there were two volume 2's. I'm now even more confused and the whole thing is an almighty mess!
Not lost any data, but things are out of control, with home shares on other disks and backups now being duplicated.
I had it all organised in a logical manner and it worked perfectly.
I think I will just have to start again from scratch with a clean install and initialised disks.
-
They're folder names. If you log into your box via Putty you can see them, and rename them using the "mv" command. Whether the system will play nice after you do that is anybody's guess so I'd backup before trying it.
I do appreciate your reply. I know it is pretty specific!
I'm a mac user, so can boot into windows seven on a bootcamp partition, but have only mastered the rudimentary stuff so far. I have used a programme recommended to activate the WOL via SSL. I think that is integrated with putty, but using commands is a step in the dark for me.
Sounds like I'm going to be stuck with it unless I gen up!
-
OK not a big issue by any means, but a real niggle and something I am hoping might be resolvable easily.
I have two volumes in my N54L - both double-disk raid 0. They are Volume 1 and Volume 2.
After trying to update to 5.1 and having a nightmare, I did a clean install and went back to 5.0
No data was lost and I'm back up and running 100% - Apart from Volume 1 is now Volume 2 and visa versa.
Not really an issue but some applications refer to the volume number and home shares appear on the relevant volume.
I tried to change it, but I can't see how as there is nowhere to edit it. In storage manager, under volume, Volume 1 shows it to be Disk Group 2. And again visa versa.
There seems no way to change it. Removing and reinstalling made no difference. It must be logged somewhere, but where?
Hoping it might be on one of the preference files, but maybe it's not as easy as that.
I can find no reference to it anywhere, so hoping for any thoughts please.
Future for HP microservers?
in DSM 6.x
Posted · Edited by blue max
Absolutely! I have no problem with that decision at all. And agree the reasons for it.
I very recently bought a gen8 microserver and if I'd come to that realisation before, I'd probably have gone another route. That's not to say it isn't a superb solution. Just it was always a no-brainer of a decision to get one. Lots of people used them and they are almost the 'default' installation. Now the hardware decision is much more difficult and varied. The end of an era to some extent.