- luv-main - example.com

Re: Having trouble connecting external USB drive
by Terry Duell 30 Aug '19

30 Aug '19

On Fri, 30 Aug 2019 15:01:51 +1000, Timothy Rice <timothy.rice(a)unimelb.edu.au> wrote: >> [ 7413.669770] usb 4-3.1: new SuperSpeed Gen 1 USB device number 8 using >> xhci_hcd >> [ 7413.682284] usb 4-3.1: New USB device found, idVendor=174c, >> idProduct=55aa, bcdDevice= 1.00 >> [ 7413.682285] usb 4-3.1: New USB device strings: Mfr=2, Product=3, >> SerialNumber=1 >> [ 7413.682286] usb 4-3.1: Product: ASMT1051 >> [ 7413.682287] usb 4-3.1: Manufacturer: asmediag >> [ 7413.682287] usb 4-3.1: SerialNumber: 1234567890B7 > > It looks like such devices are a little notorious [1][2] but can be > worked > with using tweaks under /etc/modprobe.d/ [1][3] > > ~ Tim > > [1] https://www.raspberrypi.org/forums/viewtopic.php?t=237829 > [2] https://www.spinics.net/lists/linux-usb/msg109480.html > [3] https://www.spinics.net/lists/linux-usb/msg109524.html > Thanks for the advice and info. It's all a bit beyond me at this stage of proceedings, I'll have to spend some time trying come up to understand what it all means. Cheers, -- Regards, Terry Duell

2 1

Re: Having trouble connecting external USB drive
by Terry Duell 30 Aug '19

30 Aug '19

On Fri, 30 Aug 2019 14:30:00 +1000, Rohan McLeod <rhn(a)jeack.com.au> wrote: > Terry Duell via luv-main wrote: >> Hello All, >> I'm running Fedora 30, and have an external USB drive that has been >> used with a Windows laptop to save photos whilst travelling. >> I'd now like to move those files to my Fedora system, but Fedora >> doesn't see the drive. > > You don't say how big the drive is; > > it's definitely not an exFAT issue ? > It's 750GB. I just ran dmesg immediately after connecting the drive and on that occasion the drive mounted and the icon appeared on the desktop, but sadly it isn't repeatable. Cheers, -- Regards, Terry Duell

1 0

Re: Having trouble connecting external USB drive
by Terry Duell 30 Aug '19

30 Aug '19

On Fri, 30 Aug 2019 13:25:04 +1000, Piers via luv-main <luv-main(a)luv.asn.au> wrote: > > On 30/8/19 1:19 pm, Terry Duell via luv-main wrote: >> Hello All, >> I'm running Fedora 30, and have an external USB drive that has been >> used with a Windows laptop to save photos whilst travelling. > > > Does the drive have a propriety connection software (eg: security > system) in Windows? > > Unplug it - plug it in and send the last few lines of (in terminal): > > dmesg OK...that did something! As soon as I ran dmesg the drive icon appeared on the desktop and I can now access all the files...amazing. Not sure why, but it may be a solution. Yet to see if it's repeatable. Here's the last few lines from dmesg... [ 7413.669770] usb 4-3.1: new SuperSpeed Gen 1 USB device number 8 using xhci_hcd [ 7413.682284] usb 4-3.1: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [ 7413.682285] usb 4-3.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 7413.682286] usb 4-3.1: Product: ASMT1051 [ 7413.682287] usb 4-3.1: Manufacturer: asmediag [ 7413.682287] usb 4-3.1: SerialNumber: 1234567890B7 [ 7413.683330] usb-storage 4-3.1:1.0: USB Mass Storage device detected [ 7413.683393] usb-storage 4-3.1:1.0: Quirks match for vid 174c pid 55aa: 400000 [ 7413.683427] scsi host8: usb-storage 4-3.1:1.0 [ 7414.595778] . [ 7414.724129] scsi 8:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6 [ 7414.724360] sd 8:0:0:0: Attached scsi generic sg7 type 0 [ 7414.725081] sd 8:0:0:0: [sdg] Attached SCSI removable disk [ 7415.619771] .ready [ 7415.621258] sd 7:0:0:0: [sde] 1465149168 512-byte logical blocks: (750 GB/699 GiB) [ 7415.621260] sd 7:0:0:0: [sde] 4096-byte physical blocks [ 7415.621357] sd 7:0:0:0: [sde] Write Protect is off [ 7415.621358] sd 7:0:0:0: [sde] Mode Sense: 43 00 00 00 [ 7415.621517] sd 7:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 7415.621678] sd 7:0:0:0: [sde] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) [ 7415.651278] sde: sde1 sde2 sde3 [ 7415.652518] sd 7:0:0:0: [sde] Attached SCSI disk [terry@localhost ~]$ Cheers, -- Regards, Terry Duell

