-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial Password? #2
Comments
yeah I know.. it doesn't work as expected.. About the kernel panic I get the same problem some times when booting, if you reboot finally goes fine. About AUTO_ATTACH is a parameter for the base I used for Docker/KVM from BBVA guys. Feel free to PR any fix you can do. |
Thanks for that pw. I'm currently more working on getting my own synoboot.img (w/ 1.02b / DSM 6.1.x) to work. As I found out, you have a whole different startvm-script in that docker-hub image compared to what is here on Github. So a
...worked better for booting and I actually could install a fresh DSM inside docker. What is the reason for that difference? Is there certain kernel modules you expect to make this github-version running? I tried adding various virtio-modules, but that didn't work either... About PoC: do you have a specific reason why you wouldn't recommend it for production? (...well at least some kind of "production" one would actually considering Xpenology for...) |
admin/1234 doesn't work. Not getting kernel panics or anything weird, just cannot log in. I'm on segator/xpenology:latest, btw. |
Wild guessing led me to find admin/123456 works!!! Playing with it now. |
After running the interactive command, I was able to create and run this docker, and I can log in in the terminal. However I cannot access it with my browser, eventhough the port is forwarded. from the docker terminal itself, when I tried ifconfig, it got the 169 ip address. Any idea why is that? Thanks so much! I really hope this can be working :) |
Umh dhcp not working? Are u runing in host mode maybe? |
I was running it on bridge mode, I noticed some errors in the log:
and this one:
Also, I cannot select anything during the boot menu, is that correct? Here is the complete log: ++ vtapdev=macvtapbdfeea ++ IFS=: x dnsmasq: junk found in command line INFO: Launching qemu-kvm +----------------------------------------------------------------------------+||||||||||||||||||||||||+----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted.
Insert basic USB modules... :: Loading module mptscsih ... [ OK ] :: Loading module mptspi ... [ OK ] :: Loading module mptsas ... [ OK ] :: Loading module mptctl ... [ OK ] :: Loading module ata_piix[ 31.852473] ata1: Read current link speed fail, retry 1 [ 31.870496] ata1: Read current link speed fail, retry 2 [ 31.888546] ata1: Read current link speed fail, retry 3 [ 31.910486] ata2: Read current link speed fail, retry 1 [ 31.937489] ata2: Read current link speed fail, retry 2 [ 31.964479] ata2: Read current link speed fail, retry 3 ... [ OK ] :: Loading module megaraid_sas ... [ OK ] :: Loading module mpt2sas ... [ OK ] :: Loading module mpt3sas ... [ OK ] Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... 1.42.6-8438: recovering journal 1.42.6-8438: |== | 3.7%
/sbin/e2fsck returns 1 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure No upgrade file exists End upgrade procedure ============upgrade Wait 2 seconds for synology manufactory device Fri Feb 14 16:40:00 UTC 2020 /dev/md0 /tmpRoot ext4 rw,relatime,journal_checksum,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 sys /sys sysfs rw,relatime 0 0 none /dev devtmpfs rw,relatime,size=504916k,nr_inodes=126229,mode=755 0 0 proc /proc proc rw,relatime 0 0 linuxrc.syno executed successfully. Post init rc.extras in init.post ==================== start udevd ==================== ===== trigger device plug event ===== |
@segator
|
work well with
|
Sorry, probably I'm completely missing the point, but I have troubles getting this to run...
If I try your stuff from DockerHub (so without building myself)...
...I end up in a Kernel Panic on that VM half a sec later...
When I try to start...
...I actually get something booting. After some seconds I get asked for "Diskstation login:" and some password which I do not know and couldn't find googling. Actually DSM already responds at port 5000 with a standard login screen, but no hint on what password to use...
So I tried building that docker image by myself. What do you mean with "xpenology image"? I used this Jun Loader thingies (I've tried DS3615xs V6.1 and V6.0.2). Docker build went fine, but the VM shows some Grub screen and then locks up with blank screen on 100% CPU... nothing responding anymore...
I can provide all the log outputs I required...
Oh, and btw... AUTO_ATTACH appears to be necessary, but obviously does not have an effect on this issue (...a least I tried "Y" and "N" - no effect).
Erm... and yes, sorry, but I'm pretty new to this Xpenology...
Thanks in advance,
Losty
The text was updated successfully, but these errors were encountered: