Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ.
I have a brand new 2T external Samsung SSD disk. (two of them) for backup.
I tried the first one and had an issue, I tried the second one and got the
same issue.
Am I doing something wrong ? I find it hard to believe the SSD (both) are
bad.
I plugged in the USB 3.1 adapter, I fdisk /dev/sdd, n,
Do you have any "history" with the adapter you connected them to? If not
consider it as a possibility as well (from bad experience of total
filesystem/partition corruption on two hard drives only to discover it was
something on the motherboard).
Leroy Tennison
Network Information/Cyber Securi
>Do you have any "history" with the adapter you connected them to? If not
consider it as a possibility as well
>(from bad experience of total filesystem/partition corruption on two hard
drives only to discover it was >something on the motherboard).
Actually yes I used them many times back on C7.5
> Am 12.12.2018 um 14:49 schrieb Jerry Geis :
>
> Am I doing something wrong ? I find it hard to believe the SSD (both) are
> bad.
>
I would check the integrity of this storage device:
# Notice: this destroys your data on the device
badblocks -c 10240 -s -w -t random -v /dev/sdxx
--
LF
_
On Wed, 12 Dec 2018 at 09:14, Jerry Geis wrote:
>
> >Do you have any "history" with the adapter you connected them to? If not
> consider it as a possibility as well
> >(from bad experience of total filesystem/partition corruption on two hard
> drives only to discover it was >something on the moth
>What kind of solid state 2 TB drive is this and how is it 'powered'?
>It is looking like the drives aren't getting completely written to
>before being removed as the ext4 error is a 'oh wait this drive
>doesn't have everything I expected too late to give up aah'
>type oops
This is a Samsu
Jerry Geis wrote:
>> Do you have any "history" with the adapter you connected them to? If
>> not consider it as a possibility as well
>> (from bad experience of total filesystem/partition corruption on two
>> hard drives only to discover it was >something on the motherboard).
>
> Actually yes I us
On Wed, 12 Dec 2018 at 11:38, Jerry Geis wrote:
>
> >What kind of solid state 2 TB drive is this and how is it 'powered'?
> >It is looking like the drives aren't getting completely written to
> >before being removed as the ext4 error is a 'oh wait this drive
> >doesn't have everything I expected t
>I'm a tad confused: you said the USB drive was brand new - did you use
>them with C 7.5, or not? Can you try to do a b/u using whatever drive you
>used before?
All the equipment I had before... Motherboard, cable etc... the drives
are new and this is the behaviour I was seeing...
I am currentl
I'm new to SFTP and using this mailing list was able to successfully create
my first Private/Public keyset for a vendor hosting the SFTP server (I'm the
client). I created the keyset by typing this:
# ssh-keygen -t rsa
When asked for the password/passphrase I hit and afterwards "id_rsa"
a
On 12/12/2018 03:13 PM, Gary Braatz wrote:
> I'm new to SFTP and using this mailing list was able to successfully create
> my first Private/Public keyset for a vendor hosting the SFTP server (I'm the
> client). I created the keyset by typing this:
>
>
>
> # ssh-keygen -t rsa
>
>
>
> When asked
Thanks for responding so quickly! No but I will try. Are you saying the
first vendor connection worked because id_rsa and id_rsa.pub are the
defaults if not specified? (I didn't use the -i flag for the first vendor.)
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On
On 12/12/2018 03:28 PM, Gary Braatz wrote:
> Thanks for responding so quickly! No but I will try. Are you saying the
> first vendor connection worked because id_rsa and id_rsa.pub are the
> defaults if not specified? (I didn't use the -i flag for the first vendor.)
>
>
> -Original Message---
On 12/12/2018 03:32 PM, Steve Clark wrote:
> On 12/12/2018 03:28 PM, Gary Braatz wrote:
>> Thanks for responding so quickly! No but I will try. Are you saying the
>> first vendor connection worked because id_rsa and id_rsa.pub are the
>> defaults if not specified? (I didn't use the -i flag for t
Thank You Sir! The vendor is working on this as well and I believe may have
just changed the password. The one I was using is no longer working (it
worked a few minutes ago). I'll update you later on my progress.
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Beh
Inclusion of the -i flag and the location of the private key solved the
problem.
Thanks Steve!
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Steve Clark
Sent: Wednesday, December 12, 2018 2:38 PM
To: CentOS mailing list
Subject: Re: [CentOS] SFTP - Privat
On a support forum, I was told that to turn off my board's blue led run:
echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger
Well, this does not survive a system reboot. So I was told:
Add the off bit to
/etc/rc.local
Add it above "exit 0"
So of course, CentOS is past using rc.
Does your version of CentOS have the @reboot crontab option? If it does this
is probably easier unless you want to learn how to write systemd files.
Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TTh
On 12/12/18 7:11 PM, Leroy Tennison wrote:
Does your version of CentOS have the @reboot crontab option? If it does this
is probably easier unless you want to learn how to write systemd files.
CentOS 7.6. I will have to google @reboot...
Leroy Tennison
Network Information/Cyber Security
if it's Centos/RHEL 7, you can turn it into a service that starts after
boot too, and cintrol it with systemctl.
On 12/12/18 5:04 PM, Robert Moskowitz wrote:
On a support forum, I was told that to turn off my board's blue led run:
echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger
> Date: Wednesday, December 12, 2018 20:25:48 -0500
> From: Robert Moskowitz
>
>
> On 12/12/18 7:11 PM, Leroy Tennison wrote:
>> Does your version of CentOS have the @reboot crontab option? If
>> it does this is probably easier unless you want to learn how to
>> write systemd files.
>
> Cent
On 12/12/18 9:17 PM, Richard wrote:
Date: Wednesday, December 12, 2018 20:25:48 -0500
From: Robert Moskowitz
On 12/12/18 7:11 PM, Leroy Tennison wrote:
Does your version of CentOS have the @reboot crontab option? If
it does this is probably easier unless you want to learn how to
write sy
Hi,
I am running CentOS Linux release 7.6.1810 (Core) with ClamAV installed.
When i am running freshclam i am seeing a Warning message and the details
are described below:-
# freshclam
ClamAV update process started at Thu Dec 13 11:49:18 2018
WARNING: Your ClamAV installation is OUTDATED!
WARNING
24 matches
Mail list logo
