Re: [CentOS] External harddisk

[H]

On October 1, 2020 12:03:34 PM EDT, Bruce Ferrell  wrote:
>On 9/30/20 9:11 AM, H wrote:
>> On 09/30/2020 12:03 PM, Simon Matter wrote:
 Since you have taken the disk apart it will now be useless as
>within the
 enclosure there could have been a vacuum or an inert gas.
>>>  From what I know gas filled disks didn't exist in the times when
>3X0GB was
>>> on a 2" drive.
>>>
 You will never be able to recover any data on the disk unless you
>go and
 pay
 for a professional data recovery organisation to read the platters.
>>> No, if he did care that the disks didn't become dirty then the drive
>>> should still work quite well to recover what is on it. Of course the
>cover
>>> should be put on ASAP. If you don't believe me, just try it our
>yourself.
>>>
 The price for a replacement 340GByte USB disk is about $25 which
>would
 give
 you a better product than your old disk.
>>> The OP wanted to recover what is on the disk, not use it as a normal
>disk.
>>>
>>> Simon
>>>
 Mark

 -Original Message-
 From: H
 Sent: Wednesday, September 30, 2020 4:47 PM
 To: centos@centos.org
 Subject: Re: [CentOS] External harddisk

 On 09/30/2020 05:40 AM, John Pierce wrote:
> On Tue, Sep 29, 2020, 8:33 AM H  wrote:
>
>> I have an old external harddisk, Toshiba 320 Gb, with a USB
>connector
>> that
>> I wanted to check for contents. It did not start up when
>connected and
>> I
>> could not hear the motor spinning. After leaving it in the
>freezer
>> overnight the motor spins but it is not recognized by my
>computer. I
>> disassembled it and could see that the head assembly rests
>outside the
>> disk
>> but when it is powered on, the head first moves to the center of
>the
>> disk,
>> then to the periphery and finally back to the resting position.
>This
>> happens every few seconds and leaving it connected overnight
>changed
>> nothing.
>>
> That repeated seeking suggests it's not passing its self test, and
>is
> constantly retrying.   It's probably searching for servo data on
>the
> disks,
> and not finding it.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
 I see. I have not searched for any low-level disk utility from
>Toshiba,
 the
 manufacturer of the disk. Do you think that might be worthwhile to
 hopefully
 fix this?

 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos

>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>> Simon, you are correct in all the above and I replaced the cover as
>soon as I had ascertained the movements of the head assembly.
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>
>Opening up disk drives outside of a lab environment is NEVER a good
>idea if you expect the device to be useful.
>
>I'm thinking this disk problem is tied to your more general usb
>problem.
>
>There is a guy with a shop in NYC called Louis Rossmann who MAY be able
>to help with your data recovery.  Look him up on youtube or just google
>the name.
>
>___
>CentOS mailing list
>CentOS@centos.org
>https://lists.centos.org/mailman/listinfo/centos

No. I tried this disk on other computers and it has nothing to do with USB. 
Further, I have other similar disks which do work on this computer.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Logitech C922 webcam

[H]

