Re: System not booting
On 17/06/15 02:42 PM, Peter Reid wrote: Hello, I recently rebooted my Debian 8 (Jessie) system, which I upgraded from Wheezy upon the release of Debian 8. I shutdown my system and restarted it, and the system does not appear to be 'booting'. *_Description:_* The system boots and responds to ping on both IPv4 and IPv6 interfaces, however no network facing services are starting (source: nmap); hence I cannot SSH into the server. *_Current Attempts to fix:_* I attempted to reboot once more (hard reboot from host control panel), that did not solve the issue. I have since rebooted into my provider's (SoYouStart by OVH) rescue mode, and have found some info in the logs that may be of use *_System information:_* Debian 8 ( had latest packages installed) - previously Debian 7 Processor: Intel Xeon(R) CPU W3520 @ 2.67GHz RAM: 16096MB HDD: 2 x 2000 GB in mdraid - RAID 1 MOBO: SuperMicro x8STI _Logs_ I'm really stuck with this issue, the only log I can think to provide is dmesg, the last few lines are as follows: [ 17.322135] Adding 523260k swap on /dev/sda4. Priority:-1 extents:1 across:523260k [ 17.323280] Adding 523260k swap on /dev/sdb4. Priority:-2 extents:1 across:523260k [ 17.360803] EXT4-fs (md2): re-mounted. Opts: (null) [ 17.589138] EXT4-fs (md2): re-mounted. Opts: errors=remount-ro [ 17.661897] loop: module loaded [ 20.080560] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null) [ 25.899123] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 29.069613] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 29.071646] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready *_Moving forward_* If any of you can be of assistance I would greatly appreciate it, I can provide log files upon request also. I would really like to get my system back on line as soon as possible, as I need it for my work next week. Thanks, Peter Reid You can ping but not ssh. This suggests that services are not being started. dmesg confirms this as nothing is showing up after the network is brought up. Since this seems to be a virtual machine, hooking up a monitor won't work. I had a similar problem on a real machine that seemed to be USB related and was fixed by upgrading to Jessie. In your case the reverse happened. Try changing your VM's hardware settings, removing something not absolutely necessary one piece at a time until you find what is causing the boot to hang. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5581c2ee.20...@torfree.net
Re: System not booting
On Wed, Jun 17, 2015 at 02:56:46PM -0400, Gary Dale wrote: You can ping but not ssh. This suggests that services are not being started. dmesg confirms this as nothing is showing up after the network is brought up. Hmm, no. My system has ssh running but there are no traces of ssh in dmesg at all. dmesg is only about kernel messages. ssh is userspace and it's logged elsewhere (for example, auth.log) My crazy ideas about what this could be: * A wrong /etc/fstab (systemd is picky about wrong lines in fstab). * Trying to use ssh with password with the user root after /etc/ssh/sshd_config has been updated to allow only public key. If the user is able to boot into rescue mode, adding a suitable /root/.ssh/authorized_keys should be easy. Since this seems to be a virtual machine, hooking up a monitor won't work. [...] Well, the cloud providers I've tested allow you to use a serial console where you can log into the system and use journalctl to see what happened, even if eth0 is down. I would try that. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617202111.ga16...@cantor.unex.es
Re: System not booting
Thanks Santiago, Issue fixed, bad record in fstab Thanks, Peter Reid Thanks, Peter Reid Web: http://reidweb.com Mobile: +44 78 5281 8850 On 17 June 2015 at 21:49, Peter Reid pe...@reidweb.com wrote: Hi, Good suggestions, I will try those out. However point to note: when I attempt to SSH with any set of credentials to the server, connection is being refused. Nmap of the server also suggests SSH is not running To me this would suggest that the OpenSSH service isn't even running on my server. I'll try the fstab suggestion and get back to you, that might be possible; I have edited it since my last reboot. Thanks, Peter Reid On 17 June 2015 at 21:21, Santiago Vila sanv...@unex.es wrote: On Wed, Jun 17, 2015 at 02:56:46PM -0400, Gary Dale wrote: You can ping but not ssh. This suggests that services are not being started. dmesg confirms this as nothing is showing up after the network is brought up. Hmm, no. My system has ssh running but there are no traces of ssh in dmesg at all. dmesg is only about kernel messages. ssh is userspace and it's logged elsewhere (for example, auth.log) My crazy ideas about what this could be: * A wrong /etc/fstab (systemd is picky about wrong lines in fstab). * Trying to use ssh with password with the user root after /etc/ssh/sshd_config has been updated to allow only public key. If the user is able to boot into rescue mode, adding a suitable /root/.ssh/authorized_keys should be easy. Since this seems to be a virtual machine, hooking up a monitor won't work. [...] Well, the cloud providers I've tested allow you to use a serial console where you can log into the system and use journalctl to see what happened, even if eth0 is down. I would try that. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617202111.ga16...@cantor.unex.es
System not booting
Hello, I recently rebooted my Debian 8 (Jessie) system, which I upgraded from Wheezy upon the release of Debian 8. I shutdown my system and restarted it, and the system does not appear to be 'booting'. *Description:* The system boots and responds to ping on both IPv4 and IPv6 interfaces, however no network facing services are starting (source: nmap); hence I cannot SSH into the server. *Current Attempts to fix:* I attempted to reboot once more (hard reboot from host control panel), that did not solve the issue. I have since rebooted into my provider's (SoYouStart by OVH) rescue mode, and have found some info in the logs that may be of use *System information:* Debian 8 ( had latest packages installed) - previously Debian 7 Processor: Intel Xeon(R) CPU W3520 @ 2.67GHz RAM: 16096MB HDD: 2 x 2000 GB in mdraid - RAID 1 MOBO: SuperMicro x8STI *Logs* I'm really stuck with this issue, the only log I can think to provide is dmesg, the last few lines are as follows: [ 17.322135] Adding 523260k swap on /dev/sda4. Priority:-1 extents:1 across:523260k [ 17.323280] Adding 523260k swap on /dev/sdb4. Priority:-2 extents:1 across:523260k [ 17.360803] EXT4-fs (md2): re-mounted. Opts: (null) [ 17.589138] EXT4-fs (md2): re-mounted. Opts: errors=remount-ro [ 17.661897] loop: module loaded [ 20.080560] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null) [ 25.899123] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 29.069613] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 29.071646] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready *Moving forward* If any of you can be of assistance I would greatly appreciate it, I can provide log files upon request also. I would really like to get my system back on line as soon as possible, as I need it for my work next week. Thanks, Peter Reid
Re: System not booting
Hi, Good suggestions, I will try those out. However point to note: when I attempt to SSH with any set of credentials to the server, connection is being refused. Nmap of the server also suggests SSH is not running To me this would suggest that the OpenSSH service isn't even running on my server. I'll try the fstab suggestion and get back to you, that might be possible; I have edited it since my last reboot. Thanks, Peter Reid On 17 June 2015 at 21:21, Santiago Vila sanv...@unex.es wrote: On Wed, Jun 17, 2015 at 02:56:46PM -0400, Gary Dale wrote: You can ping but not ssh. This suggests that services are not being started. dmesg confirms this as nothing is showing up after the network is brought up. Hmm, no. My system has ssh running but there are no traces of ssh in dmesg at all. dmesg is only about kernel messages. ssh is userspace and it's logged elsewhere (for example, auth.log) My crazy ideas about what this could be: * A wrong /etc/fstab (systemd is picky about wrong lines in fstab). * Trying to use ssh with password with the user root after /etc/ssh/sshd_config has been updated to allow only public key. If the user is able to boot into rescue mode, adding a suitable /root/.ssh/authorized_keys should be easy. Since this seems to be a virtual machine, hooking up a monitor won't work. [...] Well, the cloud providers I've tested allow you to use a serial console where you can log into the system and use journalctl to see what happened, even if eth0 is down. I would try that. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617202111.ga16...@cantor.unex.es
Re: *URGENT* plz need help system not booting after lvresize command
ok finally, recovering the data from old drive :(.. recovering data is not a big deal however creating the same directory infrastructure . rights assigning and stuff is pain .. Thanks for the support. On Thu, May 3, 2012 at 1:24 AM, Muhammad Yousuf Khan sir...@gmail.com wrote: On Thu, May 3, 2012 at 12:31 AM, Claudius Hubig debian_1...@chubig.net wrote: Hello Muhammad, Muhammad Yousuf Khan sir...@gmail.com wrote: at least there should be a way to reach the command prompt. is there any way to ignore this error and reach the command prompt so i can just copy the necessary data. Probably not, because this error means that accessing whatever is attached to the third SATA port is somehow broken. You did not answer my previous questions: 1) Do other HDD work at this SATA port? actually i didnt check the SATA port however i change the working HD SATA port as i already share i have multiple drives in a box so the drive is showing the same error which shows that problem is not with sata 2) How does this HDD behave at another SATA port, preferably in another computer? You could also try to get an external enclosure and connect the HDD during runtime. ok ill try this external case suggestion However, I highly doubt that you can ‘just copy’ the necessary data of this drive. lets hope for the best. however i do have the copy but have to do lots and lots of work. which i hate now :( Best regards, Claudius PS: Please do not CC me. -- There cannot be a crisis next week. My schedule is already full. -- Henry Kissinger http://chubig.net telnet nightfall.org 4242 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmmxgfatjwsvpqdfaku5koih+sujyctkrgdboapnena...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
CAGWVfMmXUZHb-wD=drr0as-pmyig8qqsofxy+ucnsmbsed-...@mail.gmail.com:
On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen a...@c2i.net wrote:
On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@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.
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_1...@chubig.net wrote:
Hello Muhammad,
Muhammad Yousuf Khan sir...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org Archive:
http://lists.debian.org/20120502200712.18a59...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120503130449.5633d...@celsius.lan
Re: *URGENT* plz need help system not booting after lvresize command
On Thu, May 3, 2012 at 4:04 PM, Arnt Karlsen a...@c2i.net wrote:
On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
CAGWVfMmXUZHb-wD=drr0as-pmyig8qqsofxy+ucnsmbsed-...@mail.gmail.com:
On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen a...@c2i.net wrote:
On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@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_1...@chubig.net wrote:
Hello Muhammad,
Muhammad Yousuf Khan sir...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org Archive:
http://lists.debian.org/20120502200712.18a59...@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
Re: *URGENT* plz need help system not booting after lvresize command
On Thu, 3 May 2012 17:29:06 +0500, Muhammad wrote in message CAGWVfM=FA6TRQeHjGSQJTkkddt9s8QnNbARrb=rmzwhssiq...@mail.gmail.com: On Thu, May 3, 2012 at 4:04 PM, Arnt Karlsen a...@c2i.net wrote: On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message CAGWVfMmXUZHb-wD=drr0as-pmyig8qqsofxy+ucnsmbsed-...@mail.gmail.com: On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen a...@c2i.net wrote: On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@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, ..well, it could have been worse, imagine if you didn't have a back-up. ;o) -- ..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-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120503162339.78a37...@celsius.lan
*URGENT* plz need help system not booting after lvresize command
i resize the LV from 300 GB to 400 GB
then i ran the listed commands
e2fsck -f /dev/mapper/vg--800-Archive400GB
resize2fs -p /dev/mapper/vg--800-Archive400GB
now when i reboot the system
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
my system is not booting up.giving me lots and lots of above erros.
no matter what i do it doesnt give me the prompt. it is continuesly
giving me this error. i tried recovery mod NO LUCK.
it worked when i unplug the 800GB drive, things start working fine via
default boot drives. however, i tried bootable CD. it shows the same
error
and i # all the partitions mount point that has been located on the
said drive. but still can not get the prompt.
PLease help, data is very important.
Thanks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cagwvfmniu6uxyvaar973edfygpaextlcfghuvh1zvmct1x1...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
On Wed, May 02, 2012 at 08:45:25PM +0500, Muhammad Yousuf Khan wrote: i resize the LV from 300 GB to 400 GB Exactly what command did you type, and what feedback did you get? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120502154926.GA6770@debian
Re: *URGENT* plz need help system not booting after lvresize command
Hello Muhammad,
Muhammad Yousuf Khan sir...@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.nettelnet nightfall.org 4242
signature.asc
Description: PGP signature
Re: *URGENT* plz need help system not booting after lvresize command
sorry, if i am miss leading with the error . actually i belive that this must have happen. by the lvresize command. actually every thing was working nice and smooth. here is the quick story. first i ran the command. 1. i resize the old partition lvresize -L 400GB VG-NAME with PATH 2 then i ran resize command resize2fs -p /dev/mapper/vg--800-Archive400GB but gives me error and tells me to run e2fsck -f 3. so i rant e2fsck -f /dev/mapper/vg--800-Archive400GB which was fine and even vg display and df -h showing the same size so i got relaxed that things are fine. 4. then i created another one for quota assignment to all the users lvcreate -L 245GB VG-NAME AND path-n name then i transfer the ext4 file system to it. i dont remeber the command but it was something.ext4 lv complete path 5 and i enabled the quota in fstab alog with the UUID to mount it on boot. 6. then i enabled kernal moudule. modprob qutoa_v2 echo qutoa_v2 /etc/modules (do you think it could be the module issue?) 7. for testing i mount the drive by mount usrquota source path mount point so it worked find . .. now next reboot problem started. thats the whole story.. Thanks On Wed, May 2, 2012 at 8:49 PM, Jon Dowland j...@debian.org wrote: On Wed, May 02, 2012 at 08:45:25PM +0500, Muhammad Yousuf Khan wrote: i resize the LV from 300 GB to 400 GB Exactly what command did you type, and what feedback did you get? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120502154926.GA6770@debian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfM=Tq_oTKZd5S4Sf3a80kXTqP5GhFY1i5Z4=abxajcn...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
i tried every single possibility regarding cables i have 3 HD i tried
the smaller HDs cable it gives me the same error.
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.
Thanks
On Wed, May 2, 2012 at 8:50 PM, Claudius Hubig debian_1...@chubig.net wrote:
Hello Muhammad,
Muhammad Yousuf Khan sir...@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
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
at least there should be a way to reach the command prompt. is there any way to ignore this error and reach the command prompt so i can just copy the necessary data. Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmk8gjw_rolcbzyav9zk2c4+xtjjqrpguvyoev3w+ke...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@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.
Thanks
On Wed, May 2, 2012 at 8:50 PM, Claudius Hubig
debian_1...@chubig.net wrote:
Hello Muhammad,
Muhammad Yousuf Khan sir...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120502200712.18a59...@celsius.lan
Re: *URGENT* plz need help system not booting after lvresize command
On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen a...@c2i.net wrote:
On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
CAGWVfM=mZy29_s0cUyv3GDZA=czvmxg4h_q6dbukrnbxvvz...@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
what do you mean by readonly FS. and what do you mean by kill a file system.
i am a newbie can you make it easy please
but right now the problem is command prompt. 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.
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_1...@chubig.net wrote:
Hello Muhammad,
Muhammad Yousuf Khan sir...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120502200712.18a59...@celsius.lan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAGWVfMmXUZHb-wD=drr0as-pmyig8qqsofxy+ucnsmbsed-...@mail.gmail.com
Re: *URGENT* plz need help system not booting after lvresize command
On Wed, May 2, 2012 at 12:28 PM, Muhammad Yousuf Khan sir...@gmail.comwrote: On Wed, May 2, 2012 at 10:49 PM, Shane Johnson s...@rasmussenequipment.com wrote: Muhammad, I think we are going to need some mere information please. You mentioned that this is on a raid, correct. Is your lvm on top of the raid? Which level of raid? i am using RAID 1 Where is your /boot mounted or / if boot isn't on it's own partition. i have two drives 320 GB boot 1 GB and / (rest of the drive) are on md0 and md 2\ sawp md1 (4gb) i have 1 800 GB drive RAID 1 but other drive was absent i was planing to add the other drive in array in few days but unfortunately this things happen Things I have done in the past, is use a Live CD for same can you please give me the path of debian live CD iso. actually i was trying to boot my system with clonzilla live CD lets see if debian can help. version and arch of Debian you are on and if necessary install mdadm and lvm2 so that I could try and reconstruct what I had before. Luckily for me, I was one test systems when I buggered things up too much. It sounds like you are on a live system- that makes things harder. Best of the Worst case scenarios from my limited experience would be having to restore from backups. If you don't have good backups its the worst of the worst and you could end up doing a complete restore from scratch). On Wed, May 2, 2012 at 11:37 AM, Muhammad Yousuf Khan sir...@gmail.com wrote: at least there should be a way to reach the command prompt. is there any way to ignore this error and reach the command prompt so i can just copy the necessary data. Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmk8gjw_rolcbzyav9zk2c4+xtjjqrpguvyoev3w+ke...@mail.gmail.com -- Shane D. Johnson IT Administrator Rasmussen Equipment The path to the CD downloads is http://www.debian.org/CD/ Pick you poison on how you want to download it. If I am understanding your situation correctly, you have 3 disks. 2 320GB disks are mirrored for md0 and then you have your LVM on top of that. Then you have disk 3 as swap (md1). Where you had the mirror active when you where trying to resize the corruption would probably be on both disks. I would use the live cd and look at each one separately and see if the filesystems on both are the new size or the old. If you have one that is ok, you can use mdadm to drop the bad disk from the raid then add it back later after you system boots from the good disk so that it becomes the mirror of the good drive. Otherwise you are going to have to try and use the live cd to try and get to your data. Reconstruct your system then put back the data you can. If you aren't using mdadm for your raid and just using LVM then you will access the fstab on the system and point it to the mirrored drive if it is still good. Good luck Mohammud. Shane
Re: *URGENT* plz need help system not booting after lvresize command
Hello Muhammad, Muhammad Yousuf Khan sir...@gmail.com wrote: at least there should be a way to reach the command prompt. is there any way to ignore this error and reach the command prompt so i can just copy the necessary data. Probably not, because this error means that accessing whatever is attached to the third SATA port is somehow broken. You did not answer my previous questions: 1) Do other HDD work at this SATA port? 2) How does this HDD behave at another SATA port, preferably in another computer? You could also try to get an external enclosure and connect the HDD during runtime. However, I highly doubt that you can ‘just copy’ the necessary data of this drive. Best regards, Claudius PS: Please do not CC me. -- There cannot be a crisis next week. My schedule is already full. -- Henry Kissinger http://chubig.net telnet nightfall.org 4242 signature.asc Description: PGP signature
Re: *URGENT* plz need help system not booting after lvresize command
On Thu, May 3, 2012 at 12:31 AM, Claudius Hubig debian_1...@chubig.net wrote: Hello Muhammad, Muhammad Yousuf Khan sir...@gmail.com wrote: at least there should be a way to reach the command prompt. is there any way to ignore this error and reach the command prompt so i can just copy the necessary data. Probably not, because this error means that accessing whatever is attached to the third SATA port is somehow broken. You did not answer my previous questions: 1) Do other HDD work at this SATA port? actually i didnt check the SATA port however i change the working HD SATA port as i already share i have multiple drives in a box so the drive is showing the same error which shows that problem is not with sata 2) How does this HDD behave at another SATA port, preferably in another computer? You could also try to get an external enclosure and connect the HDD during runtime. ok ill try this external case suggestion However, I highly doubt that you can ‘just copy’ the necessary data of this drive. lets hope for the best. however i do have the copy but have to do lots and lots of work. which i hate now :( Best regards, Claudius PS: Please do not CC me. -- There cannot be a crisis next week. My schedule is already full. -- Henry Kissinger http://chubig.net telnet nightfall.org 4242 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAGWVfMk2tYsCejSA6ZemZE2O1W2jJ2Ymºnpvocb7b1nbt...@mail.gmail.com
