Re: [DNG] Preparation for upgrade to beowulf
On Fri, Jun 12, 2020 at 04:41:22PM -0700, Steve Schlaifer wrote: > On Fri, 12 Jun 2020 15:58:27 -0400 > Hendrik Boom wrote: > > > It's getting to be time for me to upgrade my ascii server to beowulf. > > > > But I have some worries, having heard people have had problems with > > said upgrade. > > > > What I absolutely need after the upgrade is a text console and > > network cnnectivity. Because this is my link to the rest of the > > world, and if something goes wrong I won't be able to ask for help. > > Since i'm in coronavirus lockdown, a trip to a local coffeeshop's > > wifi isn't really an option. (they're pretty closed down anyway) > > > > So. What information, code, binaries, documentation should I be > > collecting ahead of time in case it doesn't go smoothly? I don't > > care that much about interactive graphics, desktop environments, and > > the like. If I get a text console with root access, internet > > connection and bridging and masquerading to my LAN, that's enough. > > > > My upgrade went pretty well with a minor problem with permissions > on /tmp which would allow root to log on but not me. Adding o+t to the > permissions took care of that. > > How about a disk image using dd to a thumb drive or equivalent. If > things go really badly, you could then dd that thumb drive back to your > hard drive and start over. If I can boot enough to do dd. I'd need a 2 terabyte thumb drive. Sounds like I need heavier metal, but I should be able to find another heavy-duty backup drive. I guess the thing to do is to make a rescue disk (possibly a live Devuan USB) or the installer an to use that. Or maybe install a small Linux system for recovering the one that works. Having a spare emergency Linux system on disk is probably a good idea anyway. I think I have enough space for that. It will have to understand local text console, IP routing, access to two ethernet intefacing, maasqierading, PPPOE, and software RAID. That's close to a minimal installation, with some configuration copied over from the current working system. Sounds doable. -- hendrik > > > Yes, I've heard of people's woes with things like ehternet device > > renaming and the like. I need to know what to do if this happens to > > me. > > > > The machine is an old AMD-64 box; it's been running for over a > > decade. I'm not entirely sure of the USB subsystem; and its floppy > > drive is dead. The lase Debian on it was the one before jassie; it > > has been updated to Devuan's jessie and has been running Devuan ever > > since. > > > > -- hendrik > > > > > > > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > > -- > --Steve > > I programmed three days > and heard no human voices > but the hard disk sang. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 21:09:06 +0200 "J. Fahrner" wrote: > > No, but I asked you why not create the root filesystem on that disk. > > If "mount -a" does not work in runlevel 2, why should it work in boot > stage 1? I have no idea. But mountall is in runlevel S, not 2. What if you mount it explicitely in a temporary script called /etc/rcS.d/99mount.sh ? That is before runlevel 2 starts. -- richard lucassen https://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 21:05, schrieb richard lucassen: No, but I asked you why not create the root filesystem on that disk. If "mount -a" does not work in runlevel 2, why should it work in boot stage 1? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 21:07:37 +0200 richard lucassen via Dng wrote: > No, maybe it has got something to do with these "big disk" messages. > Wouldn't it be an idea to copy a part of that dist to a "not such a > big disk" and see what happens? s/dist/disk/ -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 20:28:03 +0200 "J. Fahrner via Dng" wrote: > Am 2020-06-13 20:18, schrieb richard lucassen via Dng: > > That was the "rootwait" parameter as I said somewhere. Used for USB > > and MMC disks. > > "The rootwait kernel parameter only affects the first stage of boot, > while the kernel is waiting for its initial root device" > > https://stackoverflow.com/questions/14806294/linux-kernel-parameter-rootwait-being-ignored#14806347 > > That has nothing to do with my problem. No, maybe it has got something to do with these "big disk" messages. Wouldn't it be an idea to copy a part of that dist to a "not such a big disk" and see what happens? -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 20:28:03 +0200 "J. Fahrner via Dng" wrote: > "The rootwait kernel parameter only affects the first stage of boot, > while the kernel is waiting for its initial root device" > > https://stackoverflow.com/questions/14806294/linux-kernel-parameter-rootwait-being-ignored#14806347 > > That has nothing to do with my problem. No, but I asked you why not create the root filesystem on that disk. I have several Orange Pi's using a USB disk as root device. That works perfectly well. Also on PCEngine's Apu, see its lilo config: image=/boot/vmlinuz-4.9.223 label=4.9.223 read-only append="rootwait root=/dev/sda3 console=ttyS0,115200n8" R. -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 20:18, schrieb richard lucassen via Dng: That was the "rootwait" parameter as I said somewhere. Used for USB and MMC disks. "The rootwait kernel parameter only affects the first stage of boot, while the kernel is waiting for its initial root device" https://stackoverflow.com/questions/14806294/linux-kernel-parameter-rootwait-being-ignored#14806347 That has nothing to do with my problem. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 16:50:29 +0200 Didier Kryn wrote: > I had a problem around 15 years ago booting a Powerpc SBC with > rootfs on a USB disk and without initramfs. around 15 years ago. Even > though the disk was powered on its own, it didn't start spinning > before the driver started it. I solved it by adding a delay to the > kernel before mounting the rootfs - there was a parameter for that. > > Maybe it's just enough to add such a delay before trying to mount > your USB disk. That was the "rootwait" parameter as I said somewhere. Used for USB and MMC disks. -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !
Patrick Erdmann [13.06.2020 12:24]: > My test case is compiling ArcticFox, thus something in the realm of > Firefox: lots of compiler activity, make, disk access, make and python. > But, of course, predominant factor is compilation and linking. > > With ascii, I was consistently (= not just one build) doing a clean > build in about 31 minutes! Quite fast for this small beast and I was happy. > > With beowulf, this number is consistently about 41 minutes. Do you compile ArcticFox with the same compiler in both cases? GCC gets slower for each release, it seems... -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Le 13/06/2020 à 10:53, J. Fahrner via Dng a écrit : > Am 2020-06-13 10:31, schrieb richard lucassen: >> The nofail means that it wil mount automatically, but if the disk >> is absent it won't give errors. But it does not wait for the device! > > The disk has itś own power supply and is always connected. I think > there is something missing at the boot stage (driver?). > >> ok, I assume it's u-boot? In that case you can easily try to boot from >> another disk. But apparently you do not have access to the device? > > I don't know the boot process. I think it's like a Raspberry Pi. There > is a little FAT partion and a EXT4 root partition on emmc. Since it is > headless, I only can access it through ssh. When it does not boot I > have to open it, remove the emmc card, insert it into an adapter and > reverse my changes on pc.This is very elaborate. So I need a > straightforward method to isolate the problem. I had a problem around 15 years ago booting a Powerpc SBC with rootfs on a USB disk and without initramfs. around 15 years ago. Even though the disk was powered on its own, it didn't start spinning before the driver started it. I solved it by adding a delay to the kernel before mounting the rootfs - there was a parameter for that. Maybe it's just enough to add such a delay before trying to mount your USB disk. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On June 13, 2020 3:00:37 PM GMT+02:00, "J. Fahrner via Dng" wrote: > AFTER boot a "mount -a" waits until the disk is ready and mounts it > without any failure. I don't see why this should not be the same during > boot. I suspect it has more to do with disc size, see the warnings in > dmesg. A (somewhat hackish) workaround might be to try with the "_netdev" option in the fstab!? libre Grüße, Florian -- [message sent otg] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 14:19, schrieb Tito via Dng: maybe rather than trying to mount the disk earlier, you could try to spin it up so that it mounts when mountall is run. AFTER boot a "mount -a" waits until the disk is ready and mounts it without any failure. I don't see why this should not be the same during boot. I suspect it has more to do with disc size, see the warnings in dmesg. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On 6/13/20 9:49 AM, richard lucassen via Dng wrote: > On Sat, 13 Jun 2020 08:52:18 +0200 > "J. Fahrner via Dng" wrote: > >> Am 2020-06-13 08:25, schrieb J. Fahrner via Dng: >>> nofail was a good hint. Now the system boots, but the usb disk is >>> still not mounted. "mount -a" mounts it without errors after boot. >> >> What is the best way to run "mount -a" before any initscripts in >> runlevel 2? >> >> There is a script /etc/init.d/mountall.sh, but this only runs in >> runlevel S. Whats the purpose of this script? > > /etc/rcS.d/ contains scripts that run before any other runlevel. That's > why "mountall" is there. > >> The script provides "mountall". Can I make daemons that need the >> external disk dependend on "mountall". > > What is on that disk? Why not make that disk the root filesystem and > pass "rootwait" to the kernel? > > Anyhow, you may try this: > > > #/bin/dash > > ### BEGIN INIT INFO > # Provides: disk > # Required-Start: > # Required-Stop: > # Default-Start: S > # Default-Stop: > # Short-Description: prepare disk at boot time > ### END INIT INFO > > case $1 in > > start) > # Edit this: > /bin/mount /dev/disk /mnt/mountpoint > ;; > > esac > > > > put this in /etc/init.d/mount-disk.sh > run: update-rc.d mount-disk.sh defaults > > and check if there is a link in /etc/rcS.d/ called S00mount-disk.sh > > Just a guess. Not tested of course. > > My 2cts, > > R. > Hi, maybe rather than trying to mount the disk earlier, you could try to spin it up so that it mounts when mountall is run. From https://unix.stackexchange.com/questions/10930/what-command-do-i-use-to-spin-up-a-power-up-in-standby-drive: Drives supporting the "Power-up in Standby" feature are supposed to spin up as soon as they get a command that requires reading the disk. like dd if=/dev/hdX of=/dev/null count=512 #/bin/dash ### BEGIN INIT INFO # Provides: disk # Required-Start: # Required-Stop: # Default-Start: S # Default-Stop: # Short-Description: prepare disk at boot time ### END INIT INFO case $1 in start) # Edit this: /bin/dd if=/dev/disk of=/dev/null count=512 ;; esac eventually you could make this an udev/eudev rule to be run when the drive is detected. Untested, just my 2 cents, Tito ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !
On 12.06.20 13:02, d...@d404.nl wrote: > On 12-06-2020 12:49, Riccardo Mottola via Dng wrote: >> Hi all! >> >> I just upgraded from ascii to beowulf a pretty decent laptop, equipped >> with a core i7 and 8GB of RAM. >> >> I upgraded everything in place: so same desktop environment, same >> applications, same hard disk... just "apt-get dist-upgrade" essentially. >> >> I even kept gcc6 because I had it before and I need it. >> >> My test case is compiling ArcticFox, thus something in the realm of >> Firefox: lots of compiler activity, make, disk access, make and python. >> But, of course, predominant factor is compilation and linking. >> >> With ascii, I was consistently (= not just one build) doing a clean >> build in about 31 minutes! Quite fast for this small beast and I was happy. >> >> With beowulf, this number is consistently about 41 minutes. >> >> I say this is a very significant slowdown! Can I gain some speed back? >> Some setting? some spectre/meltdown mitigation? Having latest ascii, I >> think I had at least some of the backports. >> >> >> I am wary thus updating to beowulf on slower machines. >> >> Any ideas? >> Just to be sure, try this line as kernel parameters: noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off >> >> Riccardo >> ___ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > According Geekbench > https://browser.geekbench.com/v4/cpu/compare/12415873?baseline=12415673 > removing mitigation mainly makes a difference on single core performance. > > But i recently did see some Intel firmware update passing at my system. > So maybe Ascii has not yet received the same updates as Beowulf. > > Grtz. > > Nick > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Friday 12 June 2020 at 17:01:14, J. Fahrner via Dng wrote: > I'm running Devuan Beowulf on an Odroid C2 mini computer. > I cannot attach a monitor because I have no suitable cable. > Any ideas how to debug this problem? I think my initial approach would be to just buy an HDMI cable - especially given the inconvenience of taking the SD card out, moutning on another machine, adjusting, replacing, and retrying... Antony. -- I want to build a machine that will be proud of me. - Danny Hillis, creator of The Connection Machine Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On 13-06-2020 10:53, J. Fahrner via Dng wrote: > Am 2020-06-13 10:31, schrieb richard lucassen: >> The nofail means that it wil mount automatically, but if the disk >> is absent it won't give errors. But it does not wait for the device! > > The disk has itś own power supply and is always connected. I think > there is something missing at the boot stage (driver?). > >> ok, I assume it's u-boot? In that case you can easily try to boot from >> another disk. But apparently you do not have access to the device? > > I don't know the boot process. I think it's like a Raspberry Pi. There > is a little FAT partion and a EXT4 root partition on emmc. Since it is > headless, I only can access it through ssh. When it does not boot I > have to open it, remove the emmc card, insert it into an adapter and > reverse my changes on pc.This is very elaborate. So I need a > straightforward method to isolate the problem. > ___ I did have a similar problem with a Raspberry Pi caused by fsck taking to long to end. If you can add a keyboard giving a CTL D it maybe continues. Because i only do have data on it I entered a mount in rc.local. But maybe if you fsck the drive on another system? Grtz. Nick signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Anno domini 2020 Sat, 13 Jun 10:53:51 +0200 J. Fahrner via Dng scripsit: > Am 2020-06-13 10:31, schrieb richard lucassen: > > The nofail means that it wil mount automatically, but if the disk > > is absent it won't give errors. But it does not wait for the device! > > The disk has itś own power supply and is always connected. I think there > is something missing at the boot stage (driver?). > > > ok, I assume it's u-boot? In that case you can easily try to boot from > > another disk. But apparently you do not have access to the device? > > I don't know the boot process. I think it's like a Raspberry Pi. There > is a little FAT partion and a EXT4 root partition on emmc. Since it is > headless, I only can access it through ssh. When it does not boot I have > to open it, remove the emmc card, insert it into an adapter and reverse > my changes on pc.This is very elaborate. So I need a straightforward > method to isolate the problem. Don't you have access to a serial port on the device so that you can observe the boot process? Maybe it's stuck at the bootloader stage. Nik > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 10:31, schrieb richard lucassen: The nofail means that it wil mount automatically, but if the disk is absent it won't give errors. But it does not wait for the device! The disk has itś own power supply and is always connected. I think there is something missing at the boot stage (driver?). ok, I assume it's u-boot? In that case you can easily try to boot from another disk. But apparently you do not have access to the device? I don't know the boot process. I think it's like a Raspberry Pi. There is a little FAT partion and a EXT4 root partition on emmc. Since it is headless, I only can access it through ssh. When it does not boot I have to open it, remove the emmc card, insert it into an adapter and reverse my changes on pc.This is very elaborate. So I need a straightforward method to isolate the problem. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 10:20:46 +0200 "J. Fahrner via Dng" wrote: > Thats exactly what I'm expecting, waiting indefinitely. The same as > mounting in fstab without nofail option. The nofail means that it wil mount automatically, but if the disk is absent it won't give errors. But it does not wait for the device! > I can't experiment here. If it does not boot I have to remove the > emmc card and undo the change on my pc. ok, I assume it's u-boot? In that case you can easily try to boot from another disk. But apparently you do not have access to the device? -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 10:05, schrieb richard lucassen via Dng: That is why there is a rootwait option: rootwait[KNL] Wait (indefinitely) for root device to show up. Useful for devices that are detected asynchronously (e.g. USB and MMC devices). Thats exactly what I'm expecting, waiting indefinitely. The same as mounting in fstab without nofail option. I can't experiment here. If it does not boot I have to remove the emmc card and undo the change on my pc. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 09:55:54 +0200 "J. Fahrner" wrote: > Am 2020-06-13 09:49, schrieb richard lucassen: > > What is on that disk? Why not make that disk the root filesystem and > > pass "rootwait" to the kernel? > > I'm afraid that won't work either. If there are problems mounting the > disk at this early stage, even the root filesystem will not mount. That is why there is a rootwait option: rootwait[KNL] Wait (indefinitely) for root device to show up. Useful for devices that are detected asynchronously (e.g. USB and MMC devices). It waits for the USB HDD to spin up. R. -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 09:49, schrieb richard lucassen: What is on that disk? Why not make that disk the root filesystem and pass "rootwait" to the kernel? I'm afraid that won't work either. If there are problems mounting the disk at this early stage, even the root filesystem will not mount. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
On Sat, 13 Jun 2020 08:52:18 +0200 "J. Fahrner via Dng" wrote: > Am 2020-06-13 08:25, schrieb J. Fahrner via Dng: > > nofail was a good hint. Now the system boots, but the usb disk is > > still not mounted. "mount -a" mounts it without errors after boot. > > What is the best way to run "mount -a" before any initscripts in > runlevel 2? > > There is a script /etc/init.d/mountall.sh, but this only runs in > runlevel S. Whats the purpose of this script? /etc/rcS.d/ contains scripts that run before any other runlevel. That's why "mountall" is there. > The script provides "mountall". Can I make daemons that need the > external disk dependend on "mountall". What is on that disk? Why not make that disk the root filesystem and pass "rootwait" to the kernel? Anyhow, you may try this: #/bin/dash ### BEGIN INIT INFO # Provides: disk # Required-Start: # Required-Stop: # Default-Start: S # Default-Stop: # Short-Description: prepare disk at boot time ### END INIT INFO case $1 in start) # Edit this: /bin/mount /dev/disk /mnt/mountpoint ;; esac put this in /etc/init.d/mount-disk.sh run: update-rc.d mount-disk.sh defaults and check if there is a link in /etc/rcS.d/ called S00mount-disk.sh Just a guess. Not tested of course. My 2cts, R. -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Le 13/06/2020 à 09:31, J. Fahrner via Dng a écrit : > Am 2020-06-13 09:24, schrieb Didier Kryn: >> AFAIU defaults is a placeholder for when there's no option to pass. >> Therefore, if you specify nofail or noauto, defaults isn't needed. > > According to the man page of mount: > > defaults > Use the default options: rw, suid, dev, exec, auto, > nouser, and async. > > So defaults is only a shortcut for rw,suid,dev,exec,auto,nouser,async. This raises the question of the very meaning of the word "default" (~: Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 09:24, schrieb Didier Kryn: AFAIU defaults is a placeholder for when there's no option to pass. Therefore, if you specify nofail or noauto, defaults isn't needed. According to the man page of mount: defaults Use the default options: rw, suid, dev, exec, auto, nouser, and async. So defaults is only a shortcut for rw,suid,dev,exec,auto,nouser,async. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Le 12/06/2020 à 20:25, richard lucassen via Dng a écrit : > On Fri, 12 Jun 2020 17:01:14 +0200 > "J. Fahrner via Dng" wrote: > >> Any ideas how to debug this problem? >> >> This is the fstab entry: >> >> LABEL=Elements /hdd ext4 defaults 0 2 > Try to add "nofail" or "noauto": > > LABEL=Elements /hdd ext4 defaults,nofail 0 2 > > LABEL=Elements /hdd ext4 defaults,noauto 0 2 > > Just to see if it comes up. > > Just my 2 cts, > > R. > AFAIU defaults is a placeholder for when there's no option to pass. Therefore, if you specify nofail or noauto, defaults isn't needed. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-13 08:25, schrieb J. Fahrner via Dng: nofail was a good hint. Now the system boots, but the usb disk is still not mounted. "mount -a" mounts it without errors after boot. What is the best way to run "mount -a" before any initscripts in runlevel 2? There is a script /etc/init.d/mountall.sh, but this only runs in runlevel S. Whats the purpose of this script? The script provides "mountall". Can I make daemons that need the external disk dependend on "mountall". ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Boot hangs with usb disk active in fstab
Am 2020-06-12 20:25, schrieb richard lucassen: Try to add "nofail" or "noauto": nofail was a good hint. Now the system boots, but the usb disk is still not mounted. "mount -a" mounts it without errors after boot. I see no errors in /var/log/boot and dmesg. The only messages concerning this drive: [4.153932] scsi 0:0:0:0: Direct-Access WD Elements 25A3 1021 PQ: 0 ANSI: 6 [4.159536] sd 0:0:0:0: [sda] Spinning up disk... [4.161466] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 22.522458] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 22.524863] sd 0:0:0:0: [sda] 19532808192 512-byte logical blocks: (10.0 TB/9.09 TiB) [ 22.532067] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 22.538598] sd 0:0:0:0: [sda] Write Protect is off [ 22.541988] sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08 [ 22.542724] sd 0:0:0:0: [sda] No Caching mode page found [ 22.547320] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 22.554350] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 22.983388] sda: sda1 [ 22.984576] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 22.989231] sd 0:0:0:0: [sda] Attached SCSI disk ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
