Linux Mint Debian version 5 on a 32-bit system with corrupted files?

F5F Stay Refreshed Hardware Desktop Linux Mint Debian version 5 on a 32-bit system with corrupted files?

Linux Mint Debian version 5 on a 32-bit system with corrupted files?

Linux Mint Debian version 5 on a 32-bit system with corrupted files?

N

NardiHero
Junior Member

9

04-13-2023, 10:50 AM

#1

I'm using a Dell Latitude D620 running Linux Mint, but it doesn't boot correctly. I see the Linux Mint icon, then the command prompt appears. Pressing ESC shows [ 0.272141] x86/cpu: VMX (disabled by bios modprobe) because dm-raid45 isn't found in modules.dep /dev/sda2. There are file system errors on the drive, possibly due to a corrupted orphan list. The root filesystem needs manual fsck. If you don’t press ESC, it displays [ 0.272141] x86/cpu: VMX (disabled) and suggests using BusyBox v1.30.1. More details are available at the provided link.

N

NardiHero

04-13-2023, 10:50 AM #1

I'm using a Dell Latitude D620 running Linux Mint, but it doesn't boot correctly. I see the Linux Mint icon, then the command prompt appears. Pressing ESC shows [ 0.272141] x86/cpu: VMX (disabled by bios modprobe) because dm-raid45 isn't found in modules.dep /dev/sda2. There are file system errors on the drive, possibly due to a corrupted orphan list. The root filesystem needs manual fsck. If you don’t press ESC, it displays [ 0.272141] x86/cpu: VMX (disabled) and suggests using BusyBox v1.30.1. More details are available at the provided link.

G

Gabsone
Junior Member

11

04-14-2023, 09:28 PM

#2

It indicates you should check your storage or controller. Such issues usually don’t occur by themselves.

G

Gabsone

04-14-2023, 09:28 PM #2

It indicates you should check your storage or controller. Such issues usually don’t occur by themselves.

A

ajpate
Member

223

04-14-2023, 09:42 PM

#3

How to proceed? Just type your question clearly. Mention any issues like bad HDD or the 2009 context.

A

ajpate

04-14-2023, 09:42 PM #3

How to proceed? Just type your question clearly. Mention any issues like bad HDD or the 2009 context.

W

walee123
Senior Member

737

04-15-2023, 06:51 PM

#4

Reach the main command line once the corruption notice appears. Disregard the dm-raid issue since it isn't critical. Enter fsck -yf /dev/sda2 at the terminal. The fsck tool scans and fixes file system errors. Likely, the hard drive is faulty given its age; swapping it out with a basic SSD would probably improve performance significantly.

W

walee123

04-15-2023, 06:51 PM #4

Reach the main command line once the corruption notice appears. Disregard the dm-raid issue since it isn't critical. Enter fsck -yf /dev/sda2 at the terminal. The fsck tool scans and fixes file system errors. Likely, the hard drive is faulty given its age; swapping it out with a basic SSD would probably improve performance significantly.