Knarf
-
Posts
24 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Knarf
-
-
12 minutes ago, IG-88 said:
did you you waited the until the repair was complete (there is a percent counter) before a reboot or shutdown?
in storage manager under disks section is a tab "log", did you check if anything useful is in there?
Yes, I waited until it was complete and I received a nice big green check mark in my disk health widget. It was after I then upgraded to package 3 that I received the new bad news. Unfortunately I would not know if there was anything useful in the log or not. I'll have a look and see.
log is below, not sure if it tells anything useful.
Thanks for your help.
-
14 minutes ago, IG-88 said:
that rings a bell, i remember problems with microservers and bios reset but it was usually on shutting down and you seemed to loose settings on reboot
on hp systems (desktop have this option too) you can save your settings as default, that way you don't loose it if it goes to default
problems with system partitions like you had might come up when one or more disks are not present when booting up, next time when disks all online again you need to repair in storage manager, basically you re-syncing the dropped out disk to your raid
the onboard nic (afair broadcom) should work with the additional extra.lzma for 6.1 but you can use a diffrent in pcie if you want or have to
if you can use 6.1 without extra.lzma then 6.2.(0) should work too, but 6.2.1 and above will not as there are changed kernel settings and most of the drivers in juns extra.lzma that comes with the loader 1.03b will not work, only the drivers directraly provided by dsm will work, that will be fixed with the new extra.lzma i'm still working on
safest way is still 6.1 imho
That post about the bios issue would have saved me days as well. Better late than never. I repaired the Disk in storage manager but on the next boot it is now saying Drive health status is degraded and I'm getting notifications that disk 4 is trying to re-identify. Any ideas about repair short of a new HDD¿
If you think about let me know when you have the new extra.lzma ready. I'll hold off updating any further until then.
Thanks,
Frank
-
The update 3 is all OK for your system, as can be seen right here (among other places).
Notice that he did not use any custom extra.lzma.
Updated to Update 3 with no issues.
Thanks.
-
15 minutes ago, bearcat said:
How does it look from the "Storage Manager"?
Anything like this?
According to Synology there should be a link offering you to "Repair the system partition" do you see that ?
if you don't get the link (or it don't help) you might want to do a manually fsck
You may want to do some reading here for basic info and here and here for more Syno related info.
Bearcat,
I went to that page and it was just as he described-all was well until the HDD/SSD section. Showed one HDD with a partition problem. I hit repair and all is well.
Thanks for the links.
-
4 minutes ago, bearcat said:
First thing first: congrats
I know how frustrating these things can be, and sometimes you just need some time away from it, to be able to "reboot the brain".
Now, you have it running, at least a good starting point.
The update 3 is all OK for your system, as can be seen right here (among other places).
Notice that he did not use any custom extra.lzma.
I have scratched my head in regards to your BIOS resets,
as I recall some problems from long ago, where one common thing, was the use of power-savings and some old bootloaders.
If you have a look here or here you will see some old stuff in regards to that.
One "easy fix" seems to be password protecting the BIOS after setting it the way you want it.
btw: What BIOS did you finally use to flash your system?
In regards to your System Partition Failed, that is more problematic..
How does it look from the "Storage Manager"?
Anything like this?
According to Synology there should be a link offering you to "Repair the system partition" do you see that ?
if you don't get the link (or it don't help) you might want to do a manually fsck
You may want to do some reading here for basic info and here and here for more Syno related info.
Bearcat,
I used the MOD from this website since it was specifically addressing my HP N40L. https://www.nathanielperez.us/blog/hp-proliant-n40l-bios-modification-guide
I'll look at your other links and get back.
Thanks
-
I have finally succeeded in updating to DSM 6.1.7-15284.
I want to thank Bearcat and IG-88 for all their help and I'll share how I was able to solve my problem and get this to work.
I used Juns Loader 6.1 and I modified the file for the VID, PID, Time delay and used the extra.lmza file instead of the stock lmza. Updated my bios and disabled C1E.
C1E kept resetting itself and finally a comment by IG-88 about the BIOS always resetting made me think. I had my old flash drive with the old bootloader in my machine so that I could shut down thru the DSM interface and apparently this was causing the problem. I took that out, changed the BIOS settings and they held thru multiple power cycles by just using the power button. I then installed the flash drive with the new bootloader and it took. I have now cycled the machine numerous times and it seem to be working fine.
Does anyone know why the old bootloader would have been resetting my BIOS to default?
Now I have two more questions:
1 I'm receiving a system health warning that says "System Partition Failed" Is this an issue with the bootloader or a different issue? Any way to solve this?
2 DSM is offering an update to 6.1.7-152834 Update 3. Is it OK to dowload this in DSM and use the file for a manual update? I remember in the past that sometimes this was not recommended and could cause problems.
Once again thanks to Bearcat and IG-88. I never would have been able to get this solved without their help.
Frank
-
On 10/11/2019 at 11:03 AM, IG-88 said:
no, imho the only choice is to find out about c1e option in bios
is there any indication that the system is returnung to bios defaults?
do you cut power between setting it in bios and booting the loader? - if the cmos buffer cell is to old then you might loos bios settings when cutting power
usualy you get a message about the system loosing settings and returning to defaults
try to set date and time in see if it keeps that
IG-88,
I was terribly frustrated and needed to take a little time off from this project. I flashed a new BIOS to the machine tonight and then I reset the C1E and rebooted and behold the time, date and status of C1E reverted from their changed and correct settings to incorrect time and date and C1E was Enabled again.
I replaced the CMOS battery and reset everything again and yes, it still is reverting to defaults. By the way the old CMOS battery was reading 3V DC so I don't think that was the problem.
As far as restarting goes, yes I always shut down the system before removing the old flash drive and inserting the new flash drive.
Any ideas?
Thanks,
Frank
-
9 minutes ago, bearcat said:
That's the spirit, go for the win
Anyone (with enough money) can buy a genuine Synology, but what do "we" learn from that? Not much
It might be that the 6.x bootloader made the BIOS change the C1E setting, as I think "enabled" is the default setting.
And from what I recall, even from some posts in this forum, the G7 internal NIC will never work with C1E enabled.
I'l keep my fingers crossed, and hope you find gold during the weekend.
Thanks for the encouragement but I just tried again, not found on network. Checked the C1E controller and it is Enabled again, so is there a different Boot Loader I can use that will not keep enabling this or perhaps will a different bios solve the problem? I'm truly stumped. (Stuipid?)
-
7 minutes ago, bearcat said:
Don't give up, it has to work
as others are using the same combination of HW and bootloader (without other drivers etc.)
Did you doublecheck the C1E setting?
If that is all OK, you may consider flashing the BIOS, since most of the working setups have done so.
When you boot using your working DSM 5.x, you get a reserved IP, what happens if you boot DSM 6.x and try to ping that adress?
If you decide to get a new add-on NIC, you should aim for a NIC that is compatible with DSM 6.2.x (or higher?)
as your internal NIC will stop working if you are using"out-of-the-box" Jun's Loader v1.03b DS3615xs when you upgrade to 6.2.1
Due to the space available, you will need a NIC with a low profile bracket, some new cards sometimes come with both normal and low profile.
I once made a listing in this post of some Intel based cards that should be good for 6.2 but there are others as well.
Personally, I have had good experience with the HP NC360T, that may be found chep on e-bay but be sure to get the low profile bracket.
Yes, I checked C1E and it had somehow reverted but I changed it and checked it on next boot. When I ping I receive timed out response. Thanks for the NIC info. If I get a better attitude I will flash the BIOS this weekend and see what happens.
Thanks again for all your help. I could have bought a Synology for all the time I've put into this but I'm like a dog with a bone on these projects, I just want to win!
OK, so I just checked again and the setting for C1E is Enabled again!!! I wonder why it keeps re-enabling itself?
-
1 minute ago, IG-88 said:
replace/overwrite, also they can't be in the same folder with the same name - at least not with this file system (FAT)
you know about the access to the local console by serial calbe (null modem)?
that way you can see it its booting up and even login to the console the check the log (dmesg)
you also can try a different network adapter with a intel or realtek chip
I know these NIC's are different than for a typical PC (smaller?). Do you know offhand what I should be looking for? No I'm not familiar with hooking up with a serial cable for access, I do have a monitor connected.
-
31 minutes ago, IG-88 said:
no, setting the mac is only important for WOL or when using a "pair" of SN and mac (surveillance station licensing?), SN might be checked for some plugins or licensing features like certain codes or transcoding
if you just use the image from jun "as is" even without vid/pid change then you should at least see the booted system in network, not setting vid/pid will later result in a error when trying to install DSM pat file, just for checking out if the network drivers are running you can just use the image in its original state (and add a extra.lzma for more drivers if needed)
I guess this is not going to work for me. I've tried all these things including the unmodified loader and then just changing the ramdisk and no results. One last question, should the original extra.lzma file be deleted and replaced with the extra.lmza or should they both be in the folder? I deleted and replaced in my case.
Thanks
-
40 minutes ago, bearcat said:
Ok, I', a bit confused.... (happends all the time btw. ;-))
If you are able to SSH into your box, it IS online, yes?
The above highlited text, is telling me your internal NIC, HP NC107i (based on BCM5723), is running with the correct driver.
(if memory serves me right, that driver is part of the extra.lmza in Jun's bootloader).
There was a problem with the original BIOS from HP, causing the NIC to not work with Server 2012 and Win 8.1, and it was fixed by a update in 2013.
I'm not sure if that could be related to your problem, as I (and most others) don't use the original HP BIOS.
In addition to "TheBay" as I use, there are other known working mod-BIOS'es, take a look here.
Edit:
Did you use DHCP (with or without fixed lease) or static IP when running DSM 5.x?
Did you use the real MAC or a "fake" MAC in your grub.cfg?
Edit 2:
As can be seen here I have a N40L running DSM 6.2 with only the internal NIC, and a "clean" version of Jun's bootloader.
Bearcat,
Sorry if I've confused you, I rebooted back to 5.2-5644. Since it's never been found on the network I've never loaded the new .pat file. I guess I'll give a new bios a try and see if it will go then. I use a fixed ip address from the router, DSM set to DHCP. I use the "real" MAC in the grub file and a serial number from the generator. Does any of that indicate a problem?
Thanks again,
Frank
-
Unfortunately Synology Assistant still can't find NAS on network and ping receives no reply.
COmpletely different question, I've never set a virtual machine but can you tell me if this theory is correct?
1: Boot into virtual machine
2: try to update from update window in DSM-this would only be to 5.2-5967
3: If this works in a virtual machine then try it on the bare metal version thru DSM
-
Thanks, I'll try that now.
-
11 minutes ago, IG-88 said:
you can try the extra.lzma the tutorial mentions
IG-88,
Thank you for the reply. I have a couple of questions about the ramdisk, first of all I see 4 versions listed on the page referenced from the link and I do not know how to determine the proper version for my use. I'm guessing " extra.lzma for ds3615 v4.8 ". Secondly, where do you put this? I assume this is something that needs to be modified in Jun's loader but I do not know what to do.
Thanks again,
Frank
-
3 hours ago, Knarf said:
Bearcat,
Thanks for the link to the screenshot of the HP Bios screen. I double checked and found the option to disable C1E. It was way down at the bottom of the page and in my late night fog I didn't scroll down far enough. So after disableing C1E I tried to boot from the usb I made from Polanskiman's tutorial and still not showing up in the network. Later today or tonight when I have time I will make a new usb stick from your link and try again.
Thanks for your patience and help.
Frank
Well I've created a fresh usb with the modded bootloader and I make it to the Happy hacking screen as shown in the tutorial but my machine still does not show up on the network. My BIOS ID is :041, The version is :07/29/2011. Do you think I have a BIOS issue or do I need a different NIC?
This is the result I get from SSH
ZenStation> lspci|grep 0200
02:00.0 Class 0200: Device 14e4:165b (rev 10)ZenStation> ethtool -i eth0
driver: tg3
version: 3.137h
firmware-version: 5723-v3.35
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: noZenStation> lspci -k
00:00.0 Class 0600: Device 1022:9601
Subsystem: Device 103c:1609
00:01.0 Class 0604: Device 103c:9602
00:06.0 Class 0604: Device 1022:9606
Kernel driver in use: pcieport
00:11.0 Class 0106: Device 1002:4391 (rev 40)
Subsystem: Device 103c:1609
Kernel driver in use: ahci
00:12.0 Class 0c03: Device 1002:4397
Subsystem: Device 103c:1609
Kernel driver in use: ohci_hcd
00:12.2 Class 0c03: Device 1002:4396
Subsystem: Device 103c:1609
Kernel driver in use: ehci-pci
00:13.0 Class 0c03: Device 1002:4397
Subsystem: Device 103c:1609
Kernel driver in use: ohci_hcd
00:13.2 Class 0c03: Device 1002:4396
Subsystem: Device 103c:1609
Kernel driver in use: ehci-pci
00:14.0 Class 0c05: Device 1002:4385 (rev 42)
00:14.1 Class 0101: Device 1002:439c (rev 40)
Subsystem: Device 103c:1609
00:14.3 Class 0601: Device 1002:439d (rev 40)
Subsystem: Device 103c:1609
00:14.4 Class 0604: Device 1002:4384 (rev 40)
00:16.0 Class 0c03: Device 1002:4397
Subsystem: Device 103c:1609
Kernel driver in use: ohci_hcd
00:16.2 Class 0c03: Device 1002:4396
Subsystem: Device 103c:1609
Kernel driver in use: ehci-pci
00:18.0 Class 0600: Device 1022:1200
00:18.1 Class 0600: Device 1022:1201
00:18.2 Class 0600: Device 1022:1202
00:18.3 Class 0600: Device 1022:1203
00:18.4 Class 0600: Device 1022:1204
01:05.0 Class 0300: Device 1002:9712
Subsystem: Device 103c:1609
02:00.0 Class 0200: Device 14e4:165b (rev 10)
Subsystem: Device 103c:705d
Kernel driver in use: tg3I unfortunately have no idea what any of this means. I'm a slightly accomplished home networker but this is way above my head. I can type in the commands and follow directions (sometimes) but when something goes wrong I'm lost.
Once again thanks for the help.
-
Bearcat,
Thanks for the link to the screenshot of the HP Bios screen. I double checked and found the option to disable C1E. It was way down at the bottom of the page and in my late night fog I didn't scroll down far enough. So after disableing C1E I tried to boot from the usb I made from Polanskiman's tutorial and still not showing up in the network. Later today or tonight when I have time I will make a new usb stick from your link and try again.
Thanks for your patience and help.
Frank
-
1
-
-
1 hour ago, bearcat said:
Thank you for the reply. before I did the update I looked in my bios and I do not show any settings for ce1. Does this mean I need a newer bios for my hpn40l before I proceed again?
Thanks again.
-
I'm currently running 5.2-5644.3 and I'd like to update to at least 5.2-5967 which my machine is offering me on the update page. There was a time that with certain installations that worked, but mostly I remember always reading not to update from within the machine offerings.
So I followed Polanskiman's tutorial on migrating from 5.2 to 6.1.X (Jun's Loader). I get the same screen shown in the tutorial once I boot but Synology assistant never finds NAS. Will replacing the NIC solve this problem? I've seen a reference to that but I think it's for a later version.
One way or another I'd appreciate any direction on either getting 6.1 to work or what bootloader and Pat file I'll need for 5.2-5967. I've searched and worked on this all week and just can't find the answers I'm looking for so I hope someone here has some info.
Thanks
Frank
-
That worked just great for the hibernation issue.
Thanks for the tip.
-
I'll give that a shot. Thanks
-
I too did the auto update and now am not able to hibernate. I will not make this mistake again. Is there a way to rollback to the prior version? I tried installing a fresh image but when I used the PAT file it asked for a newer version.
-
I too had this problem and when I went in to edit my version was listed as 5565, not 5022. I followed the editing directions listed lower in the forum "Downgrade 5565 to 5022" and did not have any luck when I allowed Synology Assistant to automatically apply the latest update. When I used the manual option and used the PAT file from my original installation everything worked fine. You will still need to turn off windows file sharing and restart it and you may need to go into the advanced settings and clear the SAMBA cash.
Good luck and a big thanks to hongong3 for all his help.
HP N40L upgrade to 6.1.7 not showing up on network
in Answered Questions
Posted
Bearcat,
No problems before my big adventure upgrading. After, there were suddenly lots of bad clusters.
Then the RAID listed as degraded and the drive was no longer in play.
I removed all drives and put them back and it tried again to initialize but failed.
Since I don't have the original BIOS I'm not able to compare, and that is probably beyond my skills to boot.
I took the drive out and placed it in a windows machine and used Minitool partition Wizard to try to format it and start over and after trying to wipe the drive it came back with "Bad Drive" message.
My takeaway from all this is that somehow the upgrade process killed that drive. I don't know how that is possible but it did. New drive will arrive tomorrow and I'll install it and hopefully my array will rebuild sucessfully.
Thanks for your reply. Is there a way to mark this thread closed on this forum? I've looked but didn't see it, most forums want you to do that when your questions have been answered.
Frank