new error on boot up

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read this

new error on boot up

Postby silver on Tue Mar 31, 2009 9:55 am

I am running an acer aspire one. Netbook.

It is brand new. I installed Linux mint 6. Everything for the most part worked great. Although I haven't had an opportunity to check over everything.
But after two weeks of using it I have a problem.
First my hard drive is partitioned as such: |windowsxp-restore|windowsxp-boothome|2gbemptyspace|linuxmint|swapdrive|
I have the 160gb drive on my netbook.

Now the problem I am having is this. The other day when I was using my linuxmint the system locked up. So I powered down and then powered back up with the power button.
When I powered back up it won't boot. I can still boot the windowsxp part and that runs fine I did a scandisk in windows xp on the xp part and there were no errors.
So I booted up on a microsd card with mint6 and did a check disk on the linux mint part of the hard drive. And it didn't show me any errors. (I used the check disk in gparted).
The error I have is this.

[090105] ata1.00: status: [DRDY ERR]
[090168] ata1.00: error: [UNC]
[112946] ata1.00: configured for UDMA/133
[113049] ata1: EN complete
[367597] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[367689] ata1.00: BMDMA stat 0x5
[367750] ata1.00: cmd 25/00:60:1d:c5:21/00:00:11:00:00/e0 tag 0 dma

and the error just keeps going repeating for the most part.

any ideas as to what may have caused this and how I can boot back into my system?

Thanks for all the help and ideas

Ron
silver
Level 2
Level 2
 
Posts: 64
Joined: Thu Aug 30, 2007 6:32 pm
Location: Honduras

Linux Mint is funded by ads and donations.
 

Re: new error on boot up

Postby Husse on Wed Apr 01, 2009 6:41 am

So I powered down and then powered back up with the power button.

This is the cause
While it mostly is not dangerous it can cause problems if there is some writing going on to the disk at that time
You should have used the old reisub trick
Press AltGr and Printscr/Sysreq simultaneously and keep pressed Then key in REISUB - you get a safe reboot
Works always on any Linux (at least I think any)
There is a logical damage to the file system in Mint
Boot with your live CD
Do not mount any disk
Then run
Code: Select all
sudo e2fsck -f -c -v /dev/sda?

for the Mint partition - no other
Exchange sda? with whatever you have (I guess sda4)
I think you will see some messages about repairs
Caution - 32fsck is a powerful command - copy the line into terminal and change the ? there
(There is no ext3fsck :))
Image
Don't fix it if it ain't broken, don't break it if you can't fix it
Husse
Level 21
Level 21
 
Posts: 19714
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Re: new error on boot up

Postby silver on Wed Apr 01, 2009 1:37 pm

well I hope this command works with ext3 system.
I have it running and it's only on the first step which is read only test, it has 4.29% done and it has been working for 4 hours.
I don't know if it's normal for it to take so long. I hope so.

Will get back to you if and when it finishes
silver
Level 2
Level 2
 
Posts: 64
Joined: Thu Aug 30, 2007 6:32 pm
Location: Honduras

Re: new error on boot up

Postby silver on Wed Apr 01, 2009 9:00 pm

Up date
I'm at 4.42% and 11 hrs.

This is excruciating, i'm not sure but I think that most people wouldn't do this.

Not sure if I want to do this.
silver
Level 2
Level 2
 
Posts: 64
Joined: Thu Aug 30, 2007 6:32 pm
Location: Honduras

Re: new error on boot up

Postby silver on Thu Apr 02, 2009 8:25 am

Well that's that.

I'll be an old man before this is finished.
20+ hrs and only 4.64% done.
I just don't have the patients to see this through.

So reformat, reinstall is the answer for the day.

:)

But thanks anyway for the help.
Silver
silver
Level 2
Level 2
 
Posts: 64
Joined: Thu Aug 30, 2007 6:32 pm
Location: Honduras

Re: new error on boot up

Postby Husse on Thu Apr 02, 2009 12:45 pm

It should take less than five minutes on a 160 GB partition
The very long time it takes means severe logical damage so a format and reinstall is the thing to do - you'd never get fsck to fix it anyway
Image
Don't fix it if it ain't broken, don't break it if you can't fix it
Husse
Level 21
Level 21
 
Posts: 19714
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden


Return to Installation & Boot

Who is online

Users browsing this forum: austin.texas, claggan and 19 guests