Ext linux not found

Linux Mint Forums

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

joesplace Level 2
Posts: 82 Joined: Tue Dec 22, 2009 2:09 am Location: Moody, Alabama

(SOLVED) extlinux not found problem

Post by joesplace » Fri Apr 22, 2016 7:04 pm

Tried using UNetbootin today but no go. I installed it from the software manager in LM 17.3 Cinnamon but when I tried to run I get the following message: extlinux not found. Install the syslinux package or equivalent
I then opened the software manager and tried to install syslinux but it says it’s already installed.
Anybody have any ideas??

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Re: extlinux not found problem

Post by Mute Ant » Fri Apr 22, 2016 7:12 pm

They are variants of similar code.
syslinux . for booting files on a VFAT partition
extlinux . for booting files on an EXT partition . sudo apt-get install extlinux
isolinux . for booting files on an ISO9660 partition

austin.texas Level 20
Posts: 12003 Joined: Tue Nov 17, 2009 3:57 pm Location: at /home

Re: extlinux not found problem

Post by austin.texas » Fri Apr 22, 2016 7:25 pm

If UNetbootin doesn’t work for you, try MultiSystem — worked for me.
viewtopic.php?f=46&t=220803&p=1159055#p1159007

Mint 18.2 Cinnamon, Quad core AMD A8-3870 with Radeon HD Graphics 6550D, 8GB DDR3, Ralink RT2561/RT61 802.11g PCI
Linux Linx 2018

joesplace Level 2
Posts: 82 Joined: Tue Dec 22, 2009 2:09 am Location: Moody, Alabama

Re: extlinux not found problem

Post by joesplace » Fri Apr 22, 2016 7:39 pm

Источник

Arch Linux

I’m now an Arch-User for about two years and until now I managed to solve every problem I encountered. But I can’t seem to grasp, what’s going wrong currently, so I have to ask you for help.
Please keep in mind, that I’m new on the forums and that I’m not a native speaker.

I have following problem on my Acer Aspire E1 572G Laptop:

About one in two times, when I’m booting, I reach Emergency Shell instead of reaching the normal display manager.
This happens since I upgraded to the 5.3 kernel (appears on both 5.3 and 5.3.1).
In emergency shell, I log into the root account, look around and finally

On the second try, it usually boots just fine. It appears that it just won’t boot on a «cold boot», so when the laptop was powered off for half an hour or longer.
The offending lines are the following:

Sep 23 17:55:58 hypnos kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Sep 23 17:55:58 hypnos systemd[1]: systemd 243.0-1-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Sep 23 17:55:58 hypnos kernel: EXT4-fs (sda1): re-mounted. Opts: discard . Sep 23 17:55:58 hypnos kernel: Adding 4194300k swap on /swapfile. Priority:-2 extents:7 across:4947964k SSFS Sep 23 17:55:59 hypnos kernel: EXT4-fs (sda2): VFS: Can't find ext4 filesystem

And as you can guess, it only goes downhill from here:

Sep 23 17:55:59 hypnos mount[325]: mount: /home: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error. Sep 23 17:55:58 hypnos systemd[1]: Starting File System Check on /dev/sda2. Sep 23 17:55:58 hypnos systemd-fsck[320]: sda2: fsck.ntfs doesn't exist, not checking file system. Sep 23 17:55:58 hypnos systemd[1]: Started File System Check on /dev/sda2. Sep 23 17:55:58 hypnos systemd[1]: Mounting /home. Sep 23 17:55:58 hypnos systemd[1]: home.mount: Mount process exited, code=exited, status=32/n/a Sep 23 17:55:58 hypnos systemd[1]: home.mount: Failed with result 'exit-code'. Sep 23 17:55:58 hypnos systemd[1]: Failed to mount /home. Sep 23 17:55:58 hypnos systemd[1]: Dependency failed for Local File Systems. Sep 23 17:55:58 hypnos systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Sep 23 17:55:58 hypnos systemd[1]: local-fs.target: Triggering OnFailure= dependencies.

I have following setup with my disks:

/dev/sda is a 931.53 GiB WDC WD10SPZX-75Z dos formatted hard drive, containing

• /dev/sda1 — My old windows home partition (Type: HPFS/NTFS/exFAT)
• /dev/sda2 — My linux home partition (Type: Linux)

/dev/sdb is a 223.59 GiB SanDisk SSD PLUS with disklabel type gpt, containing:

• /dev/sdb1 — The root partition (Type: Linux filesystem)
• /dev/sdb3 — The boot partition (Type: EFI System)
• /dev/sdb2, /dev/sdb4 and /dev/sdb5 are used for my parallel windows installation which I haven’t bootet in months

Here’s the raw fdisk -l output. It looks a bit messy, since there’s a lot of the window stuff floating around.

Disk /dev/sdb: 223.59 GiB, 240065183744 bytes, 468877312 sectors Disk model: SanDisk SSD PLUS 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: gpt Disk identifier: F18718BE-ED6B-45A4-BC6A-F79668847C4E Device Start End Sectors Size Type /dev/sdb1 2048 209717247 209715200 100G Linux filesystem /dev/sdb2 209717248 210331647 614400 300M Windows recovery environment /dev/sdb3 210331648 210536447 204800 100M EFI System /dev/sdb4 210536448 210798591 262144 128M Microsoft reserved /dev/sdb5 210798592 420513791 209715200 100G Microsoft basic data Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-75Z 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: 0xc50c3c1e Device Boot Start End Sectors Size Id Type /dev/sda1 2048 524290047 524288000 250G 7 HPFS/NTFS/exFAT /dev/sda2 524290048 1891479551 1367189504 651.9G 83 Linux

As far as I can see, it tries to mount sda2 but «can’t find ext4 filesystem».
sda2 contains the home directory and should be mounted on boot.
So without being able to mount home, it fails to start and drops me into emergency-mode.

I have already checked the disks and my ram to no avail. They (luckily) seem fine.
Pacman reports no error when installing/reinstalling the linux and the image generation is also successful.

I have no clue, what to look for. It just seems strange, that it sometimes boots just fine and sometimes fails to recognize sda2 as an ext4 filesystem, which it clearly is.
Searching the forums didn’t yield any results for me. If someone finds anything, I’d really appreciate it (I don’t really know, what to search for, since the problem seems fairly specific. Perhaps I missed something)

Please tell me, if you need additional information. Any help is appreciating, in making my system boot normal again.

Last edited by Lyno_ (2019-09-23 18:01:16)

Источник

EXT4-fs (sdc): VFS: Can’t find ext4 filesystem

In short, this is where I found the best answers to my problem with my disks: https://help.ubuntu.com/community/DataRecovery During Fedora 15 installation, I added all my 3 drives to be mounted on boot. However, after the installation ended I could not mount them any more. During the reboot, I was presented with this message?

**Give root password for maintenance (or type Control-D for normal startup):** 

«Control-D» did not work and I ended turning off manually and reinstalling Fedora 14, in the hope it was a bug, but, as I knew latter, it was not. So I tried to added the disks manually in fstab:

$ nano /etc/fstab /dev/sdb1 /media/Unus ext4 defaults 0 0 /dev/sdc1 /media/Duo ext4 defaults 0 0 

$ mount media/Duo mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so 

$ dmesg | tail [ 897.592207] EXT4-fs (sdc): VFS: Can't find ext4 filesystem 

$ testDisk Disk /dev/sdb - 1000 GB / 931 GiB - ATA ST31000528AS Disk /dev/sdc - 2000 GB / 1863 GiB - ATA ST2000DL003-9VT1 Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121601 255 63 Partition Start End Size in sectors > P ext4 0 0 1 121601 80 63 1953525168 [Unus] Disk /dev/sdc - 2000 GB / 1863 GiB - CHS 243201 255 63 Partition Start End Size in sectors > P Unknown 0 0 1 243201 80 63 3907029168 

Note that just before installing Fedora 15, both disks were formatted with ext4 and were working normally. Is there a way to rebuild the filesystem without losing the data recorded on the disks? I wish to know what I should do, as both disks have indispensable data in them. Thanks. UPDATE: Following: http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/ As root I ran:

$ mkdir /media/Unus && mount /dev/sdb 

$ fsck.ext4 -vy /dev/sdb e2fsck 1.41.12 (17-May-2010) fsck.ext4: Superblock invalid, trying backup blocks. fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193

$ file -s /dev/sdb1 /dev/sdc1 /dev/sdb1: ACB archive data /dev/sdc1: LVM2 (Linux Logical Volume Manager) , UUID: XlSIOVm3e8Ozqv4EO0TgTCiKAOdW4V6 

Now I am figuring out how to fix disk /dev/sbc — 2000 GB / 1863 GiB — ATA ST2000DL003-9VT1 (which was ext4, by the way).

# e2fsck -n /dev/sdc1 e2fsck 1.41.12 (17-May-2010) e2fsck: Superblock invalid, trying backup blocks. e2fsck: Bad magic number in super-block while trying to open /dev/sdc1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193

Some print screens of the disks: http://imgur.com/a/hY6ze LAST UPDATE While I am waiting for the new disk to arrive, I was trying some of your suggestions. In order to try to activate a logical volume, I got this:

# lvchange -ay vg_atipico/**lv_duo** One or more specified logical volume(s) not found. 

Источник

Can’t mount disk (VFS: Can’t find ext4 filesystem) [closed]

Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers.

#mount -t ext4 /dev/sda /data mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so #dmesg | tail -1 EXT4-fs (sda): VFS: Can't find ext4 filesystem 

what am I doing wrong? I saw that many posters with similar problem were request to post the content of fstab so here it is:

#cat /etc/fstab # # /etc/fstab # Created by anaconda on Wed Aug 6 11:29:15 2014 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=276c97cc-9c5f-496f-a56f-ac3a45c58a26 / ext4 defaults,usrquota,grpquota 1 1 UUID=3978f122-03d4-48db-adeb-6fc8a2c624c4 /boot ext2 defaults 1 2 UUID=1251c6d8-c417-48df-9cf4-2f56e3a823a6 /tmp ext4 defaults 1 2 UUID=95fd67df-7172-4ac9-9264-0b50819a203a swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 

# cat /proc/partitions major minor #blocks name 8 32 244198584 sdc 8 33 102400 sdc1 8 34 4194304 sdc2 8 35 2097152 sdc3 8 36 1 sdc4 8 37 237802496 sdc5 8 48 244198584 sdd 8 49 102400 sdd1 8 50 4194304 sdd2 8 51 2097152 sdd3 8 52 1 sdd4 8 53 237802496 sdd5 8 0 21484255232 sda 8 16 21484255232 sdb 9 1 4192192 md1 9 3 237671232 md3 9 2 2096064 md2 9 0 102336 md0 #fdisk -l | grep sda Disk /dev/sda: 21999.9 GB, 21999877357568 bytes 

Источник