blue max

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About blue max

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, was what I thought too. But sadly not. Shows just how much I screwed it up !!!!!
  2. 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!
  3. 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!
  4. 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?
  5. 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.
  6. 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???
  7. 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?
  8. 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.
  9. blue max

    cpufreq and powernow-k8 modules

    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.
  10. blue max

    N54L Bios Mod not sticking - assistance appreciated.

    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
  11. 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.
  12. blue max

    Storage annoyance for OCD user

    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.
  13. blue max

    Storage annoyance for OCD user

    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!
  14. blue max

    Storage annoyance for OCD user

    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.