Re: Fwd: Do others see install failures on DNS-323 to ext2 FS from Debian 7.0 netboot.img?
On Tue, Nov 12, 2013 at 7:10 PM, Martin Michlmayr t...@cyrius.com wrote: I finally had time to look into this issue. I summarized what I found in a bug report: http://bugs.debian.org/729445 What a clear and simple report -- thanks, Martin! (Ext2 seems to be the only linux-native FS available in the installer.) I wonder why you say that. That's something I never understood about the several reports I received from other users about this problem. Why do they use ext2 for the root partition? By default, the installer should use ext3, but for some reason it must be ext2 on the DNS-323. I'm not sure why and I'm not around my ARM devices at the moment to check. But this is definitely another issue since ext2 should *not* be the default for the root partition (only for /boot). Yes. I can only speak for my colleague and myself; we saw only ext2 and several FAT-related choices when we ran d-i and chose to use its partitioning UI. I don't know why ext3 et al. were not on the menu. Of course, d-i is running in 64 MB of RAM in this case. Two possibilities occur to me: 1) the installer is ignoring more memory-intensive partitioning options right away 2) the installer looks at disk size and estimates how much RAM it will need, and then offers partitioning options it can support. A google for Memory allocation failed while setting up superblock shows (with only RAM 192 MB, no swap) some examples of the kind of problem d-i might be seeking to avoid by offering ext2 only. I apologize for speculating without reading the source. The disk I was installing on was 2 TB. When I have time, I shall try the same install on a 250 GB disk and report. I am very grateful for the help, Martin, and for any opinions from the list. -- t...@eastpole.ca East Pole Productions -- 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/calprqqacrienqhqnatq3jct97vp0zjlm+_hraeb0mq_he5_...@mail.gmail.com
Re: Fwd: Do others see install failures on DNS-323 to ext2 FS from Debian 7.0 netboot.img?
* Tai Viinikka t...@eastpole.ca [2013-11-13 10:24]: Yes. I can only speak for my colleague and myself; we saw only ext2 and several FAT-related choices when we ran d-i and chose to use its partitioning UI. I don't know why ext3 et al. were not on the menu. Of course, d-i is running in 64 MB of RAM in this case. Two Thanks for pointing this out. This explains the behaviour you're seeing. Debian installer has a low memory mode (lowmem). In this mode, additional modules are not loaded automatically; this includes the ext3 module. I'll change the instructions to tell users to choose the ext3 manually. Martin, wondering when 64 MB of RAM became low memory... -- 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/20131113190604.gb3...@jirafa.cyrius.com
Re: Fwd: Do others see install failures on DNS-323 to ext2 FS from Debian 7.0 netboot.img?
Hi Tai, * Tai Viinikka t...@eastpole.ca [2013-10-13 08:46]: Summary: the current installer for the DNS-323, using ext2 filesystem, cannot make the system bootable because necessary links are not created in /dev/disk/by-uuid/ I finally had time to look into this issue. I summarized what I found in a bug report: http://bugs.debian.org/729445 I hope someone who is more knowledgeable about this part of the installer will take a look soon. (Ext2 seems to be the only linux-native FS available in the installer.) I wonder why you say that. That's something I never understood about the several reports I received from other users about this problem. Why do they use ext2 for the root partition? By default, the installer should use ext3, but for some reason it must be ext2 on the DNS-323. I'm not sure why and I'm not around my ARM devices at the moment to check. But this is definitely another issue since ext2 should *not* be the default for the root partition (only for /boot). -- 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/20131113001054.gj12...@jirafa.cyrius.com
Fwd: Do others see install failures on DNS-323 to ext2 FS from Debian 7.0 netboot.img?
Martin, and list, I've very grateful for your work on the DNS-323 and your efforts to make an ssh-console installer available. I've also learned a lot from the debian-arm mailing list gurus along the way -- thanks to you, too. Summary: the current installer for the DNS-323, using ext2 filesystem, cannot make the system bootable because necessary links are not created in /dev/disk/by-uuid/ . (Ext2 seems to be the only linux-native FS available in the installer.) A human can fix this, but if the system is simply rebooted, it will require serial console intervention and/or skilled reworking of the boot disk. Are we alone in seeing this? Should I file a bug or re-open an existing bug? - Long Description with logs: I believe I have observed a bug that has bitten the recent ssh-console installer for Debian 7.0 on the D-Link DNS-323. I'm sorry the description is so long but it's complicated for a simple user like me. The alleged bug was previously reported by others in other contexts but not really dealt with as yet: -- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721485 [Paul] -- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701223 [Alexander] ) This description includes work by myself (dwarf in the transcript below) and a pseudonymous associate, (timdau). The failure occurred on my DNS-323 B1 machine and also on one belonging to another colleague. We both started with stock firmwares from D-Link and used the current netboot.img from Martin's DNS-323 page, 6638688 bytes in size. The debian installer runs well (although lacking modern FS options like ext3 and ext4) until it tries to make the new system bootable. Installer is running in : Low memory mode Configuring flash memory to boot the system Installed flash-kernel [ Installer locks up here ^^ ] Tail of /var/log/syslog: [Likely you want to jump to end of log] Oct 8 21:27:48 in-target: update-initramfs: deferring update (trigger activated) Oct 8 21:27:48 in-target: Processing triggers for python-support ... Oct 8 21:27:51 in-target: Processing triggers for ca-certificates ... Oct 8 21:27:51 in-target: Updating certificates in /etc/ssl/certs... Oct 8 21:28:36 in-target: 158 added, 0 removed; done. Oct 8 21:28:36 in-target: Running hooks in /etc/ca-certificates/update.d Oct 8 21:28:36 in-target: done. Oct 8 21:28:37 in-target: Processing triggers for sgml-base ... Oct 8 21:28:37 in-target: Processing triggers for initramfs-tools ... Oct 8 21:28:37 in-target: update-initramfs: Generating /boot/initrd.img-3.2.0-4-orion5x Oct 8 21:29:10 pkgsel: finishing up Oct 8 21:29:11 main-menu[1464]: DEBUG: resolver (libgcc1): package doesn't exist (ignored) Oct 8 21:29:11 main-menu[1464]: INFO: Menu item 'flash-kernel-installer' selected Oct 8 21:29:20 in-target: Reading package lists... Oct 8 21:29:20 in-target: Oct 8 21:29:20 in-target: Building dependency tree... Oct 8 21:29:26 in-target: Oct 8 21:29:26 in-target: Reading state information... Oct 8 21:29:26 in-target: Oct 8 21:29:28 in-target: The following extra packages will be installed: Oct 8 21:29:28 in-target: devio Oct 8 21:29:28 in-target: Suggested packages: Oct 8 21:29:28 in-target: u-boot-tools Oct 8 21:29:28 in-target: The following NEW packages will be installed: Oct 8 21:29:28 in-target: devio flash-kernel Oct 8 21:29:29 in-target: 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Oct 8 21:29:29 in-target: Need to get 42.4 kB of archives. Oct 8 21:29:29 in-target: After this operation, 223 kB of additional disk space will be used. Oct 8 21:29:29 in-target: Get:1 http://ftp.us.debian.org/debian/ wheezy/main devio armel 1.2-1+b1 [16.9 kB] Oct 8 21:29:29 in-target: Get:2 http://ftp.us.debian.org/debian/ wheezy/main flash-kernel armel 3.3 [25.5 kB] Oct 8 21:29:42 in-target: Fetched 42.4 kB in 0s (66.1 kB/s) Oct 8 21:29:43 in-target: Selecting previously unselected package devio. Oct 8 21:29:43 in-target: (Reading database ... Oct 8 21:29:43 in-target: 22721 files and directories currently installed.) Oct 8 21:29:43 in-target: Unpacking devio (from .../devio_1.2-1+b1_armel.deb) ... Oct 8 21:29:44 in-target: Selecting previously unselected package flash-kernel. Oct 8 21:29:44 in-target: Unpacking flash-kernel (from .../flash-kernel_3.3_armel.deb) ... Oct 8 21:29:44 in-target: Processing triggers for man-db ... Oct 8 21:29:56 in-target: Setting up devio (1.2-1+b1) ... Oct 8 21:29:56 in-target: Setting up flash-kernel (3.3) ... Oct 8 21:30:06 in-target: update-initramfs: Generating /boot/initrd.img-3.2.0-4-orion5x Oct 8 21:30:11 in-target: UUID 422805e4-bd52-4ee8-8fce-2abd5079a1ea doesn't exist in /dev/disk/by-uuid Oct 8 21:30:11 in-target: Warning: root device /dev/disk/by-uuid/422805e4-bd52-4ee8-8fce-2abd5079a1ea does not exist Oct 8 21:30:11 in-target: Oct 8 21:30:11 in-target: Press Ctrl-C to abort build, or Enter to continue On my colleague's machine with an apparently identical problem,
Re: Fwd: Do others see install failures on DNS-323 to ext2 FS from Debian 7.0 netboot.img?
* Tai Viinikka t...@eastpole.ca [2013-10-13 08:46]: Are we alone in seeing this? Should I file a bug or re-open an existing bug? No, you're not the only one. I received a number of similar bug reports recently. I'll try to investigate soon. -- 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/20131013140906.gg5...@jirafa.cyrius.com
