hansel
-
Posts
56 -
Joined
-
Last visited
-
Days Won
1
Posts posted by hansel
-
-
18 hours ago, Peter Suh said:
Did you succeed in installing DSM on your N40L through the above TCRP FRIEND loader?
I think so. I downloaded most recent version from github. I noticed the 4th bootoption called "withfriend". After that I started DSM, boot option 1. I'm running it headless now. Can I check things remote for you?
-
1
-
-
After doiing another update, postupdate (where it found the update 7.1.1.-6) and reboot into DSM, the hdd led finally went blinking continiously. It was doing something!
After a few minutes I could login into DSM webpage and see the 7.1.1 update 6.
-
I've got this message after building a new TCRP (tinycore-redpill.v0.9.4.9) loader. As far as I know my N40L doesn't support EFI.
Just before (or after?) this page, by escaping the boot sequens, I did a fdisk -l command and saw all four disks.
I could reach the webpage http:<ipaddress>:7681 just before it said "Connection Closed"
There is no way connecting with TCRP remotely by ssh.
[Update]
I rebuild TCRP again, setting user_config settings first and building the loader after that (instead of the other way around).
The result being
On the vga connected screen there is a message "Nothing has been loaded!".
-
Anyone here who has updated to DSM 6.2.4 succesfully on their HP Microserver series?
-
Is it safe to update the system to 6.2.3-25426 Update 3? All successful updates on the HP microserver machines seem to have a Intel NIC installed. I don't.
-
@IG-88I guess i'm not a up-to-date technical person (anymore). What's the drawback of using AHCI compared to SATA? Is there any?
-
Downloaded the TheBay BIOS and downgraded (from 2013 back to 2011) the BIOS. Now I see the SATA 4/5 IDE disable/enable option in Chipset category. Lost a whole bunch of other settings though!
Disabled the SATA IDE option and booted into DSM 6.2.3 Update 2 with all drive attached; 3 HDD + 1 SSD with SSD attached to motherboard SATA. SSD recognized and needed quick repair. Fixed! Thank you.
-
1
-
-
@bearcat I don't see that setting in my BIOS.
My hacked 041 BIOS had date 1/10/2013. I just updated the BIOS with the 041 2013 hacked BIOS as per https://www.nathanielperez.us/blog/hp-proliant-n40l-bios-modification-guide but that didn't change a thing. No SATA 4/5 setting. How come?
-
Hacked BIOS is installed for years. SSD always worked in DSM. Since update it's gone. See attached for the setting. I didn't touch this.
-
Besides the 3 harddisk drives, my setup also has a SSD drive. It is attached to the motherboard's SATA socket, not part of the 4 bays. Since the update this drive is not seen by the DSM system. In the BIOS I have disabled the C1/C1E option. This shouldn't affect the onboard SATA, right? I have yet to attach a display to have a look at the pre-boot to see if the BIOS does recognise the drive. The drive itself is ok, I had it attached to a SATA cradle on my laptop.
-
On 11/4/2020 at 12:07 AM, eclairs48@gmail.com said:
Have you been able to upload any new data after the upgrade? I think I am in the same boat like you, so just checking. Thank you.
I have uploaded a whole bunch of photographs from my Android smartphone without a problem. Have you been successful uploading data in the meantime?
-
@eclairs48@gmail.com No, I didn't. I shut down the system after it was running all day. (I let it run its data scrubbing since that hasn't been running for a long time). I'm not at home for a few days. I'll test next week.
-
@billat29 Really! I did check if that hidden directory existed. I have used unix systems in the past for my work. My number one listing command at the time was "ls -ltrh", don't ask me why. I thought the 'h' was for "hidden"! 😄😴
Thank you! After remove/reboot I have got a working HP N40L Microserver with up to date DSM. Nice!
-
I've taken the number 1 approach.
Quote1. use the 1.03b again and make a migration, wait at least 1h and then hard reboot if needed the system may come up than as 6.2.3
(doing a migration to a new dsm vesion and change 3615->3617 should not be a problem)
After a new installation with loader 1.03b/DS3617xs on a test disc, I swapped the test disc with the real data drives (3x1GB, SHR by the way). After the system booted, I got the Migrate button. Clicked it and it didn't take too long for the migration process to run. 5-10 minutes or so. See screenshots below. Two automatic reboots later and I got the login screen. I saw the DiskStation in the Syno Assistant app also.
Now I can login with my old account name but the system is not stable. When opening Control Panel I random get the message:
and the Control Panel closes. Sometimes followed by a not available webgui. Or, when webgui keeps working, I open DSM Update I get no connection:
Going to the network setting, there is no machine name (whilst it was broadcasted in the Syno Assistant earlier) and gateway:
The Resource Monitor is funky at 0% CPU/RAM but halfway the scale:
I wanted to check if my files are still there but there is no File Station app. When I go to package center I see it is installed. There are no icons loaded in the package center. Weird things happen. 😟
Any ideas? What if I choose "Reinstallation" instead of "Migration" at the Migration - Installation Type screen? I don't care too much about the user accounts and shares. My setup is not that complicated. I would be fine with resetting this. Reinstallation keeps your data right? Is that something I might give a try before trying @IG-88's second option? Second option is an option because I have one sata bay available.
-
But won't I need the webgui in order to enable ssh if my config is lost?
-
Thank you @IG-88.
You're right. I made an error on the DSM versions there. Screenshot tells the true story. My text is faulty. Should be DSM 6.0.2-8451. I also found that I wasn't originally using the V1.02b loader but the V1.01. That one matches with 6.0.2-8451. Sorry 'bout that. So much versions going on....
Anyway. I will have more patience and once more create a usb flash drive with V1.03b / 6.2.3-25426 / DS3617xs and do a migration. I will report back.
-
@flyride No, I didn't think about that! I haven't been active on this forum for quite some time. Must have missed that.
I've looked in the BIOS settings like crazy. There isn't anything to be found concerning boot legacy/UEFI settings. Are you sure this is available for the HP Microserver N40L?
-
But recovery doesn't do anything. It just reboots over and over again saying, in the end, it needs recovery. It doesn't recover at all.
-
@billat29 But that migration didn't go successful. It never showed up in Syno Assistant.
-
Ok, another reboot and swapping drives and I'm in the original setting again. June's 1.02/DS3615xs loader with DSM 6.0.2-25426.
Status is now "Recoverable"
Syno Assistant
DSM web gui
I've seen this before. When I try to recover, it suggests it will start recovering but this only last for 1-2 second before it reboots to tell me that the system is in recovery mode. Over and over again.
-
Ok, it's officially a mess.
This is what I did. I swapped the dummy drive with the real data drives. With the same Flash drive in the system I booted my N40L again. After a minute I saw my DiskStation with status "Migration" or a like. Clicked the migration without loss of data in the web gui and selected the 6.2.3-25426 PAT file from my desktop. And go!
Never saw my N40L again. I didn't see it in the Synology Assistant application.
Then it occurred to me that I was changing DSM version, bootloader (1.02b to 1.03b) and machine model (3615xs to 3617xs) at the same time. A fresh install worked based on the 1.03b/3617xs but these data drives have history. Might this be the problem?
Since then I have:
- swapped the dummy drive back in and booted without issues.
- placed the old 6.0.2 usb flash drive back in together with the data drives. No sight of the machine in Syno Assistant.
- made a new flash drive based on 1.03b/DS3615xs without luck.
What should/can I do now?!
-
Update 2 installed. No problem.
-
2
-
-
I finally took the time to test it out.
I removed all discs and added one empty HDD.
Created a new flash drive with loader based on DS3617xs.
Disabled the C1 / C1E option in BIOS.
Rebooted again to find the DSM onm y LAN with the Syno Assistant desktop tool. It installed the newest PAT file perfectly.
Next step is to upgrade the system with DSM disks added.
-
I revived my old N40L Microserver again. Put in the power cord and booted her up. Running well. It's running with the below version, June's loader. I'm not sure what version loader.
I wanted to try and update the DSM with a more recent version but not sure where to go first.
The microserver is stock. It does not contain a extra NIC. I think I have changed BIOS years ago. To add extra SATA port capabilities?
Anyway, what are my options? There is a serious amount of family photographs on it. I got those backed up on a external drive but I rather not do a total reinstall.
- Can I update to new DSM 6.2.3?
- 6.2.1 needed an extra Intel NIC to function. At some point there was a seperate Broadcom driver available. Does 6.2.3 still need the extra Intel NIC or is it possible to work with the broadcom driver?
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
Not sure I understand; with staticboot (or "direct boot") in de user_config.json enabled, what exactly is the benefit of that?
What should I do when an update of DSM (or TCRP?) comes out?