jollmo
-
Posts
40 -
Joined
-
Last visited
Posts posted by jollmo
-
-
On the partition with the extra.lzma is a file grub_cksum.syno
May it be that this prevents altering grub.cfg after the install, because the checksum will be checked?
EDIT:
No, it's not the case.
I was able to clone my stick via dd to a compact flash card in a card reader, changed vid/pid int the grub.cfg and succeeded to boot from that via the USB port at the back of the server.
So the NAND problem must be something completely different.
On the Mac as well under Windows it behaves exactly like the old NAND, but maybe they changed something I'm not aware of...
When ordering it as replacement for the old NAND I checked the compatibility as best as I could, but you never know...
-
7 minutes ago, flyride said:
If VID/PID does not match, the stick cannot be used to boot. It's not an install, it's permanent.
The stick is updated on install and every major update of DSM.
Ok, but what about my other thoughts?
Does the install-process writes anything back on the install media (USB stick) what prevents it from being cloned without altering something on the new media?
Has anyone here been successful in cloning his stick and booting from the clone?
-
So the VID/PID is only for the first install, right?
Does the install writes any information back on the stick?
So that for every reboot it has to be THE stick you initially installed with?
That would could be the reason, why I can't reboot from the NAND. I think so, because I just cloned my stick to another one with dd and have the same problem.
Only the original stick is able to boot.
So maybe after dd we have to alter some other things on other places?
-
My Apacer USB NAND arrived today, and this is what I did:
I cloned my stick to the NAND using dd (did it on my Mac)
dikutil list output after dd:
/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 GB disk4
1: EFI NO NAME 15.7 MB disk4s1
2: Linux Filesystem 31.5 MB disk4s2
3: Bios Boot Partition 4.2 MB disk4s3
/dev/disk5 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *16.0 GB disk5
1: EFI NO NAME 15.7 MB disk5s1
2: Linux Filesystem 31.5 MB disk5s2
3: Bios Boot Partition 4.2 MB disk5s3
so everything looks promising so far. (disk4 is the NAND disk5 the USB-stick)
I mounted the EFI-partition (disk4s1) and altered the grub.cfg file in the grub folder to match the VID/PID of the NAND.
Everything else I left untouched.
I changed the new USBNAND with the old one, holding the EMC stuff and fired up the machine.
In the BIOS I changed boot priority to the new NAND and continued booting.
After the test sequence the Intro screen message "Screen will stop updating shortly..." arrived as expected, but the machine never appeared in my network.
As I didn't change anything than VID/PID I'm a bit out of clues right now...
If someone's got an idea about what I might have missed or messed up, he/she would make me very happy.
The machine still boots up from the stick...
So I thought maybe dd-ing ist not the right thing here and did everything again from the scratch, but now with the NAND, the whole OSFMount / Win32 Disk Imager thing... I was not altering the grub-file in whole, but taking the one that works with the USB-Stick and alter only VID/PID.
Again no boot further than "Screen will stop updating shortly..."
-
I found it:
So its only cosmetic...
-
One question to the chefs: The info center gives me under general: Intel core i3-4130 / 2,5 GHz / 2 cores.
Clock speed is reported right, CPU name and number of cores isn't...
I assume, the first is only of cosmetic nature (thinking it's a DS3615) and says nothing about the computing ability of the system and it's still capable of using all 4 cores for virtualisation?
Otherwise, if I really need it, I could upgrade to E3-1275 v2 any time or even E3-1290 v2 (without video of course)...
-
6.2.3-25426 Update 3 is up and running 😏
-
The module in the px is an Apacer managed USB NAND AP-UM001GK10CS-MSNRS, which is no longer available...
The replacement is AP-UM001GR13CS-2MST which I just ordered...
My plan is to keep the original NAND for the worst case and just attach the new one, after copying the existing boot stick (with altered VID/PID) to it.
Lets see...
In the time , waiting for the new module to arrive, I will solder an adapter from USB-A to the connector of the NAND for making things easier.
-
15 hours ago, flyride said:
So I implemented the script, after rebuilding my RAID due to removing and rearranging the HDDs and verified the install, all correct.
For the moment I'm unable to reboot, because DSM is still checking consistency, which will take another 24h I'm afraid, but tomorrow this time we will know, if I can upgrade to ver 3.
IP camera is fully working in the meantime
and I already migrated my photos (1,5TB)
Thank you all for your outstanding work!!!
A working machine after less than 1h, new life for my big baby, yeah!
The next project will be installing onto the onboard USB, but for that I have to do more reading...
-
5 hours ago, flyride said:
Thank you, great find; just looked over it, will try it later the day.
-
4 hours ago, GodZone said:
Did you overwrite the internal USB ? I haven't yet
No, not yet, have to read a lot before and buy some more usb-sticks to have something to revert everything just in case...
But my plan is that at the end of the week, my px12-450 is a Synology Device...
I plan to remove some of the 3TB HDDs for better cooling, build a raid 5 of four 3TB and a raid 5 of three 8TB and leave the rest of the slots free so the heat won't be a problem and I have enough spares for every raid...
-
Up and running
(after 1h work, incl. updates and reboots)
What a beast... Blazingly fast, didn't test much, the only encounter so far is, that it won't update from DSM 6.2.3-25426 to 6.2.3-25426 Update 3 because of a corrupt file?
Weird... Same error when trying to update manually... (just tried update 2, same behaviour)
I imported the configuration from my DS218+ and it looks very promising.
Trying to connect surveillance station with my IPcam doesn't work, as the password is incorrect, connecting over the web interface, the password is ok, have to check more...
Currently copying data, will go to bed now and keep reporting tomorrow...
P.S.: its easy to find the VID/PID of the internal USB, just go to System / info center / general / external devices and let the mouse hover over the internal USB, the VID/PID shows up after a second...
-
Thank you, I already downloaded your extra.lzma and will give it a try, already gathering everything for building the stick...
I keep you informed...
-
Hi, I just registered, because I find this discussion very interesting.
I recently got an Lenovo px12-450 (which is a rebranded Iomega px12-450), which is a 12 bay enclosure, and as Lenovo doesn't support this machine any longer, I thought about installing DSM on it, as I also own a DS218+, which would make working with DSM on the px12 very easy for me...
Do you think it's worth a try or should I stay with the Lenovo system, which still works.
The CPU is a 2,5 GHz E3-1265Lv2 (ivy bridge) and I added 16GB of RAM, which should be more than enough.
The DS36xx line has got 12 bays as well, so it should work with Jun's loader 1.03b right?.
Any hint / help would be very nice, thank you!
Installation on IOMega PX4-300R
in The Noob Lounge
Posted · Edited by jollmo
OMG! 😳
I had a closer look at my original bootstick and found out, that I swapped vid and pid numbers accidentally... That was the working one...
On the other media I tried, I always put the VID in the vid column and the PID in the pid column as shown in polanskiman's tutorial...
As I tried numerous times, I accidently again swapped numbers as well on the compact flash card and suddenly it worked...
So now I also swapped VID and PID on the NAND and guess what:
I have a clean machine
No more stick in the back 🤗
It boots from the internal Apacer NAND and everything runs smooth.
Took me the whole day to find that solution...
I need a couple of beers now
Cheers everybody 🍻