* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
@ 2019-07-25 16:14 ` voidlinux-github
2019-07-25 16:49 ` voidlinux-github
` (16 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 16:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
New comment by zdykstra on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515108273
Comment:
What's your /proc/cmdline value, and what filesystem are you using?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
2019-07-25 16:14 ` voidlinux-github
@ 2019-07-25 16:49 ` voidlinux-github
2019-07-25 17:04 ` voidlinux-github
` (15 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 16:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515120700
Comment:
`[root@local ~]# /proc/cmdline`
```
BOOT_IMAGE=/boot/vmlinuz-5.0.21_1 root=UUID=bf9295b9-21f1c-4cd9-acef-44faeee4cc82 ro loglevel=4 slub_debug=P page_poison=1
```
`[root@local ~]# df -Th`
```
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 3.9G 756K 3.9G 1% /run
/dev/sdf3 ext4 30G 2.0G 27G 8% /
cgroup tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sdf2 vfat 1022M 148K 1022M 1% /boot/efi
/dev/sdf4 ext4 84G 57M 84G 1% /home
tmpfs tmpfs 3.9G 0 3.9G 0% /tmp
```
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
2019-07-25 16:14 ` voidlinux-github
2019-07-25 16:49 ` voidlinux-github
@ 2019-07-25 17:04 ` voidlinux-github
2019-07-25 17:19 ` voidlinux-github
` (14 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 17:04 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515126498
Comment:
After updating system packages, TTY shows 6 entries of `scandir: No such file or directory` besides dracut message.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (2 preceding siblings ...)
2019-07-25 17:04 ` voidlinux-github
@ 2019-07-25 17:19 ` voidlinux-github
2019-07-25 17:34 ` voidlinux-github
` (13 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 17:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515126498
Comment:
After updating system packages, TTY shows 6 entries of `scandir: No such file or directory` in the beggining and after `=> Setting up keymap to 'us'` besides dracut message.
Has something gone horribly wrong with my installation?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (3 preceding siblings ...)
2019-07-25 17:19 ` voidlinux-github
@ 2019-07-25 17:34 ` voidlinux-github
2019-07-25 17:51 ` voidlinux-github
` (12 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 17:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515139319
Comment:
Run `xbps-pkgdb -a` to see if there are some missing files, links or hashsum mismatches.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (4 preceding siblings ...)
2019-07-25 17:34 ` voidlinux-github
@ 2019-07-25 17:51 ` voidlinux-github
2019-07-25 17:54 ` voidlinux-github
` (11 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 17:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515146301
Comment:
Nope. Nothing shows.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (5 preceding siblings ...)
2019-07-25 17:51 ` voidlinux-github
@ 2019-07-25 17:54 ` voidlinux-github
2019-07-25 18:25 ` voidlinux-github
` (10 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 17:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 211 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515146301
Comment:
Nope. Nothing shows.
I've also tried `xbps-reconfigure -f -a`.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (6 preceding siblings ...)
2019-07-25 17:54 ` voidlinux-github
@ 2019-07-25 18:25 ` voidlinux-github
2019-07-26 20:59 ` voidlinux-github
` (9 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-25 18:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515120700
Comment:
`[root@local ~]# vim /proc/cmdline`
```
BOOT_IMAGE=/boot/vmlinuz-5.0.21_1 root=UUID=bf9295b9-21f1c-4cd9-acef-44faeee4cc82 ro loglevel=4 slub_debug=P page_poison=1
```
`[root@local ~]# df -Th`
```
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 3.9G 756K 3.9G 1% /run
/dev/sdf3 ext4 30G 2.0G 27G 8% /
cgroup tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sdf2 vfat 1022M 148K 1022M 1% /boot/efi
/dev/sdf4 ext4 84G 57M 84G 1% /home
tmpfs tmpfs 3.9G 0 3.9G 0% /tmp
```
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (7 preceding siblings ...)
2019-07-25 18:25 ` voidlinux-github
@ 2019-07-26 20:59 ` voidlinux-github
2019-07-26 21:22 ` voidlinux-github
` (8 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-26 20:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515597765
Comment:
Following [this guide](https://wiki.voidlinux.org/Install_Void_Linux_onto_a_USB_Stick) I've installed another Void system into USB stick. `scandir` and `dracut` error messages still persist. Maybe it somehow connected that dracut uses `/proc/self/mountinfo`?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (8 preceding siblings ...)
2019-07-26 20:59 ` voidlinux-github
@ 2019-07-26 21:22 ` voidlinux-github
2021-02-03 15:16 ` foopub
` (7 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: voidlinux-github @ 2019-07-26 21:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
New comment by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-515597765
Comment:
Following [this guide](https://wiki.voidlinux.org/Install_Void_Linux_onto_a_USB_Stick) I've installed another Void system into USB stick. `scandir` and `dracut` error messages still persist. Maybe it somehow connected that dracut uses `/proc/self/mountinfo`?
Don't know about `scandir` messages tho.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (9 preceding siblings ...)
2019-07-26 21:22 ` voidlinux-github
@ 2021-02-03 15:16 ` foopub
2021-02-03 15:50 ` foopub
` (6 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: foopub @ 2021-02-03 15:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772584406
Comment:
I realise this is a dracut issue, hence not the best place to bring it up but they've been sleeping on the bug for a while.
First of all, why not stat? Seems way more reasonable than the spaghetti ls parse:
`(stat "$resume" -c %t:%T > /sys/power/resume)>/.resume`
Surely I'm missing something?? Putting just `stat "$resume" -c %t:%T` in resume.sh in the file prints the maj:min numbers on just fine on the other hand :thinking:
That said, I tried using that but now I get stat write error :sweat_smile:
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (10 preceding siblings ...)
2021-02-03 15:16 ` foopub
@ 2021-02-03 15:50 ` foopub
2021-02-03 16:11 ` ahesford
` (5 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: foopub @ 2021-02-03 15:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772610283
Comment:
This is very weird. I did some testing and, while it functions just fine
`(stat "$resume" -c %t:%T | tr -d , > /sys/power/resume)>/.resume` gives tr: write error
`(stat "$resume" -c %t:,%T | tr -d , > /sys/power/resume)>/.resume` no error
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (11 preceding siblings ...)
2021-02-03 15:50 ` foopub
@ 2021-02-03 16:11 ` ahesford
2021-02-03 16:58 ` foopub
` (4 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: ahesford @ 2021-02-03 16:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772626257
Comment:
Herewith, a couple of observations:
- The write error is not from `stat`, `tr` or anything like that. It's the kernel rejecting the values you're trying to write to `/sys/power/resume`.
- The output of the `ls` scrape is *not* the same as that from `stat`. `ls` prints device types in decimal, but `stat` prints hex values:
```
% ls -lH /dev/watchdog
crw------- 1 root root 10, 130 Jan 25 23:43 /dev/watchdog
% stat /dev/watchdog -c '%t:%T'
a:82
```
- Sometimes these sysfs writes are finicky, and a terminating newline can cause a problem. In the original `ls` scrape, you can try `echo -n` to suppress the new line. In the `stat` version, you can use `tr -d '\n'`.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (12 preceding siblings ...)
2021-02-03 16:11 ` ahesford
@ 2021-02-03 16:58 ` foopub
2021-02-03 17:06 ` foopub
` (3 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: foopub @ 2021-02-03 16:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772661674
Comment:
> Herewith, a couple of observations:
>
> * The write error is not from `stat`, `tr` or anything like that. It's the kernel rejecting the values you're trying to write to `/sys/power/resume`.
>
> * The output of the `ls` scrape is _not_ the same as that from `stat`. `ls` prints device types in decimal, but `stat` prints hex values:
>
>
> ```
> % ls -lH /dev/watchdog
> crw------- 1 root root 10, 130 Jan 25 23:43 /dev/watchdog
>
> % stat /dev/watchdog -c '%t:%T'
> a:82
> ```
>
> * Sometimes these sysfs writes are finicky, and a terminating newline can cause a problem. In the original `ls` scrape, you can try `echo -n` to suppress the new line. In the `stat` version, you can use `tr -d '\n'`.
Aight, good points! It seems the kernel won't accept wrong values in the correct format either. Running `stat $resume -c %t:%T | tr -d '\n'` inside the script actually prints 0:0 (instead of 8:3 which is my swap file) and is also rejected.
Perhaps the stem of the issue is $resume pointing to the wrong thing?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (13 preceding siblings ...)
2021-02-03 16:58 ` foopub
@ 2021-02-03 17:06 ` foopub
2021-02-03 17:22 ` foopub
` (2 subsequent siblings)
17 siblings, 0 replies; 19+ messages in thread
From: foopub @ 2021-02-03 17:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772661674
Comment:
> Herewith, a couple of observations:
>
> * The write error is not from `stat`, `tr` or anything like that. It's the kernel rejecting the values you're trying to write to `/sys/power/resume`.
>
> * The output of the `ls` scrape is _not_ the same as that from `stat`. `ls` prints device types in decimal, but `stat` prints hex values:
>
>
> ```
> % ls -lH /dev/watchdog
> crw------- 1 root root 10, 130 Jan 25 23:43 /dev/watchdog
>
> % stat /dev/watchdog -c '%t:%T'
> a:82
> ```
>
> * Sometimes these sysfs writes are finicky, and a terminating newline can cause a problem. In the original `ls` scrape, you can try `echo -n` to suppress the new line. In the `stat` version, you can use `tr -d '\n'`.
Aight, good points! It seems the kernel won't accept wrong values in the correct format either. Running `stat $resume -c %t:%T | tr -d '\n'` inside the script actually prints 0:0 (instead of 8:3 which is my swap file) and is also rejected.
Perhaps the stem of the issue is $resume pointing to the wrong thing?
Edit: nvm, $resume seems to be pointing to a link - using `stat $resume -Lc %t:%T | tr -d '\n'` is fine
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (14 preceding siblings ...)
2021-02-03 17:06 ` foopub
@ 2021-02-03 17:22 ` foopub
2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
17 siblings, 0 replies; 19+ messages in thread
From: foopub @ 2021-02-03 17:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-772679789
Comment:
Welp... It turns out `/sys/power/resume` can take a path format too, i.e. /dev/sda3
`(readlink -fn $resume > /sys/power/resume)>/.resume` is by far the best solution.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (15 preceding siblings ...)
2021-02-03 17:22 ` foopub
@ 2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
17 siblings, 0 replies; 19+ messages in thread
From: github-actions @ 2022-04-15 2:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/13024#issuecomment-1099786664
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [ISSUE] [CLOSED] Dracut message on system boot
2019-07-12 8:00 [ISSUE] Dracut message on system boot voidlinux-github
` (16 preceding siblings ...)
2022-04-15 2:12 ` github-actions
@ 2022-04-29 2:13 ` github-actions
17 siblings, 0 replies; 19+ messages in thread
From: github-actions @ 2022-04-29 2:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Closed issue by shumvgolove on void-packages repository
https://github.com/void-linux/void-packages/issues/13024
Description:
`Void Linux 5.0.21_1`
When Void Linux boots, TTY shows this line:
```
//lib/dracut/hooks/pre-mount/10-resume.sh: line 20: echo: write error: Invalid argument rw, relatime
```
Things I've tried:
- `xbps-reconfigure -f linux5.0`
- `dracut -f -H`
- Searching in Dracut repository for `10-resume.sh` – [here](https://github.com/dracutdevs/dracut/blob/bca1967c90967d5453d8b215ff28552776e4fcb3/modules.d/95resume/parse-resume.sh#L78)
Search gave me [this](https://bugzilla.redhat.com/show_bug.cgi?id=872878) result (not really useful tho).
^ permalink raw reply [flat|nested] 19+ messages in thread