3 2

Having trouble connecting external USB drive
by Terry Duell 30 Aug '19

30 Aug '19

Hello All, I'm running Fedora 30, and have an external USB drive that has been used with a Windows laptop to save photos whilst travelling. I'd now like to move those files to my Fedora system, but Fedora doesn't see the drive. I have no trouble with USB sticks, connect them and they are immediately available, but when I connect the drive I hear a couple 'pings' from the system and that's all. I've spent some time trawling through the various stories on the subject, but all seem to relate to a permanent attachment, suggesting changes to the /etc/fstab to always mount the USB drive. I'm really looking for a 'casual' connection, as and when needed. I know that I've been able to do this in the distant past, i.e. plug in the drive and an icon appears and away I go, but that was a while ago and using earlier versions of Fedora. Any advice and help greatly appreciated. Cheers, -- Regards, Terry Duell

3 2

VPN Server: Windows + Linux Clients
by Piers 27 Aug '19

27 Aug '19

Hi there, I am looking to set up a VPN server for my cloud VM's. There will be both windows and linux clients - ideally using certificates to login. - What do you recommend (eg: OpenVPN) and are there any licensing requirements for an open source application? - My preference is to avoid installing client's on Windows if the MS network stack will handle it and it is secure - any pointers? Thanks Piers

1 0

Fwd: IMPORTANT NOTICE FROM LINUX JOURNAL, LLC.
by Andrew Pam 08 Aug '19

08 Aug '19

-------- Forwarded Message -------- Subject: IMPORTANT NOTICE FROM LINUX JOURNAL, LLC. Date: Thu, 08 Aug 2019 11:43:55 +1000 From: Linux Journal <subs(a)linuxjournal.com> Reply-To: subs(a)linuxjournal.com The Awkward Goodbye Subscribe Now *IMPORTANT NOTICE FROM LINUX JOURNAL, LLC:* *On August 7, 2019 /Linux Journal/ shut its doors for good. All staff were laid off and the company is left with no operating funds to continue in any capacity. The web site will continue to stay up for the next few weeks, hopefully longer for archival purposes if we can make it happen.* *–Linux Journal, LLC* * ---------------------------------------------------------------------------------------------* *Final Letter from the Editor: The Awkward Goodbye* by Kyle Rankin Have you ever met up with a friend at a restaurant for dinner, then after dinner you both step out to the street and say a proper goodbye, only when you leave, you find out that you both are walking in the same direction? So now, you get to walk together awkwardly until the true point where you part, and then you have another, second goodbye, that's much more awkward. That's basically this post. So, it was almost two years ago that I first said goodbye to /Linux Journal/ and the /Linux Journal/ community in my post "So Long and Thanks for All the Bash <https://linuxjournal.cmail19.com/t/j-l-mhjkdyd-tykiudkrkt-r/>". That post was a proper goodbye. For starters, it had a catchy title with a pun. The post itself had all the elements of a proper goodbye: part retrospective, part "Thank You" to the /Linux Journal/ team and the community, and OK, yes, it was also part rant. I recommend you read (or re-read) that post, because it captures my feelings about losing /Linux Journal/ way better than I can muster here on our awkward second goodbye. Of course, not long after I wrote that post, we found out that /Linux Journal/ wasn't dead after all! We all actually had more time together and got to work fixing everything that had caused us to die in the first place. A lot of our analysis of what went wrong and what we intended to change was captured in my article "What /Linux Journal's/ Resurrection Taught Me about the FOSS Community <https://linuxjournal.cmail19.com/t/j-l-mhjkdyd-tykiudkrkt-y/>" that we posted in our 25th anniversary issue. So we set to work and things were starting to look very promising. One of the changes I was particularly excited about was our expanded Deep Dive section in each issue. This "long-form journalism" approach to technical writing was something pretty special in the technical world and coming from someone who wrote a few Deep Dives of his own, there was something very freeing in knowing you could truly give a topic justice without artificial constraints on page length. You, the readers, and also new writers responded, and you could feel the new life and new energy in each issue. After dying and being revived, it was finally starting to look like some day soon we would be able to walk on our own. Unfortunately, we didn't get healthy enough fast enough, and when we found out we needed to walk on our own strength, we simply couldn't. So here we are giving our second, much more awkward, goodbye. What happens now? We gave each other a proper hug during the first goodbye, do we hug again this time? Do we do the hand-shake-that-turns-into-a-single-arm-hug thing? Do we just sort of wave and smile? It wouldn't be right to say goodbye without acknowledging the wonderful /Linux Journal/ community we have been blessed with who have stuck with us throughout the years and encouraged so much during our first goodbye. To quote from my own recounting of that time: Ultimately, we couldn't keep the lights on. /Linux Journal/ announced that it was shutting down on December 1, 2017. I followed up that announcement with an emotional farewell of my own. If you read that farewell, you'll see that somewhere in the middle it changed from a memoir into a manifesto. My sadness at seeing something I had worked on for ten years going away was replaced by anger that the Linux community had seemed to lose its way. I lost my way. I took Linux and FOSS for granted. It became clearer than ever to me that while Linux and FOSS had won the battle over the tech giants a decade before, new ones had taken their place in the meantime, and we were letting them win. Although I had written and spoken about Linux and FOSS for years, and used it personally and professionally, I felt like I hadn't done enough to support this thing I cared about so much. The death of /Linux Journal/ was a major factor in my decision to put my money where my mouth was, quit my job, and join Purism so I could work full-time helping to forward this cause. So yeah, I took the news pretty hard. We all took the news pretty hard, but where I had just lost a freelance writing gig, all of the core /Linux Journal/ team had just lost their full-time jobs. It was a difficult time, yet we also were flooded with so much support from you, our readers. Some people contacted us just to tell us how much they loved the magazine and how sorry they were to see it go. Others offered to pay more for their subscriptions if that would somehow help. Others still contacted us to see if they could develop a fundraising program to keep the magazine alive. I can't stress how much this incredible outpouring of support helped all of us during this difficult time. Thank you. So yes, thank you for sticking by us. We truly did everything we could to make this a success, and I'm so sorry it didn't work out. On a personal note, thank you to the rest of the /Linux Journal/ team. Not being able to work with all of you and chat with you is going to be the hardest part of all of this by far. If you want to keep in touch, you can find me at https://social.librem.one/@kyle on Mastodon and https://twitter.com/@kylerankin on Twitter. Facebook <https://linuxjournal.cmail19.com/t/j-l-mhjkdyd-tykiudkrkt-j/> Twitter <https://linuxjournal.cmail19.com/t/j-l-mhjkdyd-tykiudkrkt-t/> YouTube <https://linuxjournal.cmail19.com/t/j-l-mhjkdyd-tykiudkrkt-i/> Linux Journal 9597 Jones Rd #331 Houston, TX 77065 You are receiving this email because you previously subscribed to Linux Journal or had signed up for one of our products.

1 0

Re:Raid Disaster
by forums＠wtaustralia.com 24 Jul '19

24 Jul '19

Thanks again for the help. I am struggling a bit with the intricacies of this but am progressing a little I think. I have not yet tried Russell's suggestion of purchasing two new 4TB drives because of the expense but will go in that direction as a last resort. I have copied the data onto 2TB drives which are the same size and type as the originals. Not sure if that will achieve all that is required. I have been trying with mdadm to mount the drive but so far with no success. My mdadm.conf shows the drive: # definitions of existing MD arrays ARRAY /dev/md/2 metadata=1.2 UUID=b5f4346d:deb6f751:e69ac550:b0b961fe name=DiskStation:2 but when I try to mount the partition sda5 I get: bob@Comp1:~$ sudo mount /dev/md2 /media/ntfs mount: /media/ntfs: can't read superblock on /dev/md2. bob@Comp1:~$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md2 : inactive sda5[0](S) 1948779840 blocks super 1.2 unused devices: <none> Any further instructions or suggestions appreciated Bob

1 0

Raid Disaster
by forums＠wtaustralia.com 22 Jul '19

22 Jul '19

Hello all, I need some advise with regard to rescuing data from a raid disk. History: I gave a friend a Synology two bay NAS set up as a raid array to store their data safely and suggested that it was backed up regularly to another disk as well for safely. All their family photos for the last 10 years or so are stored there - the only copies. Husband (Windows User) familiarized himself with the Synology and things seemed to be OK. However he decided that I was being overcautious and that extra backup wasn't needed. :-( Unfortunately one of the disks failed and husband in his wisdom decided to 'fix' it and instead wiped all the data from the good disk - disaster. Current: I can access the damaged disk by attaching it to my Kubuntu workstation, reading it with testdisk and all the partitions and data appears to be still there, but I can't see the files because of the RAID filing system. I have tried ddrescue which I have been able to use to copy data from the main partition on the damaged disk onto an old ntfs disk I had lying around but it is still unreadable as the raid filesystem refuses to mount and I still can't see the files. I have the good disk still (no data as it was wiped, but partitions still there) and another spare identical 2 Tb disk as well. All I want is to rescue the photo files from the disk - I can then replace the disks in the Synology NAS and reinstall as well as having the photos safely saved elsewhere. How am i best to proceed?

7 7

re: Raid Disater
by forums＠wtaustralia.com 22 Jul '19

22 Jul '19

Thanks for the help Glenn. On 20/7/19 1:40 pm, Glenn McIntosh via luv-main wrote: > On 19/7/19 10:10 am, bob via luv-main wrote: >> I can access the damaged disk by attaching it to my Kubuntu workstation, >> reading it with testdisk and all the partitions and data appears to be >> still there, but I can't see the files because of the RAID filing >> system ... the raid filesystem >> refuses to mount and I still can't see the files. > Just asking for some clarification: > > * Are you saying that the files in the image are not visible with a file > carving tool such as photorec? I'd only suggest file carving as a last > resort as it is time consuming, but I've had success with it > particularly for static photo collections which tend to be small files > and relatively unfragmented, and you can use the jpg exif data to > reconstruct a semi-useful filename. I haven't tried this yet as i haven't used photorec before but it is on my list if necessary. > * When the good disk was 'wiped', was it just formatted or completely > erased? If you do have to do low level file recovery, it might be better > to work with that image instead (assuming you have more spare terabytes > of storage lying around to copy it onto!) It appears that all the data was wiped - the partitions are all still there. Not sure how to do a 'low level file recovery'. > > * When you say raid 'filesystem', are you saying it isn't a standard > file system on top of the raid? Or that there is a backup format on top > of the filesystem, maybe compressed? It appears to be Ext4: Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf58d74d3 Device Boot Start End Sectors Size Id Type /dev/sda1 256 4980735 4980480 2.4G fd Linux RAID autodetect /dev/sda2 4980736 9175039 4194304 2G fd Linux RAID autodetect /dev/sda3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sda5 9453280 3907015007 3897561728 1.8T fd Linux RAID autodetect I am unable to mount either the either the drive or the partition (sda5) where I think the data is stored. bob@Comp1:~$ sudo mount -o ro /dev/sda /media/ntfs mount: /media/ntfs: /dev/sda already mounted or mount point busy. bob@Comp1:~$ sudo mount -o ro /dev/sda5 /media/ntfs mount: /media/ntfs: unknown filesystem type 'linux_raid_member'. bob@Comp1:~$ The original disk causes the computer to baulk at startup and displays an American Megatrends screen and the message "SMART Status bad Backup and replace". I can then continue on through the BIOS and kubuntu starts OK. I can then see the disk with fdisk but not mount it as above. The detail above is using a clone of the original disk.

2 1

Re:Raid Disaster
by forums＠wtaustralia.com 22 Jul '19

22 Jul '19

Thanks to all those who have offered help. I am slowly working through all the suggestions and will post what I find and any further info. No resolution as yet unfortunately. Bob

2 1