Mapper ERROR / Issue will not allow me to get to desktop

New to Debian (Or Linux in general)? Ask your questions here!

Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-24 03:28

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mapper/SATTime--3--vg-root
fsck exited with status code 8

and then all of the "normal" lines of progress that one would expect to see during boot (for the most part) at the end it reads:

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D) to continue.

Of course had any of those suggestions worked we would not be having this conversation.

Nothing I type does anything the cursor just sits there and blinks.......
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-25 19:45

Nothing is displayed on the screen when you type the password.
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-25 22:33

I cant believe, I missed that how stupid of me.....

Ok it got me back to a root prompt at least.....so the issue NOW is how to deal with the mapper situation, as I have been learning linux I have yet to run across a mapper issue, and the only reason I even know it exists is because i was trying to figure out the hyphen or rather double hyphens in my vg that lead to my host name having double dashes -- (which is - - extra space between added for clarities sake)...

Is it ok to continue this discussion here or should this be marked as asked SOLVED and the continuing issue started new in another post.....please advise...

Thank You for your insight and assistance.....

Alan
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-26 06:24

Please post the output of the following commands :
Code: Select all
fdisk -l
blkid
lvs
ls -l /dev/mapper
cat /proc/cmdline

and the contents of the file /etc/fstab.

Try to post this information as plain text, not pictures. I admit that copy/paste may be harder in emergency mode, but you can send the standard output of a command to a file using the > shell operator, and retrieve the files from another system (multiboot or live system) or write them to a removable media (USB drive or SD card) and read them on another computer.
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-26 10:28

Thank you Sir/Madam for your kind help, it is much appreciated...

Below is the output per your request:

root@SATTime-3:~# fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x886a3416

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 499711 497664 243M 83 Linux
/dev/sda2 501758 976771071 976269314 465.5G 5 Extended
/dev/sda5 501760 976771071 976269312 465.5G 8e Linux LVM




Disk /dev/mapper/SATTime--3--vg-root: 23.3 GiB, 24998051840 bytes, 48824320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SATTime--3--vg-var: 9.3 GiB, 9999220736 bytes, 19529728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SATTime--3--vg-swap_1: 3.9 GiB, 4202692608 bytes, 8208384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SATTime--3--vg-tmp: 1.9 GiB, 1996488704 bytes, 3899392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SATTime--3--vg-home: 427.2 GiB, 458651336704 bytes, 895803392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 7.5 GiB, 8053063680 bytes, 15728640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x42c538d9

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 15728639 15726592 7.5G c W95 FAT32 (LBA)
root@SATTime-3:~#
================================================================================================
root@SATTime-3:~# blkid
/dev/sda1: UUID="38889b2d-08c3-42d2-a347-c32972fd15e0" TYPE="ext2" PARTUUID="886a3416-01"
/dev/sda5: UUID="j3TYln-we2p-HcCf-BAkf-TtMS-utEc-Os8z4K" TYPE="LVM2_member" PARTUUID="886a3416-05"
/dev/mapper/SATTime--3--vg-root: UUID="1caf6d56-8ae4-4805-ace5-8fc33c813f35" TYPE="ext4"
/dev/mapper/SATTime--3--vg-var: UUID="e990f79d-0757-4487-9285-9b31e42820e8" TYPE="ext4"
/dev/mapper/SATTime--3--vg-swap_1: UUID="0faca89f-b0b6-4b24-a096-c470bd52641c" TYPE="swap"
/dev/mapper/SATTime--3--vg-tmp: UUID="3e4a6f8e-63d2-49ff-9a4f-c13df090c5c4" TYPE="ext4"
/dev/mapper/SATTime--3--vg-home: UUID="d7e6e360-802b-42db-bef3-ee61794e864e" TYPE="ext4"
/dev/sdb1: LABEL="FIRMWARE" UUID="F04D-5294" TYPE="vfat" PARTUUID="42c538d9-01"
root@SATTime-3:~#
================================================================================================
root@SATTime-3:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home SATTime-3-vg -wi-ao---- 427.15g
root SATTime-3-vg -wi-ao---- 23.28g
swap_1 SATTime-3-vg -wi-ao---- 3.91g
tmp SATTime-3-vg -wi-ao---- 1.86g
var SATTime-3-vg -wi-ao---- 9.31g
root@SATTime-3:~#
================================================================================================
root@SATTime-3:~# ls -l /dev/mapper
total 0
crw------- 1 root root 10, 236 May 26 03:28 control
lrwxrwxrwx 1 root root 7 May 26 03:28 SATTime--3--vg-home -> ../dm-4
lrwxrwxrwx 1 root root 7 May 26 03:28 SATTime--3--vg-root -> ../dm-0
lrwxrwxrwx 1 root root 7 May 26 03:28 SATTime--3--vg-swap_1 -> ../dm-2
lrwxrwxrwx 1 root root 7 May 26 03:28 SATTime--3--vg-tmp -> ../dm-3
lrwxrwxrwx 1 root root 7 May 26 03:28 SATTime--3--vg-var -> ../dm-1
root@SATTime-3:~#
================================================================================================
root@SATTime-3:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/SATTime--3--vg-root ro quiet
root@SATTime-3:~#
================================================================================================

Thank you again for reviewing and providing feedback and guidance....

Alan
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-26 10:46

My apologize for the secondary post, I forgot the last request
here is that data......

I am still able to <startx> and gain a cerian amount of manuveribility although networking
seems to be out in that mode but I am able to mount a drive and copy a file....

I will look for your reply following the Monaco F1 GP

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/SATTime--3--vg-root / ext4 errors=remount-ro 0 $
# /boot was on /dev/sda1 during installation
UUID=38889b2d-08c3-42d2-a347-c32972fd15e0 /boot ext2 defaults $
/dev/mapper/SATTime--3--vg-home /home ext4 defaults 0 $
/dev/mapper/SATTime--3--vg-tmp /tmp ext4 defaults 0 2
/dev/mapper/SATTime--3--vg-var /var ext4 defaults 0 2
/dev/mapper/SATTime--3--vg-swap_1 none swap sw 0 $
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# This is my orange SD card which mounts to /home/time/storage
UUID=AF75-21A8 /home/username/storage vfat defaults 0 3
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-26 11:20

All looks fine.
Looking at the error message deeper, it seems that "not found" is about fsck.ext4, not /dev/mapper/...
What is the output of
Code: Select all
ls -l /sbin/*fsck*


Note : avoid using nano to display file contents. Nano is an editor, not a pager. It truncates lines. less or even cat do the job just fine.
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-26 13:42

Apparently I have to do some MORE additional reading as I am unfamiliar with just what a [pager] is and this line:

"less or even cat do the job just fine"

I do not understand at all.....I know that cat is one of the functions you asked me to perform earlier, but I am unfamiliar with this term / function as well...

Here is requested output:

===========================================================================
root@SATTime-3:/etc# ls -l /sbin/*fsck*
lrwxrwxrwx 1 root root 8 Jan 24 2017 /sbin/dosfsck -> fsck.fat
-rwxr-xr-x 1 root root 305696 Jan 31 2017 /sbin/e2fsck
-rwxr-xr-x 1 root root 47096 Jan 20 2017 /sbin/exfatfsck
-rwxr-xr-x 1 root root 48328 Mar 7 10:29 /sbin/fsck
-rwxr-xr-x 1 root root 35680 Mar 7 10:29 /sbin/fsck.cramfs
lrwxrwxrwx 1 root root 9 Jan 20 2017 /sbin/fsck.exfat -> exfatfsck
lrwxrwxrwx 1 root root 6 Jan 31 2017 /sbin/fsck.ext2 -> e2fsck
lrwxrwxrwx 1 root root 6 Jan 31 2017 /sbin/fsck.ext3 -> e2fsck
lrwxrwxrwx 1 root root 6 Jan 31 2017 /sbin/fsck.ext4 -> e2fsck
-rwxr-xr-x 1 root root 55376 Jan 24 2017 /sbin/fsck.fat
-rwxr-xr-x 1 root root 85088 Mar 7 10:29 /sbin/fsck.minix
lrwxrwxrwx 1 root root 8 Jan 24 2017 /sbin/fsck.msdos -> fsck.fat
lrwxrwxrwx 1 root root 8 Jan 24 2017 /sbin/fsck.vfat -> fsck.fat
root@SATTime-3:/etc#
===========================================================================
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-28 08:04

All looks fine again...
What's the output of
Code: Select all
fsck.ext4 -n /dev/mapper/SATTime--3--vg-root
fsck.ext2 -n /dev/sda1
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-28 11:35

I will run the requested tests shortly, and post the results per your request, in the mean time I have run the previous commands on a separate machine not affected by this issue and have a general question, first the results from a completely different machine:

=================================================================================================================================
# fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2176F407-863B-4F90-990C-528E35321566

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 617123839 616073216 293.8G Linux filesystem
/dev/sda3 617123840 625141759 8017920 3.8G Linux swap




Disk /dev/sdb: 2.7 TiB, 3000558944256 bytes, 732558336 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x5517685d

Device Boot Start End Sectors Size Id Type
/dev/sdb1 256 732558335 732558080 2.7T b W95 FAT32
=================================================================================================================================
# blkid
/dev/sda1: UUID="0916-27B0" TYPE="vfat" PARTUUID="a718143a-addf-40c1-9640-3b0d0044ea26"
/dev/sda2: UUID="466c009d-cb2e-45f9-abd7-fe3e2860f2f6" TYPE="ext4" PARTUUID="290b749b-7dbb-4fc9-ae19-67d86da8adf7"
/dev/sda3: UUID="10787350-1067-4455-aff3-9207cd5e4698" TYPE="swap" PARTUUID="f0ce8dbd-f020-4a99-8ca6-66c4f12d7257"
/dev/sdb1: LABEL="EXT-2" UUID="2640-02CE" TYPE="vfat"
=================================================================================================================================
# lvs
bash: lvs: command not found
=================================================================================================================================
# ls -l /dev/mapper
total 0
crw------- 1 root root 10, 236 May 27 04:19 control
=================================================================================================================================
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=UUID=466c009d-cb2e-45f9-abd7-fe3e2860f2f6 ro quiet
=================================================================================================================================

I was just wondering why such dramatic differences (I colorized the output do highlight the fact that I am talking a bout a separate and healthy machine).....

Mabye it just is what it is and nothing more, was just wondering, I initially thought my problem was here: Blue = Healthy Machine Red = Sick Machine

# blkid
/dev/sda1: UUID="38889b2d-08c3-42d2-a347-c32972fd15e0" TYPE="ext2" PARTUUID="886a3416-01"
/dev/sda5: UUID="j3TYln-we2p-HcCf-BAkf-TtMS-utEc-Os8z4K" TYPE="LVM2_member" PARTUUID="886a3416-05"
/dev/mapper/SATTime--3--vg-root: UUID="1caf6d56-8ae4-4805-ace5-8fc33c813f35" TYPE="ext4"
/dev/mapper/SATTime--3--vg-var: UUID="e990f79d-0757-4487-9285-9b31e42820e8" TYPE="ext4"
/dev/mapper/SATTime--3--vg-swap_1: UUID="0faca89f-b0b6-4b24-a096-c470bd52641c" TYPE="swap"
/dev/mapper/SATTime--3--vg-tmp: UUID="3e4a6f8e-63d2-49ff-9a4f-c13df090c5c4" TYPE="ext4"
/dev/mapper/SATTime--3--vg-home: UUID="d7e6e360-802b-42db-bef3-ee61794e864e" TYPE="ext4"
/dev/sdb1: LABEL="FIRMWARE" UUID="F04D-5294" TYPE="vfat" PARTUUID="42c538d9-01"


will get back to you on the problem machine shortly....
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-28 12:24

Nothing dramatic here. The differences you see are due to differences in the installation.

"Blue" machine :
EFI boot
/, /home, /tmp, /var in the same filesystem
filesystem and swap are plain partitions (no LVM)

"Red" machine :
BIOS/legacy boot
/, /home, /tmp, /var in separated filesystems
filesystems and swap are LVM logical volumes
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-28 20:27

Output from problem machine per request

========================================================================================
root@SATTime-3:/# fsck.ext4 -n /dev/mapper/SATTime--3--vg-root
e2fsck 1.43.4 (31-Jan-2017)
Warning! /dev/mapper/SATTime--3--vg-root is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/mapper/SATTime--3--vg-root: clean, 329296/1525920 files, 1947011/6103040 blocks
========================================================================================
root@SATTime-3:/# fsck.ext2 -n /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
Warning! /dev/sda1 is mounted.
/dev/sda1 was not cleanly unmounted, check forced.
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
/dev/sda1: 338/62248 files (23.7% non-contiguous), 45028/248832 blocks
========================================================================================
root@SATTime-3:/#
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-28 20:30

OK thank you for the clarification on the 2 different installations.
Good stuff to know.....

I have just posted the latest requested results from the sick machine.....
will await your analysis....

thank you
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby p.H » 2018-05-29 09:00

All looks fine again. Sorry, I don't see what's wrong and could cause the error message you reported.
What happens when you press ctrl+d at the emergency prompt ?
p.H
 
Posts: 421
Joined: 2017-09-17 07:12

Re: Mapper ERROR / Issue will not allow me to get to desktop

Postby OHPRG » 2018-05-29 09:55

The cursor jumps to the next line and sits there and blinks
“Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body,
but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming
‘Wow! What a Ride!”
User avatar
OHPRG
 
Posts: 12
Joined: 2018-05-16 01:25
Location: California, Orange County, USA


Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable