Linux Mint Forums

since the last three startups ive been met by a screen saying your disk drives are being checked for errors, this may take some time.
press c to cancel all checks currently in progress.

when i press c nothing happens.
when i press esc i get "All config files need .conf: /etc
/modprobe.d/blacklist, it will be ignored in a future release."
then something about /dev/sda4 and or sda3 being unmounted improperly.
i tried to do umount -l the devices but that just resulted in fluxbox crashing.

anyone got an idea? sorry for typing badly, im on my cell phone right now.

i just noticed when shutting the computer down that for a second when listing alot of stuff there was a red text that read failed, and before that "umount2 device or resource busy".. i dont know quite what to make of this.

Every 30 boots, Linux checks the disks (and by disks, it means partitions) for integrity of their file systems. If you cancel it, it should go away immediately but it will redo it the next time you boot, and keep trying until you let it complete. If it finds an error, it will ask what to do. Most of the time you can get away with telling it to fix it, but have your backups ready, just in case. If it fails, you would have to rebuild the partition using `fdisk(1)` and restore your data from backup.

It is possible to change the number from 30; it's part of GRUB, but I never tried it, so you have to research this on your own.

After step 2, it stops telling %age and what drive it's checking. So I let it go blindly for over 30 mins in that state, then pressed c. When I did that, it showed scanning disk 3 and ran very quickly 0-100%.
It still hasnt scanned now for 2 reboots, so maybe the problem is gone now.

Any ideas on why this occured?

No, none at all. Maybe things have changed since the last time I played around with it. Is disk 2 considerably bigger than disk 3? If not, I would suspect that disk 2 is on the edge of going belly-up.

Disk 2 is just another partition, I only have 1 physical disk.

The same problem occured this morning. When I shut down last night before going to bed I got one failed instance, Im pretty sure it was at the crypt disk blah blah row.

I dont even know what that is


Anyone, any ideas? Afaik I partitioned the disk one swap partition, one /-partition and one /home-partition. Nothing more. This problem hasnt occured before I also plugged in my cellphone via USB, and forgot it plugged in when booting. May this have anything to do with the problem?

When I pressed escape this time, trying to get out of the scans it said that /dev/sda3 and /dev/sda4 were not unmounted properly.

EDIT:
In the disk utility I just discovered that my /home-partition is 80GB, that one is /dev/sda3. My 40GB /home-partition is /dev/sda4.

So probably it has nothing to do with the phone then I suppose.

Still got the problem Pretty much every time I boot.
I still seem to get one red FAILED when shutting down.

post the output of thats a lower case L
or tell us the file system type ext3 ext4 .........if one of these 2 boot a live cd and run whare x is the # of he partition you want to check....... do all your ext3-4 partitions one at a time

VINNY

O and try to tell us exactly what it seas when you see the failed.

VINNY

First: Output of fdisk -l:

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x92aaed12

Device Boot Start End Blocks Id System
/dev/sda1 1 244 1951745 5 Extended
Partition 1 does not end on cylinder boundary.
/dev/sda2 244 256 97280 83 Linux
Partition 2 does not end on cylinder boundary.
/dev/sda3 256 9982 78125056 83 Linux
/dev/sda4 * 9982 14594 37045248 83 Linux
/dev/sda5 1 244 1951744 82 Linux swap / Solaris

My /home partition /dev/sda3 is ext2.
My / partition /dev/sda4 is also ext2.
A 100mb little partition called /dev/sda2 is ext4.


What it says when it fails:
umount2 device or resource is busy.
umount2 failed.

from a live cd/usb do as I sead above for /dev/sda3 and 4 ..then after open a terminal and do and see if you still get the umount error...........it may just be a problem with shutting down from a GUI

VINNY

I tried doing in a normal terminal, because of lack of boot cd where I'm at now.

Nothing failed! And it started up nicely after.

How do we interpret this?

crumpets wrote:I tried doing

Code: Select all

sudo shutdown -h 0

in a normal terminal, because of lack of boot cd where I'm at now.

Nothing failed! And it started up nicely after.

How do we interpret this?

that is hole nuther ball of wax......I think their was a similar prob for a wile in Kubuntu-10.04 or 10.10 through one of the sets of upgrades but is now fixed.......is your system all up to date?

and witch flavor of mint are you on?
for now keep shuting down like this untill a fix comes down the pipes or some one comes along with more

VINNY

Linux mint 9 fluxbox, just downloaded all updates via the manager yesterday. Are there any other updates avalible?

I got nothing against the console so it doesnt matter very much anyhow

The problem is back now, even when shutting down from the console It clearly says that /dev/sda3/ wasnt properly unmounted and that a check is forced.

Im thinking of just reinstalling. Obviously something is f'd up.

Anyone got any more ideas?

I figured something mightve been f'ed up with my partitions, and did a reinstall with only 2 partitions. One little swap and one big ext2.


First 5 or so reboots worked like a charm but now it's back

Anyone know if it may have anything to do with http://forums.linuxmint.com/viewtopic.p ... 63#p403863 ?