Emergency mode!!!

[skallal]

Here's the /var/log/boot.log file from the last boot of /dev/nvme0n1p1:

Code: Select all

------------ Fri Mar 22 14:55:00 PDT 2024 ------------
rootMX23: clean, 1162277/30531584 files, 91773781/122095360 blocks
[[0;1;31m TIME [0m] Timed out waiting for device [0;1;39mdev-disk-by\x2duuid-4fe7f126\x2dfe96\x2d4d7e\x2d9019\x2d603bd9803012.device[0m - /dev/disk/by-uuid/4fe7f126-fe96-4d7e-9019-603bd9803012.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39msystemd-fsck@dev-disk-by\x2duuid-4fe7f126\x2dfe96\x2d4d7e\x2d9019\x2d603bd9803012.service[0m - File System Check on /dev/disk/by-uuid/4fe7f126-fe96-4d7e-9019-603bd9803012.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mmnt-MyPassport.mount[0m - /mnt/MyPassport.
[[0;1;31m TIME [0m] Timed out waiting for device [0;1;39mdev-disk-by\x2duuid-ec8b9ec9\x2da3e9\x2d4527\x2dbd89\x2d2a1d1599915b.device[0m - /dev/disk/by-uuid/ec8b9ec9-a3e9-4527-bd89-2a1d1599915b.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39msystemd-fsck@dev-disk-by\x2duuid-ec8b9ec9\x2da3e9\x2d4527\x2dbd89\x2d2a1d1599915b.service[0m - File System Check on /dev/disk/by-uuid/ec8b9ec9-a3e9-4527-bd89-2a1d1599915b.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mmnt-Samsung.mount[0m - /mnt/Samsung.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mlocal-fs.target[0m - Local File Systems.
         Mounting [0;1;39mproc-sys-fs-binfmt_misc.mount[0m - Arbitrary Executable File Formats File System...
[[0;32m  OK  [0m] Mounted [0;1;39mproc-sys-fs-binfmt_misc.mount[0m - Arbitrary Executable File Formats File System.
[[0;32m  OK  [0m] Finished [0;1;39msystemd-binfmt.service[0m - Set Up Additional Binary Formats.
[[0;32m  OK  [0m] Finished [0;1;39msystemd-tmpfiles-setup.service[0m - Create Volatile Files and Directories.
         Mounting [0;1;39mrun-rpc_pipefs.mount[0m - RPC Pipe File System...
[[0;32m  OK  [0m] Started [0;1;39mhaveged.service[0m - Entropy Daemon based on the HAVEGE algorithm.
         Starting [0;1;39mrpcbind.service[0m - RPC bind portmap service...
         Starting [0;1;39msystemd-update-utmp.service[0m - Record System Boot/Shutdown in UTMP...
[[0;32m  OK  [0m] Mounted [0;1;39mrun-rpc_pipefs.mount[0m - RPC Pipe File System.
[[0;32m  OK  [0m] Reached target [0;1;39mrpc_pipefs.target[0m.
         Starting [0;1;39mnfs-blkmap.service[0m - pNFS block layout mapping daemon...
         Starting [0;1;39mnfs-idmapd.service[0m - NFSv4 ID-name mapping service...
         Starting [0;1;39mnfsdcld.service[0m - NFSv4 Client Tracking Daemon...
[[0;32m  OK  [0m] Reached target [0;1;39mnfs-client.target[0m - NFS client services.
[[0;32m  OK  [0m] Started [0;1;39mnfs-blkmap.service[0m - pNFS block layout mapping daemon.
[[0;32m  OK  [0m] Started [0;1;39mrpcbind.service[0m - RPC bind portmap service.
[[0;32m  OK  [0m] Started [0;1;39mnfsdcld.service[0m - NFSv4 Client Tracking Daemon.
[[0;32m  OK  [0m] Reached target [0;1;39mremote-fs-pre.target[0m - Preparation for Remote File Systems.
[[0;32m  OK  [0m] Reached target [0;1;39mrpcbind.target[0m - RPC Port Mapper.
[[0;32m  OK  [0m] Finished [0;1;39msystemd-update-utmp.service[0m - Record System Boot/Shutdown in UTMP.
[[0;32m  OK  [0m] Started [0;1;39mnfs-idmapd.service[0m - NFSv4 ID-name mapping service.
         Starting [0;1;39msystemd-update-utmp-runlevel.service[0m - Record Runlevel Change in UTMP...
[[0;32m  OK  [0m] Finished [0;1;39msystemd-update-utmp-runlevel.service[0m - Record Runlevel Change in UTMP.
[[0;32m  OK  [0m] Finished [0;1;39mufw.service[0m - Uncomplicated firewall.
[[0;32m  OK  [0m] Reached target [0;1;39mnetwork-pre.target[0m - Preparation for Network.
         Starting [0;1;39mnetworking.service[0m - Raise network interfaces...
         Starting [0;1;39msystemd-networkd.service[0m - Network Configuration...
[[0;32m  OK  [0m] Started [0;1;39msystemd-networkd.service[0m - Network Configuration.
[[0;32m  OK  [0m] Finished [0;1;39mnetworking.service[0m - Raise network interfaces.
[[0;32m  OK  [0m] Reached target [0;1;39mnetwork.target[0m - Network.
[[0;32m  OK  [0m] Reached target [0;1;39mnetwork-online.target[0m - Network is Online.
         Mounting [0;1;39mmnt-MyBook.mount[0m - /mnt/MyBook...
         Starting [0;1;39mnfs-mountd.service[0m - NFS Mount Daemon...
         Starting [0;1;39mrpc-statd.service[0m - NFS status monitor for NFSv2/3 locking....
[[0;1;31mFAILED[0m] Failed to mount [0;1;39mmnt-MyBook.mount[0m - /mnt/MyBook.
See 'systemctl status mnt-MyBook.mount' for details.
[[0;1;38;5;185mDEPEND[0m] Dependency failed for [0;1;39mremote-fs.target[0m - Remote File Systems.
[[0;32m  OK  [0m] Started [0;1;39mrpc-statd.service[0m - NFS status monitor for NFSv2/3 locking..
[[0;32m  OK  [0m] Started [0;1;39mnfs-mountd.service[0m - NFS Mount Daemon.
         Starting [0;1;39mnfs-server.service[0m - NFS server and services...
[[0;32m  OK  [0m] Finished [0;1;39mnfs-server.service[0m - NFS server and services.
         Starting [0;1;39mrpc-statd-notify.service[0m - Notify NFS peers of a restart...
[[0;32m  OK  [0m] Started [0;1;39mrpc-statd-notify.service[0m - Notify NFS peers of a restart.

No other log files were timestamped for that boot attempt.

[Charlie Brown]

Check the /etc/fstab (of the nvme0n1p1 ) whether there are invalid entries / wrong uuid numbers. (You can compare with lsblk -f or blkid )

Also if Windows is still bootable and if you didn't before: Disable "Fast Startup" there.

[skallal]

Check the /etc/fstab (of the nvme0n1p1 ) whether there are invalid entries / wrong uuid numbers. (You can compare with lsblk -f or blkid )

Also if Windows is still bootable and if you didn't before: Disable "Fast Startup" there.

I beat you to it! Just commented out a lot of unnecessary lines in fstab and now I'm booted back up on the new NVMe drive! Think I did the same on the other drive. The clue was boot.log was the only log file updated on that last failed boot attempt.

Next step is to make new backups.

I don't have any Windows bootable drives hooked up though I did earlier. It was connected through a SATA to USB adapter and probably couldn't boot Windows anyway. I've only been running Windows on this machine in KVM.

Thanks for your assistance!!!

[Charlie Brown]

:)

I was just going to add these (to maybe comment out in fstab)

Code: Select all

/mnt/MyPassport
/mnt/Samsung
/mnt/MyBook

Glad to hear both are bootable now.


P.S. You already know how to mark the thread :)

[skallal]

:)

I was just going to add these (to maybe comment out in fstab)

/mnt/MyPassport
/mnt/Samsung
/mnt/MyBook

Glad to hear both are bootable now.


P.S. You already know how to mark the thread :)

/mnt/MyBook is my network drive hosted on a Raspberry Pi 4. It's my main bulk storage on my LAN through ethernet. It's a whopping 8 TB but needs cleaned up.

[skallal]

@Charlie Brown

I think I know what really happened. The drive /dev/sda mounted was a single ext4 partition mounted at /mnt/Samsung. I had a test install of MX 23 there. Today I attempted unsuccessfully to clone a fresh Windows install to it. But it was set as ext4 in fstab.

So it wasn't Clonezilla after all, at least not directly. It was putting the 4 Windows partitions on the drive that froze both working drives. At least it's makes logical sense.

[DukeComposed]

I think I know what really happened. The drive /dev/sda mounted was a single ext4 partition mounted at /mnt/Samsung. I had a test install of MX 23 there. Today I attempted unsuccessfully to clone a fresh Windows install to it. But it was set as ext4 in fstab.

Clonezilla throws a bunch of warnings about trying to write partitions when it thinks something is going to go wrong, like if the target machine isn't the right size, and regardless of what happens it writes a log file that's worth your time to copy somewhere safe and review. Windows typically doesn't play well with others, so if there's already something else on that disk you may not have a lot of luck installing Windows on it directly, but you can always take the install ISO and apply the Windows image to an exact partition by hand. In either case when putting Windows on a new disk you want to figure out if you're going to use either (a) the Windows bootloader or (b) anything else. And if the disk is going to be run on different hardware, you should consider sysprepping the Windows machine before you create the Clonezilla image.