MX Linux Forum

Support for MX and antiX Linux distros
https://www.forum.mxlinux.org/

Emergency mode!!!

https://www.forum.mxlinux.org/viewtopic.php?t=79836

Page 1 of 2

Emergency mode!!!

Posted: Fri Mar 22, 2024 4:42 pm
by skallal
I was playing around with Clonezilla try to clone a Windows drive. Yet somehow it must have corrupted something on my two good MX Linux drives. Both instances will boot up and the MX logo shows and times outs and enters emergency mode.


Image

Obviously I can't login. The messages makes no sense in this context.

Hopefully someone can get me out of this jam. The QSI is from a Live USB session.

Code: Select all

System:
  Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: quiet splasht nosplash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_x64 Libretto January 21  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: LENOVO product: 10MK0036US v: ThinkCentre M910s
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: LENOVO model: 3106 v: SDK0J40705 WIN 3425076170358 serial: <superuser required>
    UEFI-[Legacy]: LENOVO v: M1AKT59A date: 10/27/2023
CPU:
  Info: model: Intel Core i5-6500 bits: 64 type: MCP arch: Skylake-S gen: core 6 level: v3
    note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
    microcode: 0xF0
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3600 scaling: driver: intel_pstate governor: powersave
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 25599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel arch: Gen-9
    process: Intel 14n built: 2015-16 ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:1912 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: DP-2 model: Asus VE278 serial: <filter> built: 2012 res: 1920x1080 hz: 60 dpi: 82
    gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 530 (SKL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15b7 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 2.73 TiB used: 343.81 GiB (12.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD BLACK SN850X 1000GB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 620361WD temp: 25.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT480BX500SSD1 size: 447.13 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 054 scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 Series size: 232.89 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 6B0Q scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Seagate model: Backup+ BK size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0412 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 type: USB model: USB DISK 3.2 size: 232.89 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  ID-6: /dev/sde maj-min: 8:64 type: USB vendor: Generic model: SD Card size: 14.84 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2047 libs: 1045 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 223 Uptime: 13m wakeups: 1 Memory: 31.24 GiB used: 1.27 GiB (4.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:20 pm
by DukeComposed
skallal wrote: Fri Mar 22, 2024 4:42 pm I was playing around with Clonezilla try to clone a Windows drive. Yet somehow it must have corrupted something on my two good MX Linux drives. Both instances will boot up and the MX logo shows and times outs and enters emergency mode.
First things first, boot a live session and confirm (a) each disk still has a valid partition table, and (b) that each partition can be fscked and mounted without error, and that each contains the data it's supposed to have. From there you can determine if there's anything there that can be salvaged and determine if you want to run MX Boot Repair or manually rebuild an initramfs and install a bootloader.

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:24 pm
by skallal
@DukeComposed

Please give me the syntax for fsck. Any parameters? I’m using my mobile at the moment.

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:28 pm
by Charlie Brown
  • GParted (on live session) right-click on them (one by one) : "Check" ... "Apply"..
  • ... Or when they're not mounted, i.e.

    Code: Select all

    sudo e2fsck -fyvC0 /dev/sda7
    (the partition(s) as you see, not the whole drive)

    ... Change sda7 to whatever it is sdb4 etc... or i.e. .../dev/nvme0n1p6

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:35 pm
by skallal
@DukeComposed & @Charlie Brown

Both pass on gparted. Both /dev/sdb1 (SATA SSD) & /dev/nvme0n1p1 (new nvme).

I'm wondering if something happened to my actual PC settings, Clonezilla or not. But Live USB workings, so it's probably not my system.

Next time I use Clonezilla, I'll disconnect ALL unneeded drives.

Next steps???

Any FAQs to help me?

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:38 pm
by Charlie Brown
Just check sdb1 and nvme0n1p1 simply as above and try to boot them when it's done.

Code: Select all

sudo e2fsck -fyvC0 /dev/sdb1

Code: Select all

sudo e2fsck -fyvC0 /dev/nvme0n1p1

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:49 pm
by skallal
@Charlie Brown

Somehow /sdb1, my SATA SSD is working now. And I'm typing this booted into that session. But the new M.2 NVMe is not. I ran gparted check on both in Live USB.

Here's the result of your fsck example:

Code: Select all

sudo e2fsck -fyvC0 /dev/nvme0n1p1
[sudo] password for skallal:         
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure                                           
Pass 3: Checking directory connectivity                                        
Pass 4: Checking reference counts                                              
Pass 5: Checking group summary information                                     
                                                                               
     1162277 inodes used (3.81%, out of 30531584)
       11778 non-contiguous files (1.0%)
        1047 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 1038654/1310/4
    91773781 blocks used (75.17%, out of 122095360)
           0 bad blocks
          21 large files

      909505 regular files
      129799 directories
           2 character device files
           1 block device file
           0 fifos
      188778 links
      122889 symbolic links (122226 fast symbolic links)
          72 sockets
------------
     1351046 files
This is running from /dev/sdb1 which is mounted at /.

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:52 pm
by Charlie Brown
Now, when you try to boot the nvme0n1p1 is it the same error message or anything related to Grub?

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 5:57 pm
by DukeComposed
Charlie Brown wrote: Fri Mar 22, 2024 5:38 pm Just check sdb1 and nvme0n1p1 simply as above and try to boot them when it's done.
I'd add to pick one, mount it, confirm it still looks like an MX install inside, then try to get it to boot. Once one drive is working again it should be easier to try to rescue the other.

Re: Emergency mode!!!

Posted: Fri Mar 22, 2024 6:04 pm
by skallal
@Charlie Brown

/dev/nvme0n1p1 is return the sample error as before in post #1. It shows the MX logo for about 90 seconds and gives the same message in the snapshot below.

Image

I'll try to post some of the latest log files.

@DukeComposed

Yes one of the drives in working now though not sure how it got fixed. /dev/sdb1 is working but it's by far the slower drive. /dev/nvme0n1p1 is still bad.
All times are UTC-04:00
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited