Re: SS4000E install problem
Hello Paul, On Mon, Nov 09, 2015 at 07:00:08PM -0600, Paul wrote: [...] > I would like a copy of your notes if you find them. Yes, I found them :-) (Will be mailed in private to not bother the list.) But be carefull to not brick your Nas... > I have a couple of SS4000E I would like to do something with! Great idea : you can't go wrong with Debian on them, of course ! :-) They will stay slow (the hardware is slow...) but at least you'll have a true OS on them in place of the original joke, and all in all, for applications where speed isn't a concern (rsnapshot backup server, for example), they are not bad at all. Hih, -- JFS. signature.asc Description: PGP signature
Re: Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote: > * Ian Campbell [2015-11-09 08:37]: > > It might be the same issue as this recent installation report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 > > > > I've not had a chance to dig into what is going on there. Often this > > kind of thing turns out to be an upstream change to the modules > > (different config options, splitting modules into more fine grained > > parts) which requires tweaks to the kernel config, or initramfs-tools > > or to the kernel udebs for the installer. > > There was a report on the QNAP forum about a QNAP no longer booting > after an update. The logs says: > > [8.697480] sdb: sdb1 > [8.702144] sda: sda1 sda2 sda3 > [8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk > [8.713159] sd 0:0:0:0: [sda] Attached SCSI disk > Begin: Loading essential drivers ... modprobe: module of:NocpTCsimple-bus not > found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in > modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep > modprobe: module of:NocpTCsimple-bus not found in modules.dep > modprobe: module platform:reg-dummy not found in modules.dep > done. > Begin: Running /scripts/init-premount ... done. > ... > [ and then the UUID is not found ] > > Any idea what these messages about modules.dep are about? All those modaliases correspond to devices whose drivers are built-in. So it's not surprising that they're not found in modules.dep, and I don't think this has anything to do with the failure. Ben. -- Ben Hutchings If you seem to know what you are doing, you'll be given more to do. signature.asc Description: This is a digitally signed message part
Re: SS4000E install problem
Hello JF I would like a copy of your notes if you find them. I have a couple of SS4000E I would like to do something with! Thanks Paul pmcn...@cameron.net On 11/9/2015 6:51 PM, JF Straeten wrote: Hi Bob, On Mon, Nov 09, 2015 at 08:30:54PM +, Bob Stewart wrote: Hi JF, Did you install directly from initrd.gz/zImage, or did you do an upgrade install from Squeeze? Yes, it was an upgrade from squeeze (and before that from lenny, installed when lenny was testing if I remember good). But lenny was first installed directly with initrd/zImage, loaded from a tftp server. I still have somewhere notes taken during installation, with a mix of a roadmap for the installation, if you are interested, but without warranty six years :-) after the first install (though the core principes haven't changed...). Hih,
Re: SS4000E install problem
Hi Bob, On Mon, Nov 09, 2015 at 08:30:54PM +, Bob Stewart wrote: > Hi JF, > Did you install directly from initrd.gz/zImage, or did you do an > upgrade install from Squeeze? Yes, it was an upgrade from squeeze (and before that from lenny, installed when lenny was testing if I remember good). But lenny was first installed directly with initrd/zImage, loaded from a tftp server. I still have somewhere notes taken during installation, with a mix of a roadmap for the installation, if you are interested, but without warranty six years :-) after the first install (though the core principes haven't changed...). Hih, -- JFS.
Re: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
* Ian Campbell [2015-11-09 08:37]: > It might be the same issue as this recent installation report: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 > > I've not had a chance to dig into what is going on there. Often this > kind of thing turns out to be an upstream change to the modules > (different config options, splitting modules into more fine grained > parts) which requires tweaks to the kernel config, or initramfs-tools > or to the kernel udebs for the installer. There was a report on the QNAP forum about a QNAP no longer booting after an update. The logs says: [8.697480] sdb: sdb1 [8.702144] sda: sda1 sda2 sda3 [8.705613] sd 1:0:0:0: [sdb] Attached SCSI disk [8.713159] sd 0:0:0:0: [sda] Attached SCSI disk Begin: Loading essential drivers ... modprobe: module of:NocpTCsimple-bus not found in modules.dep modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep modprobe: module of:NocpTCsimple-bus not found in modules.dep modprobe: module of:NgpioTCmarvell,orion-gpio not found in modules.dep modprobe: module of:NocpTCsimple-bus not found in modules.dep modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep modprobe: module of:NocpTCsimple-bus not found in modules.dep modprobe: module of:Nsata-phyTCmarvell,mvebu-sata-phy not found in modules.dep modprobe: module of:NocpTCsimple-bus not found in modules.dep modprobe: module platform:reg-dummy not found in modules.dep done. Begin: Running /scripts/init-premount ... done. ... [ and then the UUID is not found ] Any idea what these messages about modules.dep are about? -- Martin Michlmayr http://www.cyrius.com/
Re: SS4000E install problem
* Bob Stewart [2015-11-06 05:55]: > Is there any sort of group/mailing list for those of us who have this running? This mailing list (debian-arm) is the best one. There are some other people running Debian on their SS4000-E (but I'm not one of them, so I cannot answer any questions). > Also, is there a tutorial I could use to create my own archive of > the mirror, just in case it disappears? I believe I have more than > enough available storage. archive.debian.org is an official Debian service and won't go away. -- Martin Michlmayr http://www.cyrius.com/
Re: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
On Mon, Nov 09, 2015 at 07:13:30PM +1300, m...@wiimail.com wrote: > Could you describe a bit of what you had to do on that Seagate? > I guess I could try a few things before going after the cable... Most of my trouble was self-inflicted -- I decided I would re-flash an up-to-date U-Boot as well, and that clobbered the environment settings needed to boot. -- Eric Cooper e c c @ c m u . e d u
arm64, ppc64el, mips64el: please provide ready-to-use VM images
Hello, this is my first email to this list and I am here mainly because Linaro recently launched a "port & enhance" contest to port several free softwares to the arm64 platform. The list is at: http://performance.linaro.org/find/ They also compiled a tutorial, how to, or getting started guide to test things on arm64 using qemu: http://performance.linaro.org/setup/ I've followed the instructions there (and in the linked documentations as well) and have succesfully setup an environment with ruby and irb that seems to be working, altough i've not executed any automated tests (just opened up irb and did a 2+2 test). Since that list from Linaro seems a little outdated (it mentions ruby 1.9.1), and very different from the one on the debian arm64 blockers from last month (https://lists.debian.org/debian-arm/2015/11/msg6.html) i would like to get another view on how things are going and if could help with something. Kind regards, Daniel
Re: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue
On Mon, 2015-11-09 at 15:38 +1300, m...@wiimail.com wrote: > Hi all. > > I have been happily running debian on a Qnap HS-210 for about a year > now. > > It was a sid install onto a USB drive, last updated just before the > jessie release. > So it was running on kernel 3.16+63 and udev 215-9 from around that > time. > > Today I ran the first dist-upgrade after such long time, > and that brought in kernel 4.2+68 and udev 227-2. > > But now it is no longer bringing up the network interface on boot > ups, > so I can't ssh in anymore. It might be the same issue as this recent installation report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804351 I've not had a chance to dig into what is going on there. Often this kind of thing turns out to be an upstream change to the modules (different config options, splitting modules into more fine grained parts) which requires tweaks to the kernel config, or initramfs-tools or to the kernel udebs for the installer. > I am not sure if the problem is the kernel not finding the usb drive, > hence not completing boot, > or perhaps the udev rules changes brought by the newer version screwing > with the net config? > > The log files inside /var/log don't seem to get touched on boot > attempts, so it would seem that the kernel is not finding the USB drive? That would be consistent with #804351 at least. > I've also come across this link: > http://forum.doozan.com/read.php?2,12096 > But I don't really understand FDT or what it all means to my install? This is a third possibility. The version of flash-installer in Stretch onwards should know enough to append a DTB when required, so I think it is less likely. Which version of flash-kernel do you have installed and what is the contents of /proc/hardware (in whatever rescue environment I suppose you are using to check the logs). Ian.
