#booted into emergency mode after new drive installed
46 messages · Page 1 of 1 (latest)
booted into emergency mode after new drive installed
oh, i have relatime and noatime. could that do it?
removing noatime didnt fix it
it mounts fine manually but that doesnt help
What encrypted partitions to unlock during boot are in /etc/crypttab
Show the error
just says failed to mount /home/amber/Music
thats it
i need to configure logrotate lol some of this is years old
the link I sent tells you how to show by specific boot
-bX
the specific boot just has this
mount /home/amber/Music will try to mount with the entry in fstab
and it works, yes
but it still throws a fit when i reboot
er, it did, maybe i specified sda1
it says uid invalid field
so docs lied
That doesn't use the fstab entry
yes thats why i said that
Are you missing something from the end of line
is there a way to specify uid, since uid isnt actually a valid option
What uid?
i would look it up but i hate trying to read things on my phone
Ah uid mount option
yes
That feature depends on the filesystem
xfs
ok
it worked in 2009
even though claimed not to
Mount and chown -R the path
will that persist?
errors also invalid option, rebooting again
does persist
weird, but ty
.solved
.close
... solved
#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.
- You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
- You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".
Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you