Mageia forum

Hi All
My PC will not boot up to KDE. Running KDE, with all the latest updates
it dropped to shell and provided this

Code: Select all: mount: wrong fs type,bad option,bad superblock on /dev/sda1. missing code page or helper program, or ether error in some cases useful info foundin syslog -try dmeg : tall or so. dracut Warning :failed to mount -t ext4 -e re /dev/disk/by=uuid/........................... /sysroot dracut warning:*** an error occurred during the file system ahook. dropping to shell

sda1 is less than a year old
What could be wrong and Where do I go from here? is my PC getting old 2009?
I run a Nvidia Card
Many thanks Roy

What is your sda1, and what happens if you run fsck (filesystem check) on /dev/sda1 in the emergency shell?

sda1 is a plain old platter hard drive 500gb. only Mageia on it.
I will need to find a non wireless keyboard then I will go to Safe mode

So it's the / partition for Mageia?

And I don't get you, in your first post you quoted the part where it drops you to the shell :

RoyD wrote:
Code: Select all
dropping to shell

it goes to shell but the keyboard does not work

wired keyboard in now
try to boot to Mageia 5 . drops to Repair:/
fsck produces

Code: Select all: fsck from util-linux 2.25.2

fsck /dev/sda1 produces

Code: Select all: fsck from util-linux 2.25.2 fsck: error 2 (no such file or directory) while executing fsck.ext2 for /dev/sda1 Repair:/#

Well, has the device node already been created in that emergency shell, what does

Code: Select all: ls -al /dev/sd*

yield?
If this doesn't work then you have to use any other bootable linux media to run fsck on that partition.

Code: Select all: ls -al /dev/sd* brw--------1 root 0 8, 0 mar 19 21:21 /dev/sda brw--------1 root 0 8, 1 mar 19 21:21 /dev/sda1 brw--------1 root 0 8, 2 mar 19 21:21 /dev/sda2 brw--------1 root 0 8, 5 mar 19 21:21 /dev/sda5 brw--------1 root 0 8, 6 mar 19 21:21 /dev/sda6 brw--------1 root 0 8,16 mar 19 21:21 /dev/sdb brw--------1 root 0 8, 17 mar 19 21:21 /dev/sdb1

This morning I saw on my keyboard the num light was on. The PC was shut down last night.
So I pulled the power plug to the PC waited then put it back in. I had to do this a couple of weeks ago also.
The PC started normally.
I ran the codes you provided earlier

Code: Select all: [root@localhost roy]# fsck /dev/sda1 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sda1 is mounted. e2fsck: Cannot continue, aborting.

Code: Select all: [root@localhost roy]# ls -al /dev/sd* brw-rw---- 1 root disk 8, 0 Mar 20 07:46 /dev/sda brw-rw---- 1 root disk 8, 1 Mar 20 07:46 /dev/sda1 brw-rw---- 1 root disk 8, 2 Mar 20 07:46 /dev/sda2 brw-rw---- 1 root disk 8, 5 Mar 20 07:46 /dev/sda5 brw-rw---- 1 root disk 8, 6 Mar 20 07:46 /dev/sda6 brw-rw---- 1 root disk 8, 16 Mar 20 07:46 /dev/sdb brw-rw---- 1 root disk 8, 17 Mar 20 07:46 /dev/sdb1

When I think about it every so often the PC will freeze then goes to a black screen and I have no response from keyboard or mouse.

If you frequently pull the power plug no wonder the filesystem might be damaged.
And you cannot run fsck on a mounted filesystem and get reliable results, that's why I suggested using a live media.

Thank you for your help and patience. I will try this later today.

Right I have created a Mageia 5 Live disk.
ran the following

Code: Select all: [root@localhost ~]# fsck /dev/sda1 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sda1: clean, 168644/3301376 files, 1921575/13183084 blocks [root@localhost ~]#

Code: Select all: [root@localhost ~]# ls -al /dev/sd* brw-rw---- 1 root disk 8, 0 Mar 20 17:18 /dev/sda brw-rw---- 1 root disk 8, 1 Mar 20 17:18 /dev/sda1 brw-rw---- 1 root disk 8, 2 Mar 20 17:18 /dev/sda2 brw-rw---- 1 root disk 8, 5 Mar 20 17:18 /dev/sda5 brw-rw---- 1 root disk 8, 6 Mar 20 17:18 /dev/sda6 brw-rw---- 1 root disk 8, 16 Mar 20 17:18 /dev/sdb brw-rw---- 1 root disk 8, 17 Mar 20 17:18 /dev/sdb1 [root@localhost ~]#

I also tried

Code: Select all: [root@localhost ~]# fsck /dev/sda2 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda2 Could this be a zero-length partition? [root@localhost ~]# fsck /dev/sda5 fsck from util-linux 2.25.2 [root@localhost ~]# fsck /dev/sda6 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) /dev/sda6: clean, 238540/26968064 files, 27525484/107863944 blocks [root@localhost ~]#

sda was also the disk that is sda under Mageia?

