liukuohao

Annoying BIOS reset issue is really bugging me!!!

Recommended Posts

This is a disk image of my pen drive (512MB SD card). Plz try if it works or not: https://drive.google.com/file/d/0Bwkmhb ... sp=sharing

 

This file is created by:

1. Download Synoboot: https://github.com/Jman420/nanoBoot-DSM ... 3612xs.img

2. Write the file to pen drive.

3. Expand the partition and filesystem to ~100MB. Expansion of ext filesystem is way easier than FAT, and that is one of the reasons why I choose Synoboot.

4. Replace zImage with *ORIGINAL* XPEnology 5.6-5644.5 one.

5. Compress modified ramdisk (with synobios.ko hax) with gzip as rd.gz

6. Add initrd parameter in /boot/grub/grub.conf.

7. dd if=/dev/sdX of=img

 

Thks Updateing the bios does not reset on microserver gen 8, im testing the installation just now!!!!!1

Share this post


Link to post
Share on other sites

Hi,

 

for now it works, but i can not change the server time as it throws an exception

 

EDIT: The time cannot be changed with the patched file, BUT: if you set the bios time in UTC format, than the DSM will apply your timezone and you have the correct time in DSM

 

Apr  5 22:24:04 dsm ntpdate: Sync with time server 216.239.32.15 offset -7199.349312 sec.
Apr  5 22:24:06 dsm kernel: [15185.765355] BUG: unable to handle kernel NULL pointer dereference at           (null)
Apr  5 22:24:06 dsm kernel: [15185.765361] IP: [<          (null)>]           (null)
Apr  5 22:24:06 dsm kernel: [15185.765363] PGD 94d2f067 PUD 94cf1067 PMD 0 
Apr  5 22:24:06 dsm kernel: [15185.765365] Oops: 0010 [#5] SMP 
Apr  5 22:24:06 dsm kernel: [15185.765446] CPU: 1 PID: 1676 Comm: SYNO.Core.Regio Tainted: P      D    O 3.10.35 #1
Apr  5 22:24:06 dsm kernel: [15185.765448] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 07/16/2015
Apr  5 22:24:06 dsm kernel: [15185.765450] task: ffff8801422d8dc0 ti: ffff880095800000 task.ti: ffff880095800000
Apr  5 22:24:06 dsm kernel: [15185.765451] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
Apr  5 22:24:06 dsm kernel: [15185.765453] RSP: 0018:ffff880095803d40  EFLAGS: 00010282
Apr  5 22:24:06 dsm kernel: [15185.765454] RAX: 0000000000000000 RBX: ffff880095803dec RCX: 0000000000000000
Apr  5 22:24:06 dsm kernel: [15185.765455] RDX: 0000000000000000 RSI: ffff880095803d60 RDI: 0000000000000000
Apr  5 22:24:06 dsm kernel: [15185.765457] RBP: ffffffffffffffe7 R08: 0000000000000006 R09: 0000000000000064
Apr  5 22:24:06 dsm kernel: [15185.765458] R10: 0000000000000002 R11: 000000000000022b R12: 00000000ffff73c9
Apr  5 22:24:06 dsm kernel: [15185.765459] R13: ffff880095803d60 R14: 0000000000000006 R15: 0000000000000000
Apr  5 22:24:06 dsm kernel: [15185.765461] FS:  0000000000000000(0000) GS:ffff880147a40000(0063) knlGS:00000000f6575900
Apr  5 22:24:06 dsm kernel: [15185.765462] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Apr  5 22:24:06 dsm kernel: [15185.765463] CR2: 0000000000000000 CR3: 0000000003352000 CR4: 00000000001407e0
Apr  5 22:24:06 dsm kernel: [15185.765464] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr  5 22:24:06 dsm kernel: [15185.765466] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr  5 22:24:06 dsm kernel: [15185.765466] Stack:
Apr  5 22:24:06 dsm kernel: [15185.765468]  ffffffffa0c4e4f3 ffff88014703f3a0 ffff880143002740 00000008f9ccf980
Apr  5 22:24:06 dsm kernel: [15185.765470]  ff74030502141806 ffff88014703f3a0 ffffffff81116f82 ffff88013ed23d80
Apr  5 22:24:06 dsm kernel: [15185.765472]  ffff880095803e80 ffff880095803e60 ffffffff8111ebf1 ffff88013ed23d80
Apr  5 22:24:06 dsm kernel: [15185.765475] Call Trace:
Apr  5 22:24:06 dsm kernel: [15185.765481]  [] ? synobios_ioctl+0xda3/0x1060 [bromolow_synobios]
Apr  5 22:24:06 dsm kernel: [15185.765485]  [] ? dput+0x22/0x1b0
Apr  5 22:24:06 dsm kernel: [15185.765488]  [] ? mntput_no_expire+0x21/0x170
Apr  5 22:24:06 dsm kernel: [15185.765491]  [] ? path_openat+0x16d/0x4b0
Apr  5 22:24:06 dsm kernel: [15185.765494]  [] ? tlb_flush_mmu+0x4c/0x80
Apr  5 22:24:06 dsm kernel: [15185.765497]  [] ? do_filp_open+0x42/0x90
Apr  5 22:24:06 dsm kernel: [15185.765501]  [] ? compat_sys_ioctl+0x1e7/0x1500
Apr  5 22:24:06 dsm kernel: [15185.765504]  [] ? do_sys_open+0x15f/0x1e0
Apr  5 22:24:06 dsm kernel: [15185.765507]  [] ? sysenter_dispatch+0x7/0x21
Apr  5 22:24:06 dsm kernel: [15185.765508] Code:  Bad RIP value.
Apr  5 22:24:06 dsm kernel: [15185.765512] RIP  [<          (null)>]           (null)
Apr  5 22:24:06 dsm kernel: [15185.765514]  RSP 
Apr  5 22:24:06 dsm kernel: [15185.765515] CR2: 0000000000000000
Apr  5 22:24:06 dsm kernel: [15185.765523] ---[ end trace 87ffe4544997847d ]---

Share this post


Link to post
Share on other sites
Hi,

 

it works for HP MicroserverGen8. All credits go to updateing!

 

#Link

http://www54.zippyshare.com/v/6ktoFqSp/file.html

 

#to load the modified vmlinux place the rd.gz next to syslinux.cfg on your bootstick and change syslinux.cfg

# from

APPEND root=/dev/md0 ihd_num=0 

# to

APPEND root=/dev/md0 initrd=rd.gz ihd_num=0 

 

######## Helpful commands ########

 

#mount bootdrive in ssh session

#!/bin/sh

MOUNT_FOLDER="/root/boot"

mkdir -p ${MOUNT_FOLDER}
LOOP_DEVICE="$(losetup -f)"
losetup -o 32256 ${LOOP_DEVICE} /dev/synoboot
mount -t vfat ${LOOP_DEVICE} ${MOUNT_FOLDER}

 

#unmount bootdrive

#!/bin/sh

umount /root/boot
losetup -d /dev/loop0
rmdir /root/boot

 

# And for the HP Microserver Gen8 users, with this you can change DSM to only see the 4 really existing hdd drives and not the other dummy ones

#in /etc.defaults/synoinfo.conf
#no esata ports
esataportcfg="0x0"
#4 sata ports
internalportcfg="0xf"
#6 usb ports (2 front and 4 back)
usbportcfgo="0x2f0"

 

Hi,

 

I tried to copy the rd.gz next to syslinux.cfg on my bootstick, which has a Fat16 File System, but it has not enough free space.

 

So, I tried to allow more space with Gparted, but I got this error : "File system doesn't have expected sizes for Windows to like it. Cluster size is 2k ..."

 

Could you help me ?

 

Regards

Share this post


Link to post
Share on other sites

Hi,

 

i had the same problem with gparted. WHat i did was boot from a Hiren-Bootcd and modified the partition with PartitionMagic. So for you, take Acronis or any other Partition tool, can also be a windows tool and modify the partition with that instead of gparted.

Share this post


Link to post
Share on other sites
This is a disk image of my pen drive (512MB SD card). Plz try if it works or not: https://drive.google.com/file/d/0Bwkmhb ... sp=sharing

 

This file is created by:

1. Download Synoboot: https://github.com/Jman420/nanoBoot-DSM ... 3612xs.img

2. Write the file to pen drive.

3. Expand the partition and filesystem to ~100MB. Expansion of ext filesystem is way easier than FAT, and that is one of the reasons why I choose Synoboot.

4. Replace zImage with *ORIGINAL* XPEnology 5.6-5644.5 one.

5. Compress modified ramdisk (with synobios.ko hax) with gzip as rd.gz

6. Add initrd parameter in /boot/grub/grub.conf.

7. dd if=/dev/sdX of=img

 

Hi,

 

I finally used your disk image.

 

I had to change my settings with this command (ubuntu) :

 

sudo nano '/media/***/boot/grub/grub.conf'

 

Everything seems to works for the moment.

 

Regards

Share this post


Link to post
Share on other sites
Hi,

 

i had the same problem with gparted. WHat i did was boot from a Hiren-Bootcd and modified the partition with PartitionMagic. So for you, take Acronis or any other Partition tool, can also be a windows tool and modify the partition with that instead of gparted.

 

Thank you for this usefull tip.

 

Regards

Share this post


Link to post
Share on other sites

Excuse me ladies and gentlemen,

 

For the benefit to those, who is a real noob like me.

Who does not know a single Linux command usage and meaning.

Can the person who contribute the solution educate the people

step by step on how to circumvent the problem. Please........ :roll:

 

I will try to post pictures or diagrams for all user to understand better

if someone can help me. Please........ :wink:

 

I love to nail the problem once for all.

 

Thank you.

Share this post


Link to post
Share on other sites

Hi,

 

you can use the tutorial on xpenology.us for flashing the bootimage onto a usb stick. But instead of using their provided ".img" file you can use the file updateing provided and just flash it with for example win32diskimager onto your usb stick or microsd card.

 

But keep in mind, as sad in the post before, the time-settings wont work as whe hit e kernel exception when tryin to set the time. so you have to set your bios time in UTC-Timezone and in dsm you set your timezone. that worked for me

 

 

Greetz

Share this post


Link to post
Share on other sites

Hi,

 

This fixes the bios reset issue, but unfortunately the scheduled power on from DSM does not work :sad:

Share this post


Link to post
Share on other sites

No, I have just installed Xpenology with no additional packages. I have configured scheduled power on / off from control panel for testing purpose. I have tried it before this fix and it work. Can it be related to the UTC time? I have configured UTC+3 in synology.. the bios is configured UTC.. I didn't wait 3 hours to see if it starts.

Thanks

Share this post


Link to post
Share on other sites

This is a disk image of my pen drive (512MB SD card). Plz try if it works or not: https://drive.google.com/file/d/0Bwkmhb ... sp=sharing

This file is created by:

1. Download Synoboot: https://github.com/Jman420/nanoBoot-DSM ... 3612xs.img

2. Write the file to pen drive.

3. Expand the partition and filesystem to ~100MB. Expansion of ext filesystem is way easier than FAT, and that is one of the reasons why I choose Synoboot.

4. Replace zImage with *ORIGINAL* XPEnology 5.6-5644.5 one.

5. Compress modified ramdisk (with synobios.ko hax) with gzip as rd.gz

6. Add initrd parameter in /boot/grub/grub.conf.

7. dd if=/dev/sdX of=img

@updateing, you are my hero. I can now use my old Dell towers that suffered the bios corruption issue. Just verified full functionality and perfect restarts from the DSM on an Optiplex 755. I used Win32DiskImager with your pre-made img "XPEnology-Synoboot-512MB-5644.5.7z" and it works flawlessly. 

I just made the same edit as @tahitibub in the grub.conf to adjust my vid and pid and wow, flawless.

This is great. I can't thank you enough!

 

 

Posted via Xpenology.us

Share this post


Link to post
Share on other sites
As there has been some progress on this issue would it be a good idea to make this thread a sticky?

 

Has everyone try it? If Yes and it does work for ALL kinds of motherboard, why not?

 

If the Development Team is happy and satisfy this solution works, I don't see why the admin of the forum cannot make it as a sticky.

Share this post


Link to post
Share on other sites
As there has been some progress on this issue would it be a good idea to make this thread a sticky?

 

Has everyone try it? If Yes and it does work for ALL kinds of motherboard, why not?

 

If the Development Team is happy and satisfy this solution works, I don't see why the admin of the forum cannot make it as a sticky.

Share this post


Link to post
Share on other sites

This fix seems to works for everyone so it should be included in next release :smile:

Big thanks to the XPEnology community :mrgreen:

Share this post


Link to post
Share on other sites

Hi,

 

still remember that this fix will cause kernel exceptions for example when youre trying to change vom manual time to ntp-based time

Share this post


Link to post
Share on other sites
Hi,

 

still remember that this fix will cause kernel exceptions for example when youre trying to change vom manual time to ntp-based time

 

Can someone from the forum verify that hoppler is correct? :roll:

 

As for myself, I used to have motherboard = Supermicro PDSME server motherboard

URL = http://www.supermicro.com/products/motherboard/PD/E7230/PDSME.cfm

which give BIOS corrupt = CMOS checksum error upon every reboot during POST.

However this motherboard of mine is DEAD, so I cannot claim for sure that

Updateing image works for me. :smile:

Share this post


Link to post
Share on other sites

Tried this myself on my Optiplex 760, Definitely fixes reboot function, However you loose the ability to use Power Schedule in control panel, Does not work

Share this post


Link to post
Share on other sites
Tried this myself on my Optiplex 760, Definitely fixes reboot function, However you loose the ability to use Power Schedule in control panel, Does not work

 

Hi derwoodbones

 

While I am testing updateing boot image just a few minutes ago, my result is different than yours.

 

My BIOS time is actually incorrect configured by DSM or XPEnoboot. I am not sure which actually set it. :???:

But it is definitely not showing the ACTUAL local time at where I am staying. It is actually 8 hours behind.

If my local time is 19 hours(at night), the BIOS time will show 11 hour (at morning)

However within DSM, it does show the CORRECT time.

 

So, for my side, under power schedule, auto shutdown works no problem.

And as usual, auto start up does not work for me. :smile:

Next I am leave the power off and see whether it will auto boot in the morning.

Share this post


Link to post
Share on other sites

Using updateing boot image, auto start in power schedule does not work either :cry:

 

So have to keep trying guys!

Share this post


Link to post
Share on other sites

We edit the kernel sources instead of patching the synobios.ko file.

But the result is the same : It solve the BIOS reset issue but it breaks the power on/off schedule.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now