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 wrote:
> Hi,
>
> Good suggestions, I will try those out.
>
> However point to note: when I attempt to SSH with any se
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.
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
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
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
On Thu, 3 May 2012 17:29:06 +0500, Muhammad wrote in message
:
> On Thu, May 3, 2012 at 4:04 PM, Arnt Karlsen wrote:
> > On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
> > :
> >
> >> On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen wrote:
> >> > On Wed, 2 May 2012 22:07:14 +0500, Muh
On Thu, May 3, 2012 at 4:04 PM, Arnt Karlsen wrote:
> On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
> :
>
>> On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen wrote:
>> > On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
>> > :
>> >
>> >> i tried every single possibility reg
On Wed, 2 May 2012 23:56:06 +0500, Muhammad wrote in message
:
> On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen wrote:
> > On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
> > :
> >
> >> i tried every single possibility regarding cables i have 3 HD i
> >> tried the smaller HDs cable i
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 wrote:
> On Thu, May 3, 2
On Thu, May 3, 2012 at 12:31 AM, Claudius Hubig wrote:
> Hello Muhammad,
>
> Muhammad Yousuf Khan 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,
Hello Muhammad,
Muhammad Yousuf Khan 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 th
On Wed, May 2, 2012 at 12:28 PM, Muhammad Yousuf Khan wrote:
> On Wed, May 2, 2012 at 10:49 PM, Shane Johnson
> 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
On Wed, May 2, 2012 at 11:07 PM, Arnt Karlsen wrote:
> On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
> :
>
>> 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 m
On Wed, 2 May 2012 22:07:14 +0500, Muhammad wrote in message
:
> 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 modepro
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 listm
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 ne
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
Hello Muhammad,
Muhammad Yousuf Khan 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 theret
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 l
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
20 matches
Mail list logo
