lysin
-
Posts
12 -
Joined
-
Last visited
Posts posted by lysin
-
-
I tried with force install and it worked, but now, every time my machine boots, this error comes up...
Any ideas?
-
I've tried migrating to the new alpha, but got this error instead:
"We've detected errors on the hard drives (6), and the SATA ports have also been disabled.
Please shut down your DS3615xs to replace or remove the hard drives and try again."
I'm using the same SATA configuration as 6.0.2 loader (SataPortMap=4), and I also tried SataPortMap=1, SataPortMap=5 and SataPortMap=6.
No luck.
I´ll try again later today using the forced mode.
-
I can confirm it works on gen 8.
Ordered Microserver, but not works
Install ok. reboot and say "migrable" all in loop... any suggestion?
Used the UEFI/Legacy image on page 10. Set sata to ahci in bios
Can You share your grub.cfg?
Thanks
@tuonoazzurro
Download the UEFI image version, browse the image and copy the ramdisk file and replace the one one on your current image with that one.
-
Right, this is another issue of missing console, I am thinking about a proper (out of box) workaround.
root@test:~# grep -r "^console output$" /usr/ 2> /dev/null /usr/share/init/syno_poweroff_task.conf:console output /usr/share/init/burnin_loader.conf:console output /usr/share/init/udevtrigger.conf:console output /usr/share/init/bs-poweroff.conf:console output /usr/share/init/udevd.conf:console output
Notice that above service want to output to a console, so they will failed to start for the unlucky guys .
Simply change "console output" to "console none" should work.
I thought most board had a serial port, even if not populated, could always be seen by software if enabled, it is a standard part of PC, is that not the case?
In my case, all of my boards have serial headers, I just need to enable it somewhere in BIOS. OK, my boards are mainly Asrock ones, so maybe my observation is biased.
For debugging purpose, I add a DB9 connector to the serial header, but that is not required for normal users.
I also have an ASROCK, but unfortunately mine doesn't have a serial port.
Anyway, I edited those files and the "improper shutdown" notice is gone.
-
Just rename the file? Nice one!
I can confirm that simply renaming the file seems to do the trick. No more spam.
-
I've tried both UEFI and legacy UEFI/BIOS and both are working fine.
I have one problem tough... Every time I shutdown my machine, I got an "improper shutdown" notification on the next boot.
Anyone else experiencing this?
Cheers
Me too
And me..
Not too worried about it though.. I would say this is a nice to have (unless there really is a problem that puts the data at risk)..
Exactly, I don't mind it, but I don't know if it may or may not affect the disks... And that worries me!
-
I've tried both UEFI and legacy UEFI/BIOS and both are working fine.
I have one problem tough... Every time I shutdown my machine, I got an "improper shutdown" notification on the next boot.
Anyone else experiencing this?
Cheers
-
I've been monotoring with cat /sys/bus/platform/devices/coretemp.0/temp?_input...
you should get something like this...
NAS
- 1
-
-
Yep, I'm really excited about 64bit support and a few new features.
Wondering how soon our xpenology's will see an update...
Posted via Xpenology.us
-
Yep, I'm really excited about 64bit support and a few new features.
Wondering how soon our xpenology's will see an update...
Posted via Xpenology.us
DSM 6.1.x Loader
in Loaders
Posted
Not really. All my pre existing volumes maintained the same used/free space ratio, and my SSD that I use as cache it's working properly and with the correct size/space available.
Anyone has any tips on debugging this issue?