Re: *URGENT* plz need help system not booting after "lvresize" command
On Thu, May 3, 2012 at 4:04 PM, Arnt Karlsen <arnt@c2i.net> wrote:
> On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
> <[🔎] CAGWVfMmXUZHb-wD=DRR0As-pMYig8qqsOFXY+UcnSMBsEd-SZQ@mail.gmail.com>:
>
>> On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen <arnt@c2i.net> wrote:
>> > On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
>> > <[🔎] CAGWVfM=mZy29_s0cUyv3GDZA=Czvmxg4h_q6DBuKRnbXVVzGLQ@mail.gmail.com>:
>> >
>> >> i tried every single possibility regarding cables i have 3 HD i
>> >> tried the smaller HDs cable it gives me the same error.
>> >
>> > ..good, means hardware failure. Try another machine.
>> >
>> >>
>> >> actually i also installed quota module by modeprobe qutoa_v2 and
>> >> echo qutoa_V2 >> /etc/moudels
>> >>
>> >> in fstab i added the UUID and ursquota keyword to for quota
>> >> support.
>> >>
>> >> and the next start was very unfortunate .
>> >>
>> >> actually it is showing me the error on the point where RAID md
>> >> devices are checked
>> >>
>> >> when i unpluged the problem drive it shows me md1 md2 and md0
>> >> status and after few logs it give me the problem but when plug
>> >> the drive back, on the stage where it suppose to show the SW raid1
>> >> status it shows me this error.
>> >>
>> >>
>> >> is there any possibility i can at least get the data back. i am
>> >> 100% sure it is not a hardware problem. it has some configuration
>> >> related problem.
>> >
>> > ..yes, and it could even be both. If your data is important,
>> > keep it safe and away from that machine until you know it is
>> > ok. E.g. flaky grid power can eat your power supply enough
>> > to e.g. kill a file system journal or leave it running on a
>> > read-only fs, force feeding you "interesting challenges."
>>
>> can you please make it easy what you have :P i am not that good in
>> english :-D
>
> ..like I said above, try your disks in _another_ machine.
>
>> what do you mean by readonly FS.
>
> ..mount each of your disks with e.g.
> "mount -vo,ro /dev/bad-disk.part0 /mnt".
>
>> and what do you mean by kill a file system.
>
> ..you can _destroy_ _all_ of your data if you do a fsck or if you
> do a normal mount, which is usually a read-write mount, where you
> risk having your possibly bad file system journal try to "repair"
> your file system.
>
> ..I've had this happen twice on my own, and once on a
> client fs in the early days of ext3. No, I have no
> experience with lvm.
>
>> i am a newbie can you make it easy please
>
> ..you asked for advice here on d-u@dlo. A wise start.
>
>> but right now the problem is command prompt.
>
> ..no. _If_ you want to use that machine with your disks,
> _first_ take your disks out of that machine, and _then_
> use a LiveCD or LiveUSB or some such to verify your machine
> is working ok, check ram, cpu, power supply _etc_, you
> probably have an hardware problem that caused your disk
> failures.
>
>> is there any way that
>> Debian just ignore the error and continue the boot and at least give
>> me the command prompt where i can just copy all the stuff to USB or
>> another drive.
>
> ..yes. Use a _working_ machine, one without bad hardware.
> You will find that _much_ easier, and _much_ cheaper than
> trying to mess with bad file systems on a blown up piece
> of junk.
>
right now i didnt had enough time to troubleshoot so i just started
recovering it from the backup disk. however i thought that it could be
the partition level issue. (i mean logical) but i was wrong i deleted
the partition via windows XP boot CD but still giving me the same
error which means that there is some thing with the hardware.anyways
bad luck. now constructing the whole thing again :(
Thanks,
>> but let me shre you. i tried PXE boot via with clonezilla and
>> different OS drives but keep giving me the same error and not letting
>> me use the command prompt.
>>
>> any idea?
>>
>> Thanks
>>
>>
>>
>>
>>
>> >
>> >>
>> >> Thanks
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, May 2, 2012 at 8:50 PM, Claudius Hubig
>> >> <debian_1205@chubig.net> wrote:
>> >> > Hello Muhammad,
>> >> >
>> >> > Muhammad Yousuf Khan <sirtcp@gmail.com> wrote:
>> >> >> ata3.01 : status: { DRDY ERR }
>> >> >> ata3.01 : error : { UNC }
>> >> >> ata3.01 : exception emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> >> >> ata3.01 : BMDMA stat 0x64
>> >> >> ata3.01 : failed command : read DMA
>> >> >
>> >> > This looks as if either the hard drive or the connection thereto
>> >> > is faulty. Try to connect the HDD to another SATA port. I don’t
>> >> > think it has anything to do with your resizing.
>> >> >
>> >> > Best regards & good luck,
>> >> >
>> >> > Claudius
>> >> > --
>> >> > Like I always say -- nothing can beat the BRATWURST here in
>> >> > DUSSELDORF!! http://chubig.net
>> >> > telnet nightfall.org 4242
>> >>
>> >>
>> >
>> >
>> > --
>> > ..med vennlig hilsen = with Kind Regards from Arnt Karlsen
>> > ...with a number of polar bear hunters in his ancestry...
>> > Scenarios always come in sets of three:
>> > best case, worst case, and just in case.
>> >
>> >
>> > --
>> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> > with a subject of "unsubscribe". Trouble? Contact
>> > listmaster@lists.debian.org Archive:
>> > [🔎] 20120502200712.18a5940a@celsius.lan">http://lists.debian.org/[🔎] 20120502200712.18a5940a@celsius.lan
>> >
>>
>
>
> --
> ..med vennlig hilsen = with Kind Regards from Arnt Karlsen
> ...with a number of polar bear hunters in his ancestry...
> Scenarios always come in sets of three:
> best case, worst case, and just in case.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: [🔎] 20120503130449.5633d526@celsius.lan">http://lists.debian.org/[🔎] 20120503130449.5633d526@celsius.lan
>
Reply to: