Nick
-
Posts
18 -
Joined
-
Last visited
Posts posted by Nick
-
-
23 hours ago, sbv3000 said:
With no volume/raid you are free to play.
I would try a 5.2 install, fire up a telnet session and dmesg the system to get some details of the sata module/drivers loaded, so we at least can cross check that the controllers are supported in 6, but also could identify the sata chipset
Then have a try of various combinations of the sataportmap, 24, 42, 222 (this last one might look weird but considering XPE/DSM5 is showing drives 3/4 unconnected, I wonder if 222 might match somehow in 6 (2 sata3 , 2 phantom, 2 sata2)
I was too lazy so I just tried different portmap settings. Tried 21, 221, 23 and 32. On the last try it worked so 23 was the winning number. Thank you so much for your help, really appreciate it!
-
25 minutes ago, sbv3000 said:
Yes of course you can go though the combinations of sataportmap, however if you have a raid it will be degraded because of the missing drives and you could lose data. Of course does not matter if you are building a new array etc.
At the moment I haven't even created a volume yet, just installed the software. So all good for testing then?
If so, is there any other combination than 23 and 32 I should try? So far I've only tried with 21, which resulted in two of the three drives showing (those connected to the Sata3 ports).
-
On 2017-10-28 at 8:28 PM, sbv3000 said:
He never came back so we dont know
I can only suggest trying the port testing as in my July 22 post and see if you can 'trace' the ports to determine the sataportmap you might need.
Also try the 6.1 loader (disconnect your raid drives) and use a test hdd as above to work out how the ports are enumerated, sataportmap might not be needed in 6.1
Thanks, I need to get ahold of a drive I'm not using first. On the other hand, coulnd't I just try different sataportmap settings until it shows up?
-
On 2017-07-18 at 10:41 AM, maxime said:
In bios all ports are configured as AHCI.
4 Drives are connected from sata0 to sata3 BUT sata0 and sata1 are ports of controller1 (SATA6Gb/s), sata2 and sata3 are ports of controller2 (SATA3Gb/s)
Drives are configured in RAID 5 and work perfectly on DSM 5.2
If I understood, I've to set this line on grub.cfg
append SataPortMap=22
Is it correct?
I am having the same problem with another H61 board. Did you manage to solve it with sbv3000 suggestions?
-
Just now, Dfds said:
Have a look at this thread, seems someone else had the same issues
Thanks! I will give it a read.
-
Just now, Dfds said:
Ok, what hardware are you using? was it a fresh install or did you migrate from another version of DSM?
It's a fresh install and I'm using an Asus H81I-Plus.
-
Just now, Dfds said:
Have you tried just leaving sataportmap as default i.e. 1
Well, I tried not changing the sataportmap with the 6.0 tutorial but would then end up at the "We've detected errors on the hard drives" message and had to try the Force install. Since this option doesn't exist in the 6.1 loader I decided to try changing sataportmap right off the bat.
-
Finally got this to work, thank you!!
Allthough I think I used "append SataPortMap" wrong. I have two SATA2 ports and two SATA3 ports where two drives are connected to the SATA3 and one connected to SATA2. I though that it would mean that I have two controllers and tried with append SataPortMap=21, but I just find two harddrives in DSM. Could it be that I should use append SataPortMap=3?
-
23 hours ago, Polanskiman said:
Have you solved your problem?
Not yet, I have cleaned the drives and am now doing another try with the new 6.1 tutorial. Fingers crossed.
Thanks for the concern!
-
20 hours ago, Polanskiman said:
Try using Synology Assistant instead.I tried that too but got the same problem that it doesn’t continue after the countdown. If I do another search it still finds the unit but with the same ”recoverable” status.
-
On 2017-10-06 at 11:53 AM, Polanskiman said:
I had a look at your motherboard's specs (http://www.balticdata.lv/Gfx/ProductFiles/P4661-E8425_H81I_PLUS.pdf) and by the looks of it that board seems pretty much compatible in every way. However there seems to be a lot of options in the usb and booting sections. You might want to look into the bios options. Also you might want to update the bios if there is any update available.
Not, having that motherboard in hands it is difficult to troubleshoot but something is certain, the usb is not booting and there is potentially many reasons why it is not booting:
1 - your bios is incorrectly configured;
2 - there might be a problem with the usb drive(s);
3 - the image is not properly burned on the usb drive;
4 - etc etc
If I was you I would start by resetting the bios and updating it. Then disable any superfluous options in the bios. Just keep the basic and make sure you are booting from the USB. Also try other usb ports and make sure to use a usb 2.0 port, not usb 3.0.
If nothing works then try with jun's loader v1.02b (the image made by Genesys). It's in the this tutorial
This is something you might also want to try: https://www.all4os.com/windows/disable-asus-motherboards-uefi-secure-boot.html
Can't believe I didn't think to check for a BIOS update. Thank you, that made the boot work!
Now onto to next problem, after I try the Force install (I get the "detected errors" message) the installation won't find the NAS no more. I have tried switching to the normal boot when it restarts and I have tried keeping it on Force install but still the same issue. The countdown goes down to 0 and I get an error message. If I go back to find.mysynology.com I can still connect to it and if I have it in Force install boot it says something about "Recreate", instead of "Install".
If I boot it normally I still get the "detected errors" message.
I'm thinking of trying the SataPortMap instead of Force install but I'm not sure if I have two or one Sata controller. I have three disks where two are connected to the Sata3 ports and one in one of the two Sata2 ports. I'm guessing I should go with SataPortMap21 then?
3 hours ago, alefados said:hi to everyone!thanks for the guide. all good with the loader but i have this problem could you please help me how to solve it?
i haven't any problem with dsm 5.2
Check Note 5 in the tutorial:
"If your encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, try the Force Install menu entry in the Grub Boot Menu."
-
Okey, so I tried installing Linux Mint and that booted just fine with the USB stick. So it must have something to do with the combination of the software and the motherboard/cpu. Forgive my lack of knowlegde but the hardware support comes from the extra.izma file, correct? Is there a list that I have missed of what hardware is supported?
-
Just tried with a new USB stick (16GB Kingston) and exact same resault with the black screen and jumping cursor before ending up att BIOS again..
Could it be a compatibility issue with the motherboard?
Any Hail Marys out there?
-
20 hours ago, IG-88 said:
did you try to selct the first uefi partion for boot (not the device)?
you can also try to search the forum for "uefi partition" and will find things like this
I have now tried everything, tried with all three partitions as priority nr1, tried different USB ports (both 2.0 and 3.0), and compared the BIOS settings with the working computer (both ASUS MB).
The last thing I can think of is trying a different USB flashdrive and see if it works better. Other then that, I'm stuck!
-
1 minute ago, IG-88 said:
so go to step2 and check the boot sequence in bios
do you see the usb flash drive in bios? can you make it 1st in sequence?
Yeah, I can actually see it as three devices in the boot priority list (guessing it’s because of the partitions). Two UEFI Corsair and one that just says Corsair. I also tried to disconnect all the HDDs and still same problem with the black screen. This is starting to get really annoying..
-
12 minutes ago, IG-88 said:
you should see a at least a message about the kernel booting, if not the booting from the usb stick does not work at all
try it in a difderent computer to verify its working, verfify the boot order in bios, use a different usb stick
I tried it on a different computer and the boot sequence worked there so atleast I can rule out the USB stick. I tried to boot an HDD with windows on the future NAS and that worked so I guess it has something todo with USB booting?
-
Thanks for the very detailed instructions but I'm having problems with the booting process where it just won't boot at all. The screen stays black for a couple of seconds with a cursor jumping between the top left corner and the middle of the screen, and then just continues to BIOS.
I'm using an Asus H81I-Plus MB with the onboard Realtek RTL8111G NIC.
I have tried redoing the USB-preperation process with both the original extra.lzma ramdisk and the one you provided in the OP, but no difference.
Any thoughts of what could be wrong?
Also, could my VIN and PID really be 090C and 1000? According to USBFlashinfo it is, but it seems odd to be the same as your example in the OP (it's an old 2GB Corsair Voyager btw).
EDIT: I'm doing a fresh instal btw.
Two controllers on my mainboard... how to upgrade?
in DSM 6.x
Posted
I suppose you are right, in the Storage Manager overview it says that slots 1,2 and 5 are occupied. On the board it would be 1,2 and 3 (out of a total number of 4 connectors)