You are not logged in.

Pages: 1

#1 2022-07-23 04:53:32

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

[SOLVED] Permission bug, possible /etc/fstab problem

So, I just installed arch on a computer and I wanted to partition my SSD to have windows, arch, boot and data partitions. But the thing is: for some unknown reason, arch refuses to mount data as RW no matter what I put on fstab, and I edited it so much that now my system takes forever to start (like 5-10 minutes), and it bugs, asks for my password in terminal and then shows the GUI. Here's my fstab, I have ntfs-3g installed, should I format it over again? Nothing seems to solve this, it's really annoying.

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=573f4f9f-d064-4311-b4c5-b401ad14ba79   /           ext4      rw,relatime                              0 1 

# /dev/sda3
UUID=72C9283D0D95EDA0                       /boot       ntfs3     rw,relatime,uid=0,gid=0,iocharset=utf8   0 0 

# /dev/sda4 LABEL=data
UUID=3E0AEDD80E7BFBCF                       /data_int   ntfs3          defaults                0 0

# /dev/sda2
UUID=48DCA4E853D67FE0                       /windows    ntfs3          defaults                0 0

According to the wiki page on ntfs-3g, it should work fine, but it definetely doesn't. What am I doing wrong?

Last edited by rafaellancas (2022-07-23 21:14:11)

Offline

#2 2022-07-23 06:10:21

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

have windows, arch, boot and data partitions. But the thing is: for some unknown reason, arch refuses to mount data as RW

I guess the system journal will know the answer and it's most likely that the partition is marked "dirty" and the reason for that is quite possibly … see the 3rd link below.

I edited it so much that now my system takes forever to start (like 5-10 minutes), and it bugs, asks for my password in terminal and then shows the GUI

Likewise, the journal will know why that is - and maybe also systemd-analyze blame/critical-chain

What am I doing wrong?

I don't know. Can you guess what does…?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2022-07-23 16:21:48

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

seth wrote:

have windows, arch, boot and data partitions. But the thing is: for some unknown reason, arch refuses to mount data as RW

I guess the system journal will know the answer and it's most likely that the partition is marked "dirty" and the reason for that is quite possibly … see the 3rd link below.

I edited it so much that now my system takes forever to start (like 5-10 minutes), and it bugs, asks for my password in terminal and then shows the GUI

Likewise, the journal will know why that is - and maybe also systemd-analyze blame/critical-chain

What am I doing wrong?

I don't know. Can you guess what does…?

Thank you for your answer! I believe I have stopped hibernation and anything that would cause trouble on windows, following the third link. About the journal, what is it? The solution that I found for the long boot time was to "#" the lines, now linux just doesn't mount anything besides "/", and I can mount them manually by clicking on them on dolphin and typing my password. The only bad part is that the partitions mount completely bugged, sometimes I extract a file inside them and they say it's extracted but it's not, or they all of sudden decide to screw my permissions for specific files or folders. I tried using chown on them, but the bugs continue.

Offline

#4 2022-07-23 17:01:47

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

So, I managed to see that the bug that I have when booting up is dependency failed for file system, but I have ntfs-3g installed. What else do I need to do to make fstab work?

Offline

#5 2022-07-23 19:10:39

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

I believe I have…

The cool think about this is: you don't have to believe that - you can actually look up the condition.

About the journal, what is it?

https://wiki.archlinux.org/title/System … ing_output … you're looking for "sudo journalctl -b".

the bug that I have when booting up is dependency failed for file system

Don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2022-07-23 21:13:31

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

seth wrote:

I believe I have…

The cool think about this is: you don't have to believe that - you can actually look up the condition.

About the journal, what is it?

https://wiki.archlinux.org/title/System … ing_output … you're looking for "sudo journalctl -b".

the bug that I have when booting up is dependency failed for file system

Don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855


Awesome! I found out that ntfs-3g needs to be installed with fuse, otherwise it bugs completely, so I removed it first with sudo pacman -Rns ntfs-3g and reinstalled it with sudo pacman -S ntfs-3g fuse. Now everything is working like it should: my fstab is with ntfs-3g defaults 0 0 on the ntfs partitions and everything works fine!

Offline

#7 2022-07-23 21:42:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

Modern kernels ship the paragon ntfs3 kernel module - you should no require ntfs-3g and you didn't use it in your initial fstab.
https://wiki.archlinux.org/title/NTFS

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2022-07-24 00:59:40

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

seth wrote:

Modern kernels ship the paragon ntfs3 kernel module - you should no require ntfs-3g and you didn't use it in your initial fstab.
https://wiki.archlinux.org/title/NTFS

Yes, but fstab ignores the line if I try to put ntfs3 instead of ntfs-3g, there's nothing to do here I believe? I took a look at the link, I'll try to mount one of the partitions manually with ntfs3 later to see if it's just fstab that is ignoring it or the whole system.

Offline

#9 2022-07-24 02:33:43

skunktrader
Member
From: Brisbane, Australia
Registered: 2010-02-14
Posts: 1,677

Re: [SOLVED] Permission bug, possible /etc/fstab problem

rafaellancas wrote:

Yes, but fstab ignores the line if I try to put ntfs3 instead of ntfs-3g, there's nothing to do here I believe? I took a look at the link, I'll try to mount one of the partitions manually with ntfs3 later to see if it's just fstab that is ignoring it or the whole system.

Did you try specifying ntfs as the fstype?

Offline

#10 2022-07-24 03:35:55

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

skunktrader wrote:
rafaellancas wrote:

Yes, but fstab ignores the line if I try to put ntfs3 instead of ntfs-3g, there's nothing to do here I believe? I took a look at the link, I'll try to mount one of the partitions manually with ntfs3 later to see if it's just fstab that is ignoring it or the whole system.

Did you try specifying ntfs as the fstype?

Yes, fstab ignores the line if I do that. The only option for ntfs is ntfs-3g, otherwise it just ignores the line. But everything is working now, I was even able to make it automount my external hdd.

Offline

#11 2022-07-24 06:12:26

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

ntfs (unlike ntfs3 and ntfs-3g) doesn't support writing access to begin with.

Yes, but fstab ignores the line if I try to put ntfs3 instead of ntfs-3g

fstab does nothing, and I'd be surprised if systemd-mount completely *ignores* a not commented line in etc/fstab - please post the system jorunal for a mount where you attempted to use ntfs3 (eg. "sudo journalctl -b -3" for the third last boot)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2022-07-24 17:23:58

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

seth wrote:

ntfs (unlike ntfs3 and ntfs-3g) doesn't support writing access to begin with.

Yes, but fstab ignores the line if I try to put ntfs3 instead of ntfs-3g

fstab does nothing, and I'd be surprised if systemd-mount completely *ignores* a not commented line in etc/fstab - please post the system jorunal for a mount where you attempted to use ntfs3 (eg. "sudo journalctl -b -3" for the third last boot)

Well, now I didn't have any problems at boot, but the permissions are all messed up on the ntfs drives. To me, it looks like one of those "x11 and wayland" situations, where one(x11) just works while the other is full of bugs(wayland). But I tried your journal command:

