Sponsored Content
Operating Systems Linux Fedora SD's, fsck, dmesg, freezing, and the Corrupt FAT-fs Post 302992013 by Beta_OmegaAdinf on Monday 20th of February 2017 03:11:08 PM
Old 02-20-2017
Error SD's, fsck, dmesg, freezing, and the Corrupt FAT-fs

Up until today I haven't had a problem using an SD card with Fedora ( 25 ) but when I went to insert the SD adapter with the micro-sd card this time, the computer froze. It has frozen every time since. It is still reading the card, and after a minute or two of losing control of the GUI and terminal it mounts and I can access the files within the card. It used to mount the card with grace and ease and even performed the kindness of letting me know that the card was mounted successfully at the top of the screen. So what caused this? I don't know. It began today and today I:

Code:
sudo dnf upgrade

And from there I just modified a couple .brs files and ran them so I could go bug-hunting, and, on a side-note, enabled RPM-fusion on my system.

I don't know why any of those would cause the SD card to be read or mounted any differently, so I decided to call dmesg after inserting the card to see what I could find out.

"FAT-fs (mmcblk0p1) Volume was not properly unmounted. Some data may be corrupt. Please run fsck.". Oh so that's the problem. Well problem one led to problem two and three as when I tried to run fsck or e2fsck I got a rather cryptic warning.

/dev/mapper/fedora-root, /dev/sda1, /dev/mapper/fedora-home is mounted
Code:
WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage.

Well I don't want that, abort... abort!!! When trying to unmount these filesystems so that I could run fsck and see if I could fix the corrupt filesystem I would either get:

umount: /home: ( or /root: ) umount failed: Operation not permitted ( or the target is busy )

and /dev/sda1 flat out doesn't show up.

I'm at a loss. Can anyone explain to me how I would go about fixing the sd card and preventing the temporary full system lock-up? It would be preferred if I didn't have to perform cmd gymnastics or unmount everything on the system to do so, but if it's necessary then I'll do what I must.

Last edited by Beta_OmegaAdinf; 02-20-2017 at 04:18 PM.. Reason: Title missing comma.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CDE freezing

I am running Solaris 8 intel and recently my Common Desktop environment will not load. I enter the root username and password at the prompt, it switches to the CDE screen and the freezes. The OpenWindows environment works fine. I tried with a regular username (not root) and I get the same resutls.... (2 Replies)
Discussion started by: dangral
2 Replies

2. HP-UX

dmesg error ??

Hi all, I have a very weard error message in my dmesg output, and I cannot find the solution in google. Does anyone know what it might be ? Equivalently mapped reserve pool exhausted; Overall application performance may be improved by increasing the "eqmemsize" tunable parameter (currently... (3 Replies)
Discussion started by: davidg
3 Replies

3. SCO

SCO Unix 5.0.5 freezing

Hie I use SCO Unix 5.0.5 as my operating system and i have been having the following problem for the past couple of days : After every 3 hours or more , my system freezes and all users are locked out .I can not do anything even on the console . Each time i have to press the reset button... (2 Replies)
Discussion started by: babby
2 Replies

4. UNIX for Advanced & Expert Users

/usr corrupt, can get to fsck (solaris)

I have a solaris 5.8 system, it wont boot because /usr is corrupt, which means i cannot bring up fsck to run a disk check. Any ideas? (3 Replies)
Discussion started by: frankkahle
3 Replies

5. UNIX for Advanced & Expert Users

Thousands of "unattached inode" entries freezing fsck

We have some CentOS systems with ext3 filesystems that (on occasion) experiences long power failures that are longer than the UPS can handle. We run an fsck on the file systems at every boot, and sometimes they will come back on after a power failure, and when fsck runs there are tens of thousands... (0 Replies)
Discussion started by: nothsa
0 Replies

6. UNIX for Advanced & Expert Users

Strange FAT filesystem

My Garmin GPS device has a slot for an SD card. I'm using a 32 GB SD card which holds 22 GB data currently. If I attach my device to a USB port it shows two devices, the internal memory and the SD card. I have no problems with the internal memory which holds only 2 GB of data. I can mount... (2 Replies)
Discussion started by: HJarausch
2 Replies

7. Solaris

unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)

What can I fix this issue? I have ran below commands but everything is same.:confused: WARNING: Last shutdown is later than time on time-of-day chip: check date. The / file system (/dev/rdsk/c1t0d0s0) is being checked WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies

8. Hardware

Laptop freezing issues

I am having Laptop freezing issues. Whenever I try to use Firfox and vlc, chrome and vlc, firefox and chrome, or anything similar to that my computer freezes. I always have to kill one of the processes before I can use my laptop again. I am guessing this is a hardware issue because when I move... (5 Replies)
Discussion started by: cokedude
5 Replies
UMOUNT(8)						    BSD System Manager's Manual 						 UMOUNT(8)

NAME
umount -- unmount filesystems SYNOPSIS
umount [-fv] special | node umount -a | -A [-fv] [-h host] [-t type] DESCRIPTION
The umount command calls the unmount(2) system call to remove a special device or the remote node (rhost:path) from the filesystem tree at the point node. If either special or node are not provided, the appropriate information is taken from the list of filesystems provided by getfsent(3). The options are as follows: -a All the filesystems described via getfsent(3) are unmounted. -A All the currently mounted filesystems except the root are unmounted. -f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. The root filesystem cannot be forcibly unmounted. -h host Only filesystems mounted from the specified host will be unmounted. This option implies the -A option and, unless otherwise speci- fied with the -t option, will only unmount NFS filesystems. -t type Is used to indicate the actions should only be taken on filesystems of the specified type. More than one type may be specified in a comma separated list. The list of filesystem types can be prefixed with ``no'' to specify the filesystem types for which action should not be taken. For example, the umount command: umount -a -t nfs,hfs umounts all filesystems of the type NFS and HFS. -v Verbose, additional information is printed out as each filesystem is unmounted. NOTES
Due to the complex and interwoven nature of Mac OS X, umount may fail often. It is recommended that diskutil(1) (as in, ``diskutil unmount /mnt'') be used instead. SEE ALSO
unmount(2), getfsent(3), mount(8), diskutil(1) HISTORY
A umount command appeared in Version 6 AT&T UNIX. 4th Berkeley Distribution May 8, 1995 4th Berkeley Distribution
All times are GMT -4. The time now is 12:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy