liukuohao

If I am not mistaken, Marvell chipset is flaky. You can google it. Yes, I know this link is about UNraid, but it is based Debian Linux. https://unraid-guides.com/2020/12/07/dont-ever-use-cheap-pci-e-sata-expansion-cards-with-unraid/ If you want stability, preferably if possible try to get an server grade HBA card and flash it with IT mode.

So in other words, there is no issue whatsoever in applying the major & minor updates?

Hi, I just want to get some general rule of thumb, what is the best way to update your Xpenology PC. Ultimately you have to decide whether your Xpenology PC is in production phase or testing phase? So if it in production phase, update it on a testing Xpenology first, check is there any issue arise, before updating on your production one in order to prevent unexpected fail login into DSM web interface / data loss, as such suggested by the forum administrator: What is the best method of updating? A) I know I can refer to this place before applying updates: https://xpenology.com/forum/forum/78-dsm-updates-reporting/ B) But I come across this from Google search: https://xpenology.org/updating-minor-versions/ which it teaches you download the updates, but don't apply it, but update it manually through using SSH client- using Putty and connect into your Xpenology NAS, enter a command and update from there. Thank you.

I don't see why it can't be supported, which loader you are using?

When you said you use a port multiplier, are you using this kind of hardware? The red cable is connected to your SATA 2 port of your motherboard, for example. I heard this kind of expansion is flaky. I wouldn't recommend to run in Xpenology.

Hi, Currently, I have a motherboard: GA-B85M-DS3H, it has 4 x SATA3 + 2 SATA2, total of 6 drives, it can support. CPU is an Intel i7-4770 CPU based on socket 1150, Haswell architecture. This motherboard support hot-swappable drives in the BIOS/UEFI. So, in order to take advantage this feature, I need have 6 drives connected during DSM installation? I am about to start 1st installation of DSM 7.x, however after reading the is information about selecting the hardware: DSM 7.x Loaders and Platforms - Tutorials and Guides - XPEnology Community I windows user for many years, not a linux pro. so naturally, I a bit confused about these terminologies: 1) SataPortMap 2) DiskIdxMap 3) device tree Questions: 1) If I am to select the architecture: apollolake, DS918+, how many drive would it be display within DSM, the number = 4, right? 2) Can appollolake, DS918+ supports more than 4 drives, but cosmetically, it can only show 4 drives? 3) What happen if I can a extra HBA into the PCI-E x16 slot, which can support 4 more drives, same issue, it will only shows 4 drives? 4) How to map out drives? 5) What is RAIDF1 support means? Thank you.

Ok thanks man, appreciated.

Thanks for your fast reply............. Can I use Rufus to make a image? Or It has to be Win32DiskImager?

Hello guys, After DSM 6.x is already installed. Is there a way to access the grub.cfg on the usb bootloader drive? I need to change the serial no. Previous version of DSM, e.g. within DSM 5, the OS allow user to view the content of the usb bootloader drive, and access the grub.cfg file using File Station. But under DSM 6.x this method is not available any more. Any advice will be appreciated. Thank you.

Weird Stuff?? Yeah..... What lesson you learned here............ First and foremost, back up your important data to a USB 3 portable hard drive. I suspect your PSU has reached the time to replace a new one. I suspect motherboard is not getting stable Voltage + Current to support all the devices running.

updateing I could not get 5644 to boot before using your version, I believe my issue was bzimage instead of zimage (it simply would never load). Anyway now that I got it booted I cant get the pat file to install. It just sits at 0% Here is what I have tried. 1. Removed hard drives and blanked them out with no partitions. 2. Tried a different set of hard drives 3. Disabled all hard drives but 2. Nothing allows the pat install to get past 0%. Any ideas? Previous version I could get to boot was 5565.2, no other version after that booted for me till I found your 5644.5 Hi madhits45 from what I gathered you are trying to installed Xpenology using updateing Image. However, after wasted much time on my own, and consulted a member from the forum. The updateing image is not suppose to install a fresh Xpenology. You are supposed to install Xpenology as per Normal way/route. That is the instruction is found here: http://xpenology.me/xpenoboot-5-2-5644-5-released/ After you have successfully installed, and if you find that your hardware still get corrupted BIOS every time it reboots Xpenoogy. (Note, it does happen often, only some motherboards do). You need to create the NEW image on your usb thumb drive using the updateing's version. Next you are going to use updateing's image to boot your Xpenology. And that will solve the annoying problem of messing up your motherboard's BIOS setting upon reboot. That is all. Basically you are replacing updateing image with the official release image, to boot up Xpenology.

Hi, I have got some old 7200rpm IDE hard disks lying doing nothing, I am think of reusing it in DSM. Modern motherboard only provides 1 IDE connector and that is all you have. Can add support for old hardware? PATA Host Adapter? See below: http://www.newegg.com/Product/Product.aspx?Item=N82E16816102012 I am not a Linux geek, so I not sure this link will help or not. Basically there is no official Linux drivers from Promise. But someone was kind to share out this link: http://www.lugh.de/promise/

Thank You Trantor . At least we nailed this annoying problem and users from the forum can use their own choice of motherboard without problem. But from my side of testing scheduled power off works fine, but not scheduled power on.

Using updateing boot image, auto start in power schedule does not work either So have to keep trying guys!

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. Next I am leave the power off and see whether it will auto boot in the morning.

Can someone from the forum verify that hoppler is correct? 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.

Has everyone try it? If Yes and it does work for ALL kinds of motherboard, why not? [emoji851] 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. [emoji851]

Has everyone try it? If Yes and it does work for ALL kinds of motherboard, why not? [emoji851] 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. [emoji851]

Ok, are you using 3rd party power management package? like Advance Power Manager for Synology DS Link: https://sourceforge.net/projects/advpowermgr4ds/? If so, please reply. Thank you.

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........ I will try to post pictures or diagrams for all user to understand better if someone can help me. Please........ I love to nail the problem once for all. Thank you.

Ok guys pls give "updateing" a big thank you for his effort of sharing his work. I am not in the position to verify the solution is workable or not, hopefully the developer can take a look and nail the problem once for all! [emoji106][emoji106][emoji106] Sent from my iPhone using Tapatalk

Hello vejta66 I created this post merely to address the issue of RESET BIOS, when you set time to turn on your XPEnologized PC. The intention is to create the awareness that such a problem exist when you are playing around with XPEnology. And also share the "workaround solution" and NOT requesting for a permanent fix. Because, neither me nor the fellow forum user is able to do it, unless we are the core developers. You need to PM the administrator as to how to solve this problem. So in short, I couldn't offer any help in answering your question regarding to X64 build. As far as I know, unless you are willing to change your hardware to a different motherboard, like INTEL DQ35JOE, there is no reset BIOS issue, but as of now, I CANNOT promise the lastest version of XPEnoboot + the lastest DSM image will NOT cause BIOS resetting problem. Simply because I couldn't find the time to test it

Nope, unfortunately, I am still waiting patiently, unless you willing to buy the developers some beer, may be they consider solving this age old problem.[emoji1] Sent from my iPhone using Tapatalk

Yeah, if you want to the lastest and greatest, using XPEnoboot, then that is the price you pay for..... unfortunately. If are happy about using Nanoboot, then should continue using it. Question in my mind never get answer.....under what special reason that the developers were not able to crack their heads and solve this age old problem???? All the best for the coming year 2016.

Hi Barat, I have not been very active in this post. Anyway thanks for sharing Unfortunately, for DSM 5.2, I am pretty sure BIOS reset issue is still exist even though I have not tested. Unless some one in the forum is willing to beg the differ. BIOS reset will occur during POST if you have scheduled the PC to shutdown certain time. Unless, you have tried new motherboards that uses the newest BIOS firmware UEFI. But still bear in mind, this is not an absolute fix on the problem. There is no 100% guarantee. You just have to keep trying new motherboards....till you are broke!!! Just kidding....