On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell  wrote:
>On 9/30/20 8:52 AM, H wrote:
>> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
>Family USB 3.0 xHCI Controller
>My system has these:
>
>00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB xHCI (rev 05)
>00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB EHCI #2 (rev 05)
>00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB EHCI #1 (rev 05)
>
>lspci -s 00:14.0 -v
>00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB xHCI (rev 05) (prog-if 30 [XHCI])
>     Subsystem: ASUSTeK Computer Inc. Device 201f
>     Flags: bus master, medium devsel, latency 0, IRQ 25
>     Memory at dd60 (64-bit, non-prefetchable) [size=64K]
>     Capabilities: [70] Power Management version 2
>     Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
>     Kernel driver in use: xhci_hcd
>     Kernel modules: xhci_pci
>
>lspci -s 00:1a.0 -v
>00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI])
>     Subsystem: ASUSTeK Computer Inc. Device 201f
>     Flags: bus master, medium devsel, latency 0, IRQ 16
>     Memory at dd618000 (32-bit, non-prefetchable) [size=1K]
>     Capabilities: [50] Power Management version 2
>     Capabilities: [58] Debug port: BAR=1 offset=00a0
>     Capabilities: [98] PCI Advanced Features
>     Kernel driver in use: ehci-pci
>     Kernel modules: ehci_pci
>
>lspci -s 00:1d.0 -v
>00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI])
>     Subsystem: ASUSTeK Computer Inc. Device 201f
>     Flags: bus master, medium devsel, latency 0, IRQ 23
>     Memory at dd617000 (32-bit, non-prefetchable) [size=1K]
>     Capabilities: [50] Power Management version 2
>     Capabilities: [58] Debug port: BAR=1 offset=00a0
>     Capabilities: [98] PCI Advanced Features
>     Kernel driver in use: ehci-pci
>     Kernel modules: ehci_pci
>
>These are my kernel modules:
>
>lsmod | grep usb
>btusb  53248  0
>btrtl  16384  1 btusb
>btbcm  16384  1 btusb
>btintel    20480  1 btusb
>bluetooth 589824  41 btrtl,btintel,bnep,btbcm,rfcomm,btusb
>snd_usb_audio 278528  1
>snd_usbmidi_lib    36864  1 snd_usb_audio
>snd_hwdep  16384  2 snd_hda_codec,snd_usb_audio
>snd_rawmidi    40960  1 snd_usbmidi_lib
>snd_pcm   143360  5
>snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi
>snd    98304  23 
>snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm
>usbhid 57344  0
>usbcore   290816  9
>uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
>
>
>This line is important:
>
>usbcore   290816  9
>uvcvideo,usbhid,snd_usb_audio,ehci_hcd,xhci_pci,snd_usbmidi_lib,btusb,xhci_hcd,ehci_pci
>
>Notice the last two entries:  xhci_hcd and ehci_pci
>
>Those correspond to:
>
>   for my two usb 2 controllers:
>
>     Kernel driver in use: xhci_hcd
>     Kernel modules: xhci_pci
>
>   for my single usb 3 controller:
>
>     Kernel driver in use: xhci_hcd
>     Kernel modules: xhci_pci
>
>
>from your lspci:
>
>00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset
>Family USB 3.0 xHCI Controller
>
>This is the sole USB controller in your system and it's a USB 3
>controller
>
>so... in your case let's do:
>
>sudo lspci -s 00:14.0 -v
>
>then try:
>
>sudo modprobe usbcore
>
>and repeat:
>
>sudo lspci -s 00:14.0 -v
>
>see if the Kernel driver/module lines change.  If they do, plug the
>camera in and check for it to be recognized in lsusb
>
>
>
>
>___
>CentOS mailing list
>CentOS@centos.org
>https://lists.centos.org/mailman/listinfo/centos

Thank you. Unfortunately I will not have access to this computer for some time, 
will let you know when I can try what you suggest.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] No sound after latest Firefox update (firefox-78.3.0-1.el6.centos.x86_64)

[Robert Nichols]

On 10/1/20 3:24 PM, Jonathan Billings wrote:

On Thu, Oct 01, 2020 at 04:01:29PM -0400, mailist wrote:

The Ubuntu-derived distros are much better suited to desktop.  I run several
of them, as well as
CentOS 7 and 8.  Ubuntu, Kubuntu (Ubuntu with KDE), Lubuntu, Debian, PopOS,
and Zorin.


They all use systemd.  If you're running CentOS 6 to avoid that,
you're out of luck.


I can live with systemd. It's the Gnome 3 UI that I can't stand. I gave
Mate a try briefly, but ran into some issues that I don't recall just
now. I'll give it another try, but I may just give up and switch to
Mint. The major issue for my doing that is the package manager, since
I have several custom packages that are RPMs.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] External harddisk

[Leroy Tennison]

I don't know whether testdisk would be helpful in this case or not but your 
options are limited, might give it a try.

From: CentOS  on behalf of H 
Sent: Friday, October 2, 2020 6:40 AM
To: CentOS mailing list 
Subject: [EXTERNAL] Re: [CentOS] External harddisk

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


On October 1, 2020 12:03:34 PM EDT, Bruce Ferrell  wrote:
>On 9/30/20 9:11 AM, H wrote:

Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
P:


[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]


2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com


This message has been sent on behalf of a company that is part of the Harris 
Operating Group of Constellation Software Inc.

If you prefer not to be contacted by Harris Operating Group please notify 
us.



This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential or otherwise legally exempt from disclosure. If you 
are not the named addressee, you are not authorized to read, print, retain, 
copy or disseminate this message or any part of it. If you have received this 
message in error, please notify the sender immediately by e-mail and delete all 
copies of the message.





>> On 09/30/2020 12:03 PM, Simon Matter wrote:
 Since you have taken the disk apart it will now be useless as
>within the
 enclosure there could have been a vacuum or an inert gas.
>>>  From what I know gas filled disks didn't exist in the times when
>3X0GB was
>>> on a 2" drive.
>>>
 You will never be able to recover any data on the disk unless you
>go and
 pay
 for a professional data recovery organisation to read the platters.
>>> No, if he did care that the disks didn't become dirty then the drive
>>> should still work quite well to recover what is on it. Of course the
>cover
>>> should be put on ASAP. If you don't believe me, just try it our
>yourself.
>>>
 The price for a replacement 340GByte USB disk is about $25 which
>would
 give
 you a better product than your old disk.
>>> The OP wanted to recover what is on the disk, not use it as a normal
>disk.
>>>
>>> Simon
>>>
 Mark

 -Original Message-
 From: H
 Sent: Wednesday, September 30, 2020 4:47 PM
 To: centos@centos.org
 Subject: Re: [CentOS] External harddisk

 On 09/30/2020 05:40 AM, John Pierce wrote:
> On Tue, Sep 29, 2020, 8:33 AM H  wrote:
>
>> I have an old external harddisk, Toshiba 320 Gb, with a USB
>connector
>> that
>> I wanted to check for contents. It did not start up when
>connected and
>> I
>> could not hear the motor spinning. After leaving it in the
>freezer
>> overnight the motor spins but it is not recognized by my
>computer. I
>> disassembled it and could see that the head assembly rests
>outside the
>> disk
>> but when it is powered on, the head first moves to the center of
>the
>> disk,
>> then to the periphery and finally back to the resting position.
>This
>> happens every few seconds and leaving it connected overnight
>changed
>> nothing.
>>
> That repeated seeking suggests it's not passing its self test, and
>is
> constantly retrying.   It's probably searching for servo data on
>the
> disks,
> and not finding it.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
 I see. I have not searched for any low-level disk utility from
>Toshiba,
 the
 manufacturer of the disk. Do you think that might be worthwhile to
 hopefully
 fix this?

 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos

>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>> Simon, you are correct in all the above and I replaced the cover as
>soon as I had ascertained the movements of the head assembly.
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>
>Opening up disk drives outside of a lab environment is NEVER a good
>idea if you expect the device to be useful.
>
>I'm thinking this disk problem is tied to your more general usb
>problem.
>
>There is a guy with a shop in NYC c

Re: [CentOS] Laptop display issue

[H]

On October 1, 2020 3:42:34 PM EDT, H  wrote:
>I now have an older laptop with a display problem. I installed Centos 7
>on it in February and had to install the xorg-x11-drv-ati and evdev
>drivers because the docking station has an ATI Radeon card. Everything
>worked fine with a dual display setup. I probably after that ran a
>system update but did not reboot while in this office. Today, when I
>got to the office again for the first time in seven months it does not
>boot into the desktop but fails after displaying ”Started Light Display
>Manager” with a mouse pointer on one display that can be moved but no
>desktop at all. The keyboard works and I can start a terminal session.
>
>If I remove the laptop from the docking station everything works as
>expected but not in the station, presumably because it now uses the
>docking station card. Futzing around I see that systemctl --failed
>lists nothing, nor did dmesg immediately suggest a reason. In the yum
>history I see that this driver was updated to 19.0.1-3 from the
>19.0.1-2 that installed with. Yum downgrade to 19.0.1-2 did not change
>the issue. Nor has booting an older kernel helped so far.
>
>Although when I remove quiet from the grub command line it seems to
>stop after ”Started Load CPU microcode update” following the ”Started
>Light Display Manager” already mentioned, I strongly suspect some issue
>with the graphics driver.
>
>Since the computer boots and seems to run fine with the internal
>display when removed from the docking station it seems that there are
>no hardware issues in the unit itself. My understanding is that the ATI
>driver can be a problem and needs to match the kernel etc - perhaps
>there is something wrong here?
>
>Any suggestions for how to attack this? I need to use it in the docking
>station and have no alternative. Thank you.

Researching this further, the issue seems to be with x11. I found that blindly 
typing my password to log into the system seems to log me in and launches the 
expected startup applications. Since there is no desktop on the display, I can 
start a CtrlAlt-F2 root session and can verify this by ps aux.

Looking at Xorg.0.log, I see an error message - when I do not log in as a 
regular user - ”failed to add fb -22” followed by ”modeset(0): failed to set 
mode: invalid argument”. This is presumably the point of failure in displaying 
the graphical desktop.

Again, this is a ATI Radeon card and occurred after ”some” yum update. I have 
not been able to revert to a previous working desktop yet, loading an older 
kernel does not help. I suspect it is some interaction between the kernel, the 
display driver and x11.

I found that after initially installing the x11 ATI driver I had also installed 
fglrx-x11 from elrepo I believe but can now not find it, nor whether there is 
an update available that might resolve my problem.

Any suggestions?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Laptop display issue

[H]

On October 2, 2020 12:24:06 PM EDT, H  wrote:
>On October 1, 2020 3:42:34 PM EDT, H  wrote:
>>I now have an older laptop with a display problem. I installed Centos
>7
>>on it in February and had to install the xorg-x11-drv-ati and evdev
>>drivers because the docking station has an ATI Radeon card. Everything
>>worked fine with a dual display setup. I probably after that ran a
>>system update but did not reboot while in this office. Today, when I
>>got to the office again for the first time in seven months it does not
>>boot into the desktop but fails after displaying ”Started Light
>Display
>>Manager” with a mouse pointer on one display that can be moved but no
>>desktop at all. The keyboard works and I can start a terminal session.
>>
>>If I remove the laptop from the docking station everything works as
>>expected but not in the station, presumably because it now uses the
>>docking station card. Futzing around I see that systemctl --failed
>>lists nothing, nor did dmesg immediately suggest a reason. In the yum
>>history I see that this driver was updated to 19.0.1-3 from the
>>19.0.1-2 that installed with. Yum downgrade to 19.0.1-2 did not change
>>the issue. Nor has booting an older kernel helped so far.
>>
>>Although when I remove quiet from the grub command line it seems to
>>stop after ”Started Load CPU microcode update” following the ”Started
>>Light Display Manager” already mentioned, I strongly suspect some
>issue
>>with the graphics driver.
>>
>>Since the computer boots and seems to run fine with the internal
>>display when removed from the docking station it seems that there are
>>no hardware issues in the unit itself. My understanding is that the
>ATI
>>driver can be a problem and needs to match the kernel etc - perhaps
>>there is something wrong here?
>>
>>Any suggestions for how to attack this? I need to use it in the
>docking
>>station and have no alternative. Thank you.
>
>Researching this further, the issue seems to be with x11. I found that
>blindly typing my password to log into the system seems to log me in
>and launches the expected startup applications. Since there is no
>desktop on the display, I can start a CtrlAlt-F2 root session and can
>verify this by ps aux.
>
>Looking at Xorg.0.log, I see an error message - when I do not log in as
>a regular user - ”failed to add fb -22” followed by ”modeset(0): failed
>to set mode: invalid argument”. This is presumably the point of failure
>in displaying the graphical desktop.
>
>Again, this is a ATI Radeon card and occurred after ”some” yum update.
>I have not been able to revert to a previous working desktop yet,
>loading an older kernel does not help. I suspect it is some interaction
>between the kernel, the display driver and x11.
>
>I found that after initially installing the x11 ATI driver I had also
>installed fglrx-x11 from elrepo I believe but can now not find it, nor
>whether there is an update available that might resolve my problem.
>
>Any suggestions?

I should also have added that because the wikipages at elrepo.org are down, I 
cannot consult those...
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos 7.7 and ATI driver

[H]

As you have seen in another message I have a failed system after an update from 
7.5. I /think/ the issue might be with the ATI driver which seems to fail to 
load a framebuffer in Xorg.0.log.

Is anyone successfully running a Radeon graphics card on 7.7? If so, might you 
share any issues and solutions?

Thanks.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos8: Glusterd do not start correctly when I startup or reboot all server together

[Dario Lesca]

The systemd glusterd.service unit modify do not resolve my problem

The solution is mount the glusterfs volume with this line into
/etc/fstab:
   virt2:/gfsvol2 /virt-gfs glusterfs 
defaults,_netdev,noauto,x-systemd.automount,x-systemd.device-timeout=20,x-systemd.requires=glusterd.service
 0 0

run 
   systemctl daemon-reload

and run this for mount the volume
   systemctl restart virt\\x2dgfs.mount

Now all work fine, also when I reboot or when I power on all server
together

Many thanks
Dario

Il giorno lun, 28/09/2020 alle 22.40 +0200, Dario Lesca ha scritto:
> I have install and configure on two server centos8 glusterfs in
> replica
> mode in this manner:
> 
>dnf install centos-release-gluster -y
>dnf install glusterfs-server glusterfs glusterfs-fuse -y
>systemctl enable --now glusterd
>gluster peer probe virt1
>gluster peer status
>sh creavolume.sh gfsvol1 301G /gfsvol1 xfs
># NOTE: this is a my shell script to create fs on lvm
>mkdir /gfsvol1/brick1
>gluster pool list
>gluster volume create gfsvol1 replica 2 virt1:/gfsvol1/brick1
>virt2:/gfsvol1/brick1 force
>gluster volume start gfsvol1
>gluster volume info gfsvol1
>gluster volume status gfsvol1
>gluster volume heal gfsvol1
># add to /etc/fstab
>vi /etc/fstab
>virt1:/gfsvol2 /virt-gfs glusterfs defaults,noatime,_netdev 0 0

virt2:/gfsvol2 /virt-gfs glusterfs 
defaults,_netdev,noauto,x-systemd.automount,x-systemd.device-timeout=20,x-systemd.requires=glusterd.service
 0 0

>mkdir /virt-gfs
>mount -a
> 
> All work fine but when I start or restart all server together
> glusterd
> server start but if I try mount the volume, gluster is not working.
> 
> At this point if I restart the glusterd service and run "mount -a"
> all
> work fine.
> 
> Seem is a boot network problem
> 
> Then I have try modify glusterd.service with 
> 
> $ sudo systemctl edit  glusterd.service --full
> 
> And modify the unit in this way:
> 
>#old
>< After=network.target
>< Before=network-online.target
>#new
>> After=network.target network-online.target
>> #Before=network-online.target
> 
> Now all work fine, mostly when I start or restart all server
> together.
> 
> There is another solution or this is a Bug?
> 
> Many thanks for your suggest
> 
-- 
Dario Lesca
(inviato dal mio Linux Fedora 32 Workstation)

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos