- This topic has 39 replies, 5 voices, and was last updated Jan 5-11:34 am by 0day.
-
Posts
-
anticapitalista
If you did what I suggested above, then forget about eudev/udev. Do not remove udev
Did it solve the problem?
You should have eudev 3.6Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
0day
I thought that the remaining configuration of the packages not installed could be removed, I’ve always done …
caprea
I reinstalled, the problem lies in the residual configuration of udev that I had deleted, should I leave udev in the remaining configuration
How did you do that ?
If you did that the problem is probably not related to the update of eudev.Which version of eudev is now installed on your system?DaveW
So far, no go… I have tried the suggestions from anticapitalista, as follows:
1. From boot menu, typing 3 doesn’t do anything. However, on the list of boot options, I can select alternate kernels (all have same issue), and I can select ‘c’ to get a commandline, with a limited list of commands. I was able to type characters into the commandline. But I’m not sure how to use the available commands.2. Booting from live USB stick, I did chroot and update-initramfs. This did not fix issue.
3. Booting from live USB stick, I downloaded the eudev debs, did the chroot and dpkg. The system reported that it was downgrading udev. Also ran update-initramfs again. The problem remains.
4. I noted during the initramfs dialogue, it reported an fsck error (Warning: Could not determine file system type for fsck hook. Ignoring.) I don’t know if this is a factor. However, when booting from the harddrive, the first couple of lines after the boot screen, report an fsck error, on this machine. (On the other machine, which was not updated, and still works, there is no similar message.) Hopefully, this is a clue.
Thank you.
- This reply was modified 4 years, 4 months ago by DaveW.
Anonymous
Hey DaveW,
Can you type ctrl-alt-f3 at the login screen and get a text login? This will allow
a little more insight if it’s eudev or another update causing it. Also anticapitalista,
does davew or new installs/upgrades still need to have the “dev” repo on the synaptic
section line before doingapt-get update && apt-get dist-upgradeAt login screen, there is no response from keyboard. ctrl-alt-f3 does nothing.
anticapitalista
Again boot via live media and type
fsck /dev/sda1Obviously, the /dev/sda1 should point to your installed system
- This reply was modified 4 years, 4 months ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Okay. I did chroot and ran fsck (Antix is on sda2 partition.) The partition is mounted.
I can access data on the partition.
But fsck complains as follows:root@D620-Antix:/# fsck /dev/sda2
fsck from util-linux 2.29.2
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/sda2 is mounted.
fsck.ext4: No such file or directory while trying to open /dev/sda2
Possibly non-existent device?
root@D620-Antix:/#- This reply was modified 4 years, 4 months ago by DaveW.
Does “/etc/mtab” file exist when you open /etc in the file manager.
there also should be a line withuuid= "some numbers" / ext4 defaults,noatime 1 1
or similar in the “/etc/fstab” file
the/ ext4 defaults,noatime 1 1part in both should match for your root partition.
That’s the “/etc” on the mounted harddrive partition not the live “/etc”.Try running fsck with the drive unmounted.
anticapitalista
No need to chroot when running live for the fsck
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Yes, mtab and fstab are present on the harddrive (sda2)
sda2 is formatted ext4I use Midnight Commander as file manager. From file dates, it looks like when I ran fsck it updated the files on the USB stick, not sda2. I ran fsck /dev/sda2 with sda2 both mounted and unmounted with no difference.
Both files on the USB stick show sda2 /media/D620-Antix ext4,realtime 0 0
I made copies of the original files on sda2, then overwrote them with the files from the USB stick, then changed the lines in both files to show sda2 /D620-Antix
So far, the fsck error still appears during the boot dialogue, and things are still locked up at the login screen. I guess I’ll make a new ISO of my working system, in preparation for re-installation.
- This reply was modified 4 years, 4 months ago by DaveW.
can I install the residual udev configuration I had removed from the live? Does eudev use the residual udev configuration?
anticapitalista
Why not do what I suggested?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
https://wiki.ubuntu-it.org/AmministrazioneSistema/Chroot now I try with chroot by entering the command you indicated to me
- You must be logged in to reply to this topic.
