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.
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
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
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
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
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"
>
>
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"
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
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
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
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.
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
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
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
>>
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 -
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
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
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
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
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
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
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.
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
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
>
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,
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
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
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
28 matches
Mail list logo
