Re: Unable to boot QNAP TS-119 since update on 12 Nov
* Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-16 19:17]: I keep getting Failed to obtain MAC because eth0 seems to think it's MAC address is 00:00:00:00:05:09. I had hoped this issue would go away after reflashing the QNAP firmware and reformatting my harddrive. Unforturnately this didn't turn out to be the case. Is there any way to get around this? (you mentioned that you had identified the cause and were going to write it uo in http://lists.debian.org/debian-arm/2010/05/msg00052.html but I haven't found any further information on this issue) Sure, read http://forum.qnap.com/viewtopic.php?f=147t=30069 (Sorry, requires login... no idea why) -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131118165123.gb29...@jirafa.cyrius.com
Re: Unable to boot QNAP TS-119 since update on 12 Nov
* Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-16 06:34]: cat /dev/mtdblock0 /dev/mtdblock4 /dev/mtdblock5 /dev/mtdblock1 /dev/mtdblock2 /dev/mtdblock3 F_TS-119_debian and make that available for download, so that I can directly flash it, then that might spare me the process of having my disk wiped by the original firmware and re-installing from scratch. However, I'm not sure the boot will succeed (at least until sshd is started) if the flash doesn't match the debian version on disk. Martin? It won't work because the initramfs contains the UUID of your root partition. UUID is a unique ID. You have two options: 1) Flash Debian installer and use that to access your system on disk and flash the old kernel using flash-kernel version; see http://www.cyrius.com/journal/debian/installer-flash-kernel 2) Copy the old kernel/ramdisk from disk and generate a recovery image from them. As I mentioned, this is currently not documented on my page and I'm travelling at the moment. I might be able to write some instructions next week but you could just go with option 1). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131116093136.gi3...@jirafa.cyrius.com
AW: Unable to boot QNAP TS-119 since update on 12 Nov
Martin Michlmayr [t...@cyrius.com] wrote on 2013-11-16 10:31 1) Flash Debian installer and use that to access your system on disk and flash the old kernel using flash-kernel version; see http://www.cyrius.com/journal/debian/installer-flash-kernel I keep getting Failed to obtain MAC because eth0 seems to think it's MAC address is 00:00:00:00:05:09. I had hoped this issue would go away after reflashing the QNAP firmware and reformatting my harddrive. Unforturnately this didn't turn out to be the case. Is there any way to get around this? (you mentioned that you had identified the cause and were going to write it uo in http://lists.debian.org/debian-arm/2010/05/msg00052.html but I haven't found any further information on this issue) Regards Felix -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/126f2941065a084bbf03c60fe296864c2bc47...@exmbx2010-2.campus.mcgill.ca
Re: AW: Unable to boot QNAP TS-119 since update on 12 Nov
Hi Felix, 1) Flash Debian installer and use that to access your system on disk and flash the old kernel using flash-kernel version; see http://www.cyrius.com/journal/debian/installer-flash-kernel I keep getting Failed to obtain MAC because eth0 seems to think it's MAC address is 00:00:00:00:05:09. I had hoped this issue would go away after reflashing the QNAP firmware and reformatting my harddrive. Unforturnately this didn't turn out to be the case. Is there any way to get around this? (you mentioned that you had identified the cause and were going to write it uo in http://lists.debian.org/debian-arm/2010/05/msg00052.html but I haven't found any further information on this issue) There is one method which consist to reset your hardware (uboot) parameters. You'll then can read, and also write to your uboot environments varialbes, where is located the MAC adresses. *TAKE CARE* ; without serial console access, in case of any error, you can break your installation and brick your hardware, rendering it useless ! You can also force the MAC adresses with command line (ethtool I suppose) and then help installer-flash-kernel script correct it ? Or the solution I preffer; modify temporarly the script installer-flash-kernel to force the MAC @adress. I have never used QNAP hardware and cannot help you more than with theory... May be I am wrong on can be corrected by someone on the list. Regards, Gérald -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5287d2d4.9060...@doukki.net
Unable to boot QNAP TS-119 since update on 12 Nov
Hi there, I was following debian testing on a QNAP TS 119. Since the update late on 12 Nov 2013, I am unable to boot the device. While I haven't been able to root cause my problems, I suspect it might have to do with the kernel update included in that version. I have since then re-flashed the device but haven't gotten around to putting it back on-line. I was wondering whether anybody else has had better results on a similar device (kirkwood chipset) with the current jesse tree, which would point to a misconfiguration on my side. In which case I would consider staying on testing rather than dropping back to stable. Also, I have had the weird 00:00:00:05:0e mac address issue when trying to reflash the device referenced at http://lists.debian.org/debian-arm/2010/05/msg00052.html Unfortunately, I haven't been able to resolve this without re-inserting my HD which would make the QNAP firmware wipe it appearently. Is there any well known way to re-flash a current debian kernel without wiping the contents of the HD? Regards Felix
Re: Unable to boot QNAP TS-119 since update on 12 Nov
* Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-15 16:39]: I was following debian testing on a QNAP TS 119. Since the update late on 12 Nov 2013, I am unable to boot the device. While I haven't been able to root cause my problems, I suspect it might have to do with the kernel update included in that version. I take it you have no serial console? Is there any well known way to re-flash a current debian kernel without wiping the contents of the HD? You can generate a recovery image with the old kernel from disk. I thought there were intructions for this on my web site but I just checked and there aren't. :( -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131115172439.ge3...@jirafa.cyrius.com
Re: Unable to boot QNAP TS-119 since update on 12 Nov
I can make my ts 119 kernel image available for download. Would that help? It's wheezy. (Skickat från min telefon == Sent from my phone) On Nov 15, 2013 6:25 PM, Martin Michlmayr t...@cyrius.com wrote: * Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-15 16:39]: I was following debian testing on a QNAP TS 119. Since the update late on 12 Nov 2013, I am unable to boot the device. While I haven't been able to root cause my problems, I suspect it might have to do with the kernel update included in that version. I take it you have no serial console? Is there any well known way to re-flash a current debian kernel without wiping the contents of the HD? You can generate a recovery image with the old kernel from disk. I thought there were intructions for this on my web site but I just checked and there aren't. :( -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131115172439.ge3...@jirafa.cyrius.com
AW: Unable to boot QNAP TS-119 since update on 12 Nov
* Martin Michlmayr t...@cyrius.com [2013-11-15 18:24]: * Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-15 16:39]: I was following debian testing on a QNAP TS 119. Since the update late on 12 Nov 2013, I am unable to boot the device. While I haven't been able to root cause my problems, I suspect it might have to do with the kernel update included in that version. I take it you have no serial console? Sorry no. I'm also not very good at soldering. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/126f2941065a084bbf03c60fe296864c2bc47...@exmbx2010-2.campus.mcgill.ca
AW: Unable to boot QNAP TS-119 since update on 12 Nov
* Björn Wetterbom wrote on 2013-11-15 21:06 * Felix Andreas Braun felix.br...@mail.mcgill.ca [2013-11-15 16:39]: I was following debian testing on a QNAP TS 119. Since the update late on 12 Nov 2013, I am unable to boot the device. While I haven't been able to root cause my problems, I suspect it might have to do with the kernel update included in that version. I can make my ts 119 kernel image available for download. Would that help? It's wheezy. If you could export the entire contents of your flash cat /dev/mtdblock0 /dev/mtdblock4 /dev/mtdblock5 /dev/mtdblock1 /dev/mtdblock2 /dev/mtdblock3 F_TS-119_debian and make that available for download, so that I can directly flash it, then that might spare me the process of having my disk wiped by the original firmware and re-installing from scratch. However, I'm not sure the boot will succeed (at least until sshd is started) if the flash doesn't match the debian version on disk. Martin? Thanks anyway for your offer. Regards Felix -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/126f2941065a084bbf03c60fe296864c2bc47...@exmbx2010-2.campus.mcgill.ca
