Am 2020-06-14 22:54, schrieb g4sra via Dng:
How do you know the mount is failing ?
It's not mounted after mount command.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Am 2020-06-15 05:11, schrieb spiralofhope:
I wonder if there's anything S.M.A.R.T. information can tell you.
There is a spinup time test, and I wonder if perhaps there is SMART
logging within the drive that could reveal a problem with the drive not
spinning up as quickly as it should, and maybe
On Fri, 12 Jun 2020 17:01:14 +0200
"J. Fahrner via Dng" wrote:
> When this disk is active in /etc/fstab the boot process hangs
> forever.
I wonder if there's anything S.M.A.R.T. information can tell you.
There is a spinup time test, and I wonder if perhaps there is SMART
logging within the driv
On Sun, Jun 14, 2020 at 02:30:39PM +0200, d...@d404.nl wrote:
> Which is still quiet high. I would advise to renew the thermal paste on
> your processor. I can recommend Arctic Silver 5 AS5-3.5G Thermal Paste.
> Made a difference of another 20°C on idle on my old i5.
If the system ran cool before
J. Fahrner via Dng wrote:
> I don't see why this parameter is so important. When I read the description,
> this is the delay for scanning usb devices after power up. But as you can see
> in the logs, the device is responding and telling its characteristics. Only
> mounting the filesystem fails
On Sun, 14 Jun 2020 21:49:50 +0200
"J. Fahrner via Dng" wrote:
> > And an earlier suggestion to copy important things to a smaller disk
> > and use that disk, does that probably solve the issue?
>
> A smaller disk is no option, since this is my media server at home.
> It is filled with 66%.
I m
-- snip --
> Only mounting the filesystem fails.
How do you know the mount is failing ?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Am 2020-06-14 21:25, schrieb richard lucassen via Dng:
Ok, I missed that, sorry. Maybe 5 is too low, try 10 or 15 I'd say.
I don't see why this parameter is so important. When I read the
description, this is the delay for scanning usb devices after power up.
But as you can see in the logs, th
On Sun, 14 Jun 2020 20:54:06 +0200
"J. Fahrner" wrote:
> Am 2020-06-14 20:48, schrieb richard lucassen:
> > What happens if you change the content of that script:
> >
> > #!/bin/dash
> > echo 5 > /sys/module/usb_storage/parameters/delay_use
>
> For what reason? I had it in /boot/boot.ini and th
Am 2020-06-14 20:48, schrieb richard lucassen:
What happens if you change the content of that script:
#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use
For what reason? I had it in /boot/boot.ini and that worked. I looked up
/sys/module/usb_storage/parameters/delay_use and it
On Sun, 14 Jun 2020 20:31:22 +0200
"J. Fahrner via Dng" wrote:
> Am 2020-06-14 20:07, schrieb d...@d404.nl:
> > It is a kernel parameter not a module parameter. You have to add it
> > to your kernel boot line.
>
> Ok, I found out how to do that. It's in /boot/boot.ini
> But that made no differen
Am 2020-06-14 20:07, schrieb d...@d404.nl:
It is a kernel parameter not a module parameter. You have to add it to
your kernel boot line.
Ok, I found out how to do that. It's in /boot/boot.ini
But that made no difference to my problem.
This is my current setup:
/etc/fstab has the mount option n
On Sun, Jun 14, 2020 at 08:07:59PM +0200, d...@d404.nl wrote:
> On 14-06-2020 20:00, J. Fahrner via Dng wrote:
> > Am 2020-06-14 19:51, schrieb Tomasz Torcz:
> >> Try files in /sys/module/usb_storage/parameters
> >> Or you can put in kernel command line: usb_storage.parameter=…
> >> as described
On 14-06-2020 20:00, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:51, schrieb Tomasz Torcz:
>> Try files in /sys/module/usb_storage/parameters
>> Or you can put in kernel command line: usb_storage.parameter=…
>> as described at
>> https://www.kernel.org/doc/html/latest/admin-guide/kernel-paramete
Am 2020-06-14 19:51, schrieb Tomasz Torcz:
Try files in /sys/module/usb_storage/parameters
Or you can put in kernel command line: usb_storage.parameter=…
as described at
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
Something is wrong her:
root@Odroid2:~# modprobe
On 14-06-2020 19:46, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:39, schrieb d...@d404.nl:
>> Most likely the usb_storage module is compiled in the kernel.
>
> How can I set its parameters in this case?
> sysctl -a lists nothing about storage or usb.
From what i am able to find the kernel param
On Sun, Jun 14, 2020 at 07:46:57PM +0200, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:39, schrieb d...@d404.nl:
> > Most likely the usb_storage module is compiled in the kernel.
>
> How can I set its parameters in this case?
Try files in /sys/module/usb_storage/parameters
Or you can put in ker
Am 2020-06-14 19:39, schrieb d...@d404.nl:
Most likely the usb_storage module is compiled in the kernel.
How can I set its parameters in this case?
sysctl -a lists nothing about storage or usb.
___
Dng mailing list
Dng@lists.dyne.org
https://mailingli
On 14-06-2020 19:36, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:30, schrieb richard lucassen:
>> What tells "modinfo g_mass_storage"?
>
> $ sudo modinfo g_mass_storage
> filename:
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
> license: GPL
> author: Mic
Am 2020-06-14 19:30, schrieb richard lucassen:
What tells "modinfo g_mass_storage"?
$ sudo modinfo g_mass_storage
filename:
/lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
license:GPL
author: Michal Nazarewicz
description:Mass Storage Gadget
depends
On Sun, 14 Jun 2020 19:11:38 +0200
"J. Fahrner via Dng" wrote:
> Am 2020-06-14 19:07, schrieb J. Fahrner via Dng:
> > modinfo: ERROR: Module usb_storage not found.
>
> Maybe they have their own drivers for usb?
>
> # find /lib/modules/3.16.82+/kernel/drivers -name '*storage*'
> /lib/modules/3.1
Am 2020-06-14 19:07, schrieb J. Fahrner via Dng:
modinfo: ERROR: Module usb_storage not found.
Maybe they have their own drivers for usb?
# find /lib/modules/3.16.82+/kernel/drivers -name '*storage*'
/lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
/lib/modules/3.16.82+/kernel
Am 2020-06-14 19:05, schrieb richard lucassen:
That's rather strange. From "modinfo usb_storage":
parm: delay_use:seconds to delay before using a new device (uint)
And what happens if you load the module in advance?:
echo "usb_storage" >> /etc/modules
modinfo: ERROR: Module usb_storage not f
On Sun, 14 Jun 2020 18:38:48 +0200
"J. Fahrner via Dng" wrote:
> Am 2020-06-14 17:25, schrieb richard lucassen via Dng:
> > echo "options usb_storage delay_use=5" >
> > /etc/modprobe.d/usb_storage.conf
>
> seems not to work.
>
> After boot:
>
> cat /sys/module/usb_storage/parameters/delay_use
Am 2020-06-14 17:25, schrieb richard lucassen via Dng:
echo "options usb_storage delay_use=5" >
/etc/modprobe.d/usb_storage.conf
seems not to work.
After boot:
cat /sys/module/usb_storage/parameters/delay_use
1
___
Dng mailing list
Dng@lists.dyne.or
On Sun, 14 Jun 2020 17:24:01 +0200
richard lucassen via Dng wrote:
Oops:
echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf
must be:
echo "options usb_storage delay_use=5" > /etc/modprobe.d/usb_storage.conf
--
richard lucassen
https://contact.xaq.nl/
On Sun, 14 Jun 2020 14:12:21 +0200
"J. Fahrner via Dng" wrote:
> Very big device. Trying to use READ CAPACITY
You may try this:
echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf
https://bbs.archlinux.org/viewtopic.php?id=125831
R.
--
richard lucassen
https://contact.xa
On 6/14/20 4:44 PM, J. Fahrner via Dng wrote:
> Am 2020-06-14 15:09, schrieb Dr. Nikolaus Klepp:
>> Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
>> J. Fahrner via Dng scripsit:
>>> [ 22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
>>> [ 1145.246051] EXT4-fs (sda1): mounted filesystem with order
Am 2020-06-14 15:09, schrieb Dr. Nikolaus Klepp:
Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
J. Fahrner via Dng scripsit:
[ 22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1145.246051] EXT4-fs (sda1): mounted filesystem with ordered data
I see this on RPi, too, just the delay is smaller (
Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
J. Fahrner via Dng scripsit:
> [ 22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 1145.246051] EXT4-fs (sda1): mounted filesystem with ordered data
I see this on RPi, too, just the delay is smaller (~ 30 secs) - but that's
anoying, too.
Nik
--
On 14-06-2020 14:14, Lars Noodén via Dng wrote:
> On 6/14/20 2:03 PM, d...@d404.nl wrote:
>> On 14-06-2020 12:53, Lars Noodén via Dng wrote:
>>> On 6/14/20 1:47 PM, d...@d404.nl wrote:
On 14-06-2020 12:38, Lars Noodén via Dng wrote:
> An upgrade to Beowulf went very smoothly but since upgr
On 6/14/20 2:03 PM, d...@d404.nl wrote:
> On 14-06-2020 12:53, Lars Noodén via Dng wrote:
>> On 6/14/20 1:47 PM, d...@d404.nl wrote:
>>> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
An upgrade to Beowulf went very smoothly but since upgrading I notice
that the fans are always running.
Am 2020-06-14 13:32, schrieb richard lucassen via Dng:
It's weird. What does "dmesg" tell?
dmesg > /tmp/dmesg
and look if there are any messages there
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuac
Am 2020-06-14 13:23, schrieb Dr. Nikolaus Klepp:
Are you 100% absolutely sure your board is not stuck at the bootloader
stage before the kernel is started?
Yes. It responds to ping, so network is running.
___
Dng mailing list
Dng@lists.dyne.org
https:
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner" wrote:
> But if I do it interactively with "sudo mount /hdd" the drive gets
> mounted and the waiting daemons are started.
>
> I'm very confused...
When you mount it interactively the path is different and maybe it's
waiting for some input.
Try
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner" wrote:
> But if I do it interactively with "sudo mount /hdd" the drive gets
> mounted and the waiting daemons are started.
>
> I'm very confused...
It's weird. What does "dmesg" tell?
dmesg > /tmp/dmesg
and look if there are any messages there
Anno domini 2020 Sun, 14 Jun 13:03:13 +0200
J. Fahrner via Dng scripsit:
> Am 2020-06-14 10:11, schrieb richard lucassen:
> > Did you format the disk with a newer system than the system you run it
> > on? So, I wonder what happens if you remove the huge_file option
>
> I don't remember on which s
On Sun, Jun 14, 2020 at 08:46:48AM +0200, Riccardo Mottola via Dng wrote:
> Hi,
>
> On 6/12/20 9:21 PM, Steve Litt wrote:
> > > Maybe try ;https://make-linux-fast-again.com/ kerneloptions to
> > > disable all spectre and meltdown stuff
> > I hope you mean the preceding as a diagnostic test and n
On 14-06-2020 12:53, Lars Noodén via Dng wrote:
> On 6/14/20 1:47 PM, d...@d404.nl wrote:
>> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
>>> An upgrade to Beowulf went very smoothly but since upgrading I notice
>>> that the fans are always running. Although the air temperature is about
>>> 25°
Am 2020-06-14 10:11, schrieb richard lucassen:
Did you format the disk with a newer system than the system you run it
on? So, I wonder what happens if you remove the huge_file option
I don't remember on which system I formatted that drive.
After playing around the problem is very strange. It's
On 6/14/20 1:47 PM, d...@d404.nl wrote:
> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
>> An upgrade to Beowulf went very smoothly but since upgrading I notice
>> that the fans are always running. Although the air temperature is about
>> 25°C the cores seem to run much hotter than necessary, pu
On 14-06-2020 12:38, Lars Noodén via Dng wrote:
> An upgrade to Beowulf went very smoothly but since upgrading I notice
> that the fans are always running. Although the air temperature is about
> 25°C the cores seem to run much hotter than necessary, pushing 70°C or
> hotter. The system is not re
On an "apt-get update" I get the following errors:
Err:10 http://pkgmaster.devuan.org/merged beowulf/main armhf Contents
(deb)
Hash Sum mismatch
Hashes of expected file:
- Filesize:31681725 [weak]
-
SHA256:04dda4a3166f89d6cd274bd662e29997a9c59c0015e3a29537c5918ff35edd01
Hashes of
An upgrade to Beowulf went very smoothly but since upgrading I notice
that the fans are always running. Although the air temperature is about
25°C the cores seem to run much hotter than necessary, pushing 70°C or
hotter. The system is not really under any load. What should I be
looking at to mak
> "fsmithred" == fsmithred via Dng writes:
> On 6/12/20 10:05 AM, David Kuehling via Dng wrote:
>>
[..]
>>
>> - none of the alsa sound driver modules is loaded during boot, so I
>> end up with a Desktop that does not support audio
>>
>> - the amdgpu module is not loaded, so not 3-D acceler
On Sun, 14 Jun 2020 08:21:51 +0200
"J. Fahrner via Dng" wrote:
> Am 2020-06-13 22:10, schrieb richard lucassen via Dng:
> > 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 runlev
46 matches
Mail list logo