[rafael@pc ~]$ sudo journalctl -b -3
[sudo] senha para rafael: 
jul 23 20:37:46 pc kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15
jul 23 20:37:46 pc kernel: Linux version 5.18.13-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 ZEN SMP PREEMPT_DYNAMIC Fri, 22 Ju>
jul 23 20:37:46 pc kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=573f4f9f-d064-4311-b4c5-b401ad14ba79 rw rootfstype=ext4 loglevel=3 quiet
jul 23 20:37:46 pc kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
jul 23 20:37:46 pc kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
jul 23 20:37:46 pc kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
jul 23 20:37:46 pc kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
jul 23 20:37:46 pc kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
jul 23 20:37:46 pc kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
jul 23 20:37:46 pc kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
jul 23 20:37:46 pc kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
jul 23 20:37:46 pc kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
jul 23 20:37:46 pc kernel: signal: max sigframe size: 2032
jul 23 20:37:46 pc kernel: BIOS-provided physical RAM map:
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009c3ff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000000009c400-0x000000000009ffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000403fffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x0000000040400000-0x00000000855bdfff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000855be000-0x00000000855befff] ACPI NVS
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000855bf000-0x00000000855bffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000855c0000-0x000000008cbe8fff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008cbe9000-0x000000008d098fff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008d099000-0x000000008d14ffff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008d150000-0x000000008d505fff] ACPI NVS
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008d506000-0x000000008dffefff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008dfff000-0x000000008dffffff] usable
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x000000008e000000-0x00000000cf7fffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
jul 23 20:37:46 pc kernel: BIOS-e820: [mem 0x0000000100000000-0x000000042f7fffff] usable
...skipping...
jul 23 20:39:22 pc systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jul 23 20:39:22 pc systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Create Static Device Nodes in /dev.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname>
jul 23 20:39:22 pc systemd[1]: systemd-sysusers.service: Deactivated successfully.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
jul 23 20:39:22 pc systemd[1]: Stopped Create System Users.
jul 23 20:39:22 pc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Remount Root and Kernel File Systems.
jul 23 20:39:22 pc systemd[1]: lvm2-monitor.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
jul 23 20:39:22 pc systemd[1]: Reached target System Shutdown.
jul 23 20:39:22 pc systemd[1]: Reached target Late Shutdown Services.
jul 23 20:39:22 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
jul 23 20:39:22 pc systemd[1]: systemd-reboot.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Finished System Reboot.
jul 23 20:39:22 pc systemd[1]: Reached target System Reboot.
jul 23 20:39:22 pc systemd[1]: Shutting down.
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc kernel: watchdog: watchdog0: watchdog did not stop!
jul 23 20:39:22 pc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc systemd-shutdown[1]: Syncing filesystems and block devices.
jul 23 20:39:22 pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 23 20:39:22 pc systemd-journald[235]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 23 20:39:22 pc systemd-journald[235]: Journal stopped
...skipping...
jul 23 20:39:22 pc systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jul 23 20:39:22 pc systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Create Static Device Nodes in /dev.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname>
jul 23 20:39:22 pc systemd[1]: systemd-sysusers.service: Deactivated successfully.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
jul 23 20:39:22 pc systemd[1]: Stopped Create System Users.
jul 23 20:39:22 pc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Remount Root and Kernel File Systems.
jul 23 20:39:22 pc systemd[1]: lvm2-monitor.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
jul 23 20:39:22 pc systemd[1]: Reached target System Shutdown.
jul 23 20:39:22 pc systemd[1]: Reached target Late Shutdown Services.
jul 23 20:39:22 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
jul 23 20:39:22 pc systemd[1]: systemd-reboot.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Finished System Reboot.
jul 23 20:39:22 pc systemd[1]: Reached target System Reboot.
jul 23 20:39:22 pc systemd[1]: Shutting down.
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc kernel: watchdog: watchdog0: watchdog did not stop!
jul 23 20:39:22 pc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc systemd-shutdown[1]: Syncing filesystems and block devices.
jul 23 20:39:22 pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 23 20:39:22 pc systemd-journald[235]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 23 20:39:22 pc systemd-journald[235]: Journal stopped
...skipping...
jul 23 20:39:22 pc systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jul 23 20:39:22 pc systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Create Static Device Nodes in /dev.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname>
jul 23 20:39:22 pc systemd[1]: systemd-sysusers.service: Deactivated successfully.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
jul 23 20:39:22 pc systemd[1]: Stopped Create System Users.
jul 23 20:39:22 pc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Remount Root and Kernel File Systems.
jul 23 20:39:22 pc systemd[1]: lvm2-monitor.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
jul 23 20:39:22 pc systemd[1]: Reached target System Shutdown.
jul 23 20:39:22 pc systemd[1]: Reached target Late Shutdown Services.
jul 23 20:39:22 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
jul 23 20:39:22 pc systemd[1]: systemd-reboot.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Finished System Reboot.
jul 23 20:39:22 pc systemd[1]: Reached target System Reboot.
jul 23 20:39:22 pc systemd[1]: Shutting down.
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc kernel: watchdog: watchdog0: watchdog did not stop!
jul 23 20:39:22 pc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc systemd-shutdown[1]: Syncing filesystems and block devices.
jul 23 20:39:22 pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 23 20:39:22 pc systemd-journald[235]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 23 20:39:22 pc systemd-journald[235]: Journal stopped
...skipping...
jul 23 20:39:22 pc systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jul 23 20:39:22 pc systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Create Static Device Nodes in /dev.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname>
jul 23 20:39:22 pc systemd[1]: systemd-sysusers.service: Deactivated successfully.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
jul 23 20:39:22 pc systemd[1]: Stopped Create System Users.
jul 23 20:39:22 pc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Remount Root and Kernel File Systems.
jul 23 20:39:22 pc systemd[1]: lvm2-monitor.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
jul 23 20:39:22 pc systemd[1]: Reached target System Shutdown.
jul 23 20:39:22 pc systemd[1]: Reached target Late Shutdown Services.
jul 23 20:39:22 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
jul 23 20:39:22 pc systemd[1]: systemd-reboot.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Finished System Reboot.
jul 23 20:39:22 pc systemd[1]: Reached target System Reboot.
jul 23 20:39:22 pc systemd[1]: Shutting down.
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc kernel: watchdog: watchdog0: watchdog did not stop!
jul 23 20:39:22 pc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc systemd-shutdown[1]: Syncing filesystems and block devices.
jul 23 20:39:22 pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 23 20:39:22 pc systemd-journald[235]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 23 20:39:22 pc systemd-journald[235]: Journal stopped
...skipping...
jul 23 20:39:22 pc systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jul 23 20:39:22 pc systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Create Static Device Nodes in /dev.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname>
jul 23 20:39:22 pc systemd[1]: systemd-sysusers.service: Deactivated successfully.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
jul 23 20:39:22 pc systemd[1]: Stopped Create System Users.
jul 23 20:39:22 pc systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Remount Root and Kernel File Systems.
jul 23 20:39:22 pc systemd[1]: lvm2-monitor.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a>
jul 23 20:39:22 pc systemd[1]: Reached target System Shutdown.
jul 23 20:39:22 pc systemd[1]: Reached target Late Shutdown Services.
jul 23 20:39:22 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=>
jul 23 20:39:22 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
jul 23 20:39:22 pc systemd[1]: systemd-reboot.service: Deactivated successfully.
jul 23 20:39:22 pc systemd[1]: Finished System Reboot.
jul 23 20:39:22 pc systemd[1]: Reached target System Reboot.
jul 23 20:39:22 pc systemd[1]: Shutting down.
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc audit: BPF prog-id=0 op=UNLOAD
jul 23 20:39:22 pc systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc kernel: watchdog: watchdog0: watchdog did not stop!
jul 23 20:39:22 pc systemd-shutdown[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog0
jul 23 20:39:22 pc systemd-shutdown[1]: Watchdog running with a timeout of 10min.
jul 23 20:39:22 pc systemd-shutdown[1]: Syncing filesystems and block devices.
jul 23 20:39:22 pc systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 23 20:39:22 pc systemd-journald[235]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 23 20:39:22 pc systemd-journald[235]: Journal stopped

No partitions are even mentioned throughout the code, but, if you got anything useful, pleas share with me.

Thank you so much for your support!

Offline

#13 2022-07-24 19:38:28

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

...skipping...

don't copy and paste out of the pager.
Redirect the output into a file or pastebin service

sudo journalctl -b -3 | curl -F 'file=@-' 0x0.st

but nb. that "-3" was just an example.
I don't know whether you were using the ntfs3 module 3 boots ago, you'll have to look for yourself (eg. "sudo journalctl -b -4 | grep ntfs3" to look at the 4th last boot)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2022-07-25 12:27:03

rafaellancas
Member
Registered: 2022-05-31
Posts: 86

Re: [SOLVED] Permission bug, possible /etc/fstab problem

seth wrote:

...skipping...

don't copy and paste out of the pager.
Redirect the output into a file or pastebin service

sudo journalctl -b -3 | curl -F 'file=@-' 0x0.st

but nb. that "-3" was just an example.
I don't know whether you were using the ntfs3 module 3 boots ago, you'll have to look for yourself (eg. "sudo journalctl -b -4 | grep ntfs3" to look at the 4th last boot)


Well, the whole output the thing to a file or pastebin service is way out of my knowledge at the moment, I will have to learn at least a little more about journal before being able to do that. I put ntfs3 again and tried the other command, since it was my last boot, I should put -1 right? The thing is my terminal just ignores the command if it's like that, but without anything it shows some folders that I copied last night. This "ntfs3" was supposed to work with read/write permissions?

[rafael@pc ~]$ sudo journalctl -b -1 | grep ntfs3
[sudo] senha para rafael: 
[rafael@pc ~]$ sudo journalctl -b | grep ntfs3
jul 25 09:21:12 pc kernel: ntfs3: Max link count 4000
jul 25 09:21:12 pc kernel: ntfs3: Enabled Linux POSIX ACLs support
jul 25 09:21:12 pc kernel: ntfs3: Read-only LZX/Xpress compression included
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=1ca5b, "The Legend of Dragoon" add mount option "acl" to use acl
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=1ca5b, "The Legend of Dragoon" add mount option "acl" to use acl
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=1ca5b, "The Legend of Dragoon" add mount option "acl" to use acl
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=714e, "PSX" add mount option "acl" to use acl
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=714e, "PSX" add mount option "acl" to use acl
jul 25 09:21:30 pc kernel: ntfs3: sdb1: ino=714e, "PSX" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=5, "/" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=5, "/" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=5, "/" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=8e, "Click" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=8e, "Click" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=8e, "Click" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=27, "$RECYCLE.BIN" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=27, "$RECYCLE.BIN" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=27, "$RECYCLE.BIN" add mount option "acl" to use acl
jul 25 09:21:32 pc kernel: ntfs3: sda4: ino=8cc0, ".Trash-1000" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: 239 callbacks suppressed
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=292a, "Silhouette Mirage" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=7fd3, "Downloads" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=7fd3, "Downloads" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=7fd3, "Downloads" add mount option "acl" to use acl
jul 25 09:21:40 pc kernel: ntfs3: sda4: ino=7fd3, "Downloads" add mount option "acl" to use acl
[rafael@pc ~]$

Offline

#15 2022-07-25 13:02:31

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,527

Re: [SOLVED] Permission bug, possible /etc/fstab problem

The grep only tells you that you're / have been using ntfs3 during the current boot, but you probably still want to post the entire journal for the boot .
The flurry of duplicate messages is weird, though.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB