billat29
-
Posts
351 -
Joined
-
Last visited
-
Days Won
10
Posts posted by billat29
-
-
I also found something that suggested that you might be able to use ethtool to force 1Gb.
-
I have no idea what I am talking about (and I don't know how the modes are advertised) but I see that it thinks that the switch only does 100baseT
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes-
1
-
-
@XDOM Once the loader has booted the keyboard has no function.
The next step is to locate your box on the LAN using either find.synology.com or Synology Assistant from a PC
Which loader and DSM version do you want?
See here:
-
2 hours ago, Ghosthawk said:
i have updated the bios but still cannot select between cms or uefi
Looking at the ASUS website, this is an old board that appears to be BIOS only, so disregard the comment about selecting csm / legacy.
Do you get the loader messages on the monitor when you boot?
-
@personanyYour question was answered by @flyride immediately after your post.
-
If I had a G7 lying around and wanted somewhere for plain storage or very light duties, I might use it rather than throwing it away.
Mine sits in the corner and powers up to receive backups from my main device before shutting down again.
At this point, I wouldn't pay much money for one and you certainly don't need 8GB.
-
1
-
-
I made the same mistake (wrong command parameters) not deleting /.xpenoboot when I did my upgrade to 6.2.3
I confessed my error in the upgrade thread.
@hansel made a very good description of what happens when you fail to do so. If you are getting those symptoms, then you have this problem.
In my case I ssh'd in and just ran the rm command and rebooted. My system is perfectly functional now.
-
1
-
-
I read through your topic (so that others don't have to).
I understand that you used to have 6.1 installed and that atlas said your nic was not supported under 6.2.
And then you started an upgrade.
If this is correct, then you need to do this
-
1
-
-
Hurray! You can safely accept the upgrade to 6.2.3 update 2 and then you are done!!!!
-
1
-
-
Classic symptom. You have successfully run the upgrade, so don't do it again. However you need to do ssh in and delete the /.xpenoboot directory.
You need to move quickly after booting before all the services stop.
-
1
-
-
Off the top of my head - I can't answer your questions directly or rather in detail. But I can say with confidence that there is a thread that discusses the appearance of the bootloader in ESXi and what to do about it (same will be true for Workstation) and also
onemany where the enumeration of the attached drives is discussed.Search and you will find.
-
I suggest doing 1. and writing down all the steps and recording what happens - or doesn't happen. As @IG-88 says, if it gets stuck in the middle of the installation, then leave it for a while. I also now remember one of my steps to upgrade to 6.2 required a couple of hard boots and a wait to make sure the disk light had stopped.
If it all stops, post what you did and what messages you did (or didn't) get.
-
1
-
-
Thanks @IG-88. I have been looking for that tutorial for use here and failing miserably.
I am glad you were confused about the 1.02b loader too.
-
HP Gen7 is legacy boot only
-
1
-
-
OK. Got that. Boot / recovery loop says to me "wrong loader". But at this point, I can't see whats wrong. I'll have to have a think about it. I'll be happy if one of the gurus stops by in the meantime
-
1
-
-
If you haven't had the recover option before just the migration option, I would attempt recovery. I would not expect it to try to install a version of DSM at this point.
-
Did you not say that the last time it said "migrate"? In which case I would go ahead
-
IF the drives in this box originally came from the old 5.2 box then you need to do this before any further investigation:
-
1
-
-
Well, that's all very interesting.
Back to first principles.
1. Check the physical network. All switches up and with lights where you expect them? Is there anything to suggest that you had a power outage overnight?
2. Connect a monitor to each box in turn. Do you get all the loader boot messages when you reboot it?
3. Boot each box in turn with your ubuntu USB. Ping it from your PC. Obtain the hardware address of its network card. Plug the loader USB in as well and list its vid and pid.
4. Mount the loader USB under your OS of choice and examine the config file to make sure that it matches.
5. Do the same for the other machine and loader.
I predict that one of the loaders has the wrong MAC address set. I suspect the other may have tried to auto update itself.
-
Battery on the motherboard is dead. It will be a standard coin style battery. Straightforward to replace. Open it up and have a look.
-
Let me summarise where I think we are.
You have an i7 based machine that is now on 6.2 and it works.
What you are now trying to do is to get a system up on the old ASUS with new disks and that is the machine that you are having problems with.
I looked at the product page for the ASUS and it clearly says that it is a UEFI machine. The loader that you have created for 6.2 will not boot unless you can put the ASUS into legacy BIOS mode.
On that basis, what I would do now is to put the 5.2 USB stick aside and create a new stick with the 1.02b DS3615xs loader, following the tutorial. I would clearly mark the new stick to make sure that there is no possibility of putting it in the i7 machine by mistake and then download and install DSM 6.1.7.
If it doesn't boot this stick, check and check again that you have vid and pid of the new stick set correctly along with the mac address of the ASUS.
If the installation process gets stuck again, take a screenshot and post that up here with a description of what you were doing at the time.
-
No budget is fine. We just need to spend a little time looking at the problem. There are a number of different scenarios that could be causing your problem.
But you need to supply more information.
But first a random suggestion. What mode is your new box booting in? It needs to boot in csm/legacy mode not UEFI mode for the "6.2" loader to boot. Look at that first.
If it only boots in UEFI mode then you need the 1.02b loader and DSM 6.1.7
If that doesn't get you anywhere then you need to come back with
1. Version of the bootloader you are using - I am looking for both the version (1.02b / 1.03b) and the machine type (DS3615xs etc)
2. The hardware you are using. I am looking for CPU model and chipset - but motherboard model will do.
3. What does "work" mean when you put your USB into another machine. Does synology assistant or find.synology.com locate it?
4. Same for when you put your 5.2 loader into the target machine.
-
I see that you had an accidental upgrade from 5.2 in 2016 and that I presume you recovered from.
It doesn't look like you are creating the USB properly.
So here is some reading 😬
Depending on your hardware, your target version of DSM would be 6.1.7 with the 1.02b loader or 6.2.3 with the 1.03b loader.
These options are outlined here:
You can look through the updates reporting section - the one for 6.2.3 is here:
to see if anyone has reported success or failure in updating your hardware. There is also a corresponding one for 6.1.7.
Having selected your target release, then the general method for creating a USB and installing DSM is here:
although it is for 6.1. it is the same method for 6.2.3 but with the different loader.
If you get stuck - or find it all just too much information, post details of your hardware and someone should be able to have a look at where you've got to and what you can do.
-
Perfect.😀
HP Microserver G7 (N36L) will not use 1Gb/s
in AMD
Posted