As the filesystems look OK, could there have been any changes in Mageia /etc/fstab?
The mount line in the first post looks strange:

RoyD wrote:mount: wrong fs type,bad option,bad superblock on /dev/sda1.
missing code page or helper program, or ether error
in some cases useful info foundin syslog -try dmeg : tall or so.
dracut Warning :failed to mount -t ext4 -e re /dev/disk/by=uuid/...........................

Also, does the behaviour change if you select any older kernel in the Mageia bootloader?

I have not changed the fstab.
Just tries server 3.19.8_3.mga5 instead of server 4.1.15-2 .mga5 and did not boot. pressed f2. a few errors show
ext4-fs error device sda1 :ext4_find_entry:1289: imode#2753012: comm systemd_tmpfile :reading directory iblock 0
sda1 previous i/o error to superblock detected.

tried Mageia 5 many errors
many comm plymouthd: unable to read itables

I wonder if an old problem has come back to haunt me.
In Jan viewtopic.php?f=7&t=10663 an update did not work

Well, the question was not if you did any changes to the fstab but if there were changes. Please post the contents so we can take a look.

Please also post the output as root of

Code: Select all: fdisk -l lsblk -f

You do have lots patience. Thank you

Code: Select all: [live@localhost ~]$ su - gpg-agent[3463]: directory `/root/.gnupg' created gpg-agent[3463]: directory `/root/.gnupg/private-keys-v1.d' created gpg-agent[3464]: gpg-agent (GnuPG) 2.0.27 started [root@localhost ~]# fdisk -l Disk /dev/loop0: 1.7 GiB, 1759780864 bytes, 3437072 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/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 105466724 105464677 50.3G 83 Linux /dev/sda2 105469938 976768064 871298127 415.5G 5 Extended /dev/sda5 105469952 113852654 8382703 4G 82 Linux swap / Solaris /dev/sda6 113856512 976768064 862911553 411.5G 83 Linux Partition 3 does not start on physical sector boundary. Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 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: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 1953520064 1953518017 931.5G 83 Linux [root@localhost ~]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 ext4 b79e0c7a-fe61-43e9-bb27-49f7aa2b91a0 ├─sda2 ├─sda5 swap 088de398-f72b-414a-bfb0-0c5508169aa6 └─sda6 ext4 b8126fa6-b268-4717-ae15-7b22c8ba6498 sdb └─sdb1 ext4 VMM and Backup 98fed849-4eb0-4d35-befb-ec66a550ab86 sr0 iso9660 Mageia-5-KDE4-LiveDVD 2015-06-13-21-53-00-00 loop0 squashfs /run/mgali [root@localhost ~]#

You forgot to post the contents of the Mageia fstab.

fstab

Code: Select all: # Entry for /dev/sda1 : UUID=b79e0c7a-fe61-43e9-bb27-49f7aa2b91a0 / ext4 relatime,acl 1 1 # Entry for /dev/sda6 : UUID=b8126fa6-b268-4717-ae15-7b22c8ba6498 /home ext4 relatime,acl 1 2 none /proc proc defaults 0 0 # Entry for /dev/sda5 : UUID=088de398-f72b-414a-bfb0-0c5508169aa6 swap swap defaults 0 0

Looks all fine to me. If your box still complains about the fsck during normal boot, you may need to force a verbose filesystem check via

Code: Select all: fsck -fV /dev/sda1

when it's not mounted, meaning via live boot media, and it would be good if you can post the output here.
If that still doesn't help it's probably best to backup the data from your Mageia partition and reinstall, then copy your stuff back.

Code: Select all: [root@localhost /]# fsck -fv /dev/sda1 fsck from util-linux 2.25.2 e2fsck 1.42.12 (29-Aug-2014) 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 168645 inodes used (5.11%, out of 3301376) 121 non-contiguous files (0.1%) 82 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 163797/62 1921576 blocks used (14.58%, out of 13183084) 0 bad blocks 1 large file 145409 regular files 18362 directories 0 character device files 0 block device files 0 fifos 5884 links 4865 symbolic links (4778 fast symbolic links) 0 sockets ------------ 174520 files [root@localhost /]#

Thank you for all your help. if you think its best to re install please tell me. I have all the data so thats not problem. More importantly what could have caused the problem?

doktor5000 wrote:If that still doesn't help it's probably best to backup the data from your Mageia partition and reinstall, then copy your stuff back.

No clue what's actually broken on your box currently as obviously the filesystem seems to be OK from the output you posted, so can't tell you what may have caused it.

Thank you for all you help

I am not sure if it is the same topic but I find my problem is quite similar: sometimes my pc starts to issue strange sounds and then screen become blank with note ¨no input system¨ or something like that. The only possibility is to use power button to shut down and then power on. However my pc is quite new - I bought this HP last year. So I wander is it hardware problem or software. Is there any error logs in the system?

Mageia forum

Superblock [SOLVED]

Superblock [SOLVED]

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock

Re: Superblock [SOLVED]

Re: Superblock [SOLVED]