Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - VastOne

Pages: [1] 2 3 ... 29
1
General Support / Kernel 5.14.01 and nVidia woes
« on: September 23, 2021, 07:38:26 PM »
This is already a solved issue but I am going to post it for anyone in the future for reference

Also ... It has been a while since I have done a How To or even been around.. I am still alive, still hoping for a different installer for VSIDO but also life happens and I love to golf... Cheers

I got back from a 2 week holiday with 2 of my sons, my daughter and my granddaughters up north to a massive update (obviously) and it included a new kernel jumping me from 5.10 to 5.14

I run nVidia latest drivers and didn't notice anything on the dkms build but honestly I was not really paying close attention... Upon reboot top that driver I was greeted with a failed to load start kernel module error and suspected it was a nVidia issue straight away.. This is how I solved it based on this nugget I found searching for a quick way to fix it

I started that kernel in repair mode which brings you to a spot to enter your root pw
I then used the following commands to start the network

(This was done a day later)

Code: [Select]
#ip link (it tells you what the card name is, in my case it was enp6s0)
# ip link set enp6s0 up

I then did the following:

Code: [Select]
# apt-get update
# apt-get dist-upgrade

Right away I noticed that the nVidia drivers had been updated and that a fix was already in place

All I had to do was apply the following to commit the kernel and new packages together

Code: [Select]
dpkg-reconfigure nvidia-kernel-dkms
I then just typed exit for a reboot (or ctrl alt del)

And booted to 5.140-1 perfectly

For those who live by the POIDH (Picture Or It Didn't Happen) creed


2
I have a PC that I have not booted into for a long time, at least 2 years

I tried to do a VSIDO install and here is where the weirdness begins .. When using the last/latest VSIDO ISO in live cd it boots fine with the realtek r8169 NIC loading and working fine. As soon as it is installed though I get the following message on boot and no network

Code: [Select]
no dedicated PHY driver found for PHY ID 0x01001002, maybe realtek.ko needs to be added to initramfs?
I have spent a couple of days trying to figure this out and I am stumped

First this is a Gigabyte GA-MA790X-UD4P motherboard that has the realtek r8169 as the onboard NIC and it has been flashed to its latest rom

After trying to update to newer kernels with no luck I decided to take a FSArchive of a working pc from a while back that has the 4.19 kernel, i installed it and the NIC and everything works fine. Every bit of code has been updated to the latest SID levels except the kernel

I have also installed the latest 5.9.0-5 and it fails but after reading about this all over google I think if I tried the 5.4 kernel it might work

I am now going to post two sets of data.. one of the working 4.19 kernel followed by the 5.9.0-5 that failed.. I am not necessarily looking for a solution like the good people over on Arch did here but I would like to discuss why some kernels appear to work and others seem to have left the r8169 code completely out

First set of data is from the working 4.19 kernel

lspci #

Code: [Select]
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD780 Host Bridge
00:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (external gfx0 port B)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port A)
00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port F)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micr-o Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: NVIDIA Corporation G96C [GeForce 9500 GT] (rev a1)
02:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
02:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

sudo journalctl -b #

journalctl -b # can be found here

systemctl list-unit-files --state=enabled

Code: [Select]
UNIT FILE                STATE   VENDOR PRESET
acpid.path               enabled enabled     
acpi-fakekey.service     enabled enabled     
acpi-support.service     enabled enabled     
anacron.service          enabled enabled     
apparmor.service         enabled enabled     
atd.service              enabled enabled     
avahi-daemon.service     enabled enabled     
blk-availability.service enabled enabled     
bluetooth.service        enabled enabled     
console-setup.service    enabled enabled     
cron.service             enabled enabled     
e2scrub_reap.service     enabled enabled     
getty@.service           enabled enabled     
irqbalance.service       enabled enabled     
keyboard-setup.service   enabled enabled     
live-config.service      enabled enabled     
live-tools.service       enabled enabled     
lm-sensors.service       enabled enabled     
lvm2-monitor.service     enabled enabled     
minidlna.service         enabled enabled     
minissdpd.service        enabled enabled     
networking.service       enabled enabled     
ntp.service              enabled enabled     
quota.service            enabled enabled     
quotarpc.service         enabled enabled     
rsync.service            enabled enabled     
rsyslog.service          enabled enabled     
rtkit-daemon.service     enabled enabled     
ssh.service              enabled enabled     
systemd-pstore.service   enabled enabled     
udisks2.service          enabled enabled     
vsftpd.service           enabled enabled     
wpa_supplicant.service   enabled enabled     
acpi-fakekey.socket      enabled enabled     
acpid.socket             enabled enabled     
avahi-daemon.socket      enabled enabled     
dm-event.socket          enabled enabled     
lvm2-lvmpolld.socket     enabled enabled     
uuidd.socket             enabled enabled     
remote-fs.target         enabled enabled     
anacron.timer            enabled enabled     
apt-daily-upgrade.timer  enabled enabled     
apt-daily.timer          enabled enabled     
e2scrub_all.timer        enabled enabled     
exim4-base.timer         enabled enabled     
logrotate.timer          enabled enabled     
man-db.timer             enabled enabled     
mlocate.timer            enabled enabled

Code: [Select]
vastone@vsido:~$ lsmod |grep r81
r8169                  90112  0
libphy                 77824  3 r8169,realtek
 

vastone@vsido:~$ lsmod |grep real
snd_hda_codec_realtek   118784  1
snd_hda_codec_generic    86016  1 snd_hda_codec_realtek
snd_hda_codec         151552  3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           94208  4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd                    94208  15 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
realtek                20480  0
libphy                 77824  3 r8169,realtek

vastone@vsido:~$ sudo dmesg |grep -i r8169
[    2.297190] libphy: r8169: probed
[    2.297341] r8169 0000:03:00.0 eth0: RTL8168d/8111d, 00:24:1d:1d:6c:b4, XID 281000c0, IRQ 24
[    2.297342] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   14.943452] r8169 0000:03:00.0: firmware: direct-loading firmware rtl_nic/rtl8168d-1.fw
[   14.944117] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[   16.715243] r8169 0000:03:00.0 eth0: Link is Up - 10Mbps/Full - flow control rx/t

This is now data fom the non working 5.9.0-5 kernel

vastone@vsido:~$ lspci #

Code: [Select]
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD780 Host Bridge
00:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (external gfx0 port B)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port A)
00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port F)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: NVIDIA Corporation G96C [GeForce 9500 GT] (rev a1)
02:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
02:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 02)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

vastone@vsido:~$ systemctl list-unit-files --state=enabled

Code: [Select]
UNIT FILE                STATE   VENDOR PRESET
acpid.path               enabled enabled     
acpi-fakekey.service     enabled enabled     
acpi-support.service     enabled enabled     
anacron.service          enabled enabled     
apparmor.service         enabled enabled     
atd.service              enabled enabled     
avahi-daemon.service     enabled enabled     
blk-availability.service enabled enabled     
bluetooth.service        enabled enabled     
console-setup.service    enabled enabled     
cron.service             enabled enabled     
e2scrub_reap.service     enabled enabled     
getty@.service           enabled enabled     
irqbalance.service       enabled enabled     
keyboard-setup.service   enabled enabled     
live-config.service      enabled enabled     
live-tools.service       enabled enabled     
lm-sensors.service       enabled enabled     
lvm2-monitor.service     enabled enabled     
minidlna.service         enabled enabled     
minissdpd.service        enabled enabled     
networking.service       enabled enabled     
ntp.service              enabled enabled     
quota.service            enabled enabled     
quotarpc.service         enabled enabled     
rsync.service            enabled enabled     
rsyslog.service          enabled enabled     
rtkit-daemon.service     enabled enabled     
ssh.service              enabled enabled     
systemd-pstore.service   enabled enabled     
udisks2.service          enabled enabled     
vsftpd.service           enabled enabled     
wpa_supplicant.service   enabled enabled     
acpi-fakekey.socket      enabled enabled     
acpid.socket             enabled enabled     
avahi-daemon.socket      enabled enabled     
dm-event.socket          enabled enabled     
lvm2-lvmpolld.socket     enabled enabled     
uuidd.socket             enabled enabled     
remote-fs.target         enabled enabled     
anacron.timer            enabled enabled     
apt-daily-upgrade.timer  enabled enabled     
apt-daily.timer          enabled enabled     
e2scrub_all.timer        enabled enabled     
exim4-base.timer         enabled enabled     
logrotate.timer          enabled enabled     
man-db.timer             enabled enabled     
mlocate.timer            enabled enabled     

48 unit files listed.

Code: [Select]
vastone@vsido:~$ sudo journalctl -b #


take a look at this code here journalctl -b #



Code: [Select]
vastone@vsido:~$ lsmod |grep r81
Code: [Select]
r8169                  98304  0
mdio_devres            16384  1 r8169
libphy                151552  3 r8169,mdio_devres,realtek

vastone@vsido:~$ lsmod |grep real
snd_hda_codec_realtek   143360  1
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
snd_hda_codec         163840  3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core          106496  4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd                   110592  15 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
realtek                24576  0
libphy                151552  3 r8169,mdio_devres,realtek

vastone@vsido:~$ sudo dmesg |grep -i r8169
[    1.629639] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[    1.650048] libphy: r8169: probed
[    1.650051] r8169 0000:03:00.0: no dedicated PHY driver found for PHY ID 0x01001002, maybe realtek.ko needs to be added to initramfs?
[    1.665669] r8169: probe of 0000:03:00.0 failed with error -49

3
VSIDO News & Announcements / The end of the VSIDO era
« on: November 23, 2020, 09:17:06 PM »
I want to thank you all who stuck with this project for as long as you have..

By the end of day tomorrow, I anticipate this site will no longer exist as I have simply ran out of funds to even afford to pay a 70 dollar annual fee

I may try to run the site from my home with DDS .. not sure yet, but since there is so little traffic I am not sure anyone would notice

I do have it all backed up, the sad part is that it has always been a resource for solutions and honestly that is all I ever wanted

Cheers to you all .. I can always be reached at vastone at the gmail com

4
  • Updated VSIDO to latest Debian SID kernel – 4.19.0-5-amd64 #1 SMP Debian 4.19.37-1 (2019-05-05)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

________________________________


The x64 is installing flawlessly (though still a delay during the bootloader installation)
The x64_uEFI installer is not seeing the
Code: [Select]
/lib/live/mount/medium/live/filesystem.squashfs
even though it is clearly there

5
Hardware Help & Support / ceni changes
« on: March 28, 2019, 03:07:33 AM »
ceni is in Debian repos and when ported there the name was changed to Ceni which caused headaches... 

For those who want it here is  fix for Ceni / ceni so that you won't have to change any menus... Run the following to create a ceni symlink

Code: [Select]
sudo ln -s /usr/sbin/Ceni /usr/local/bin/ceni
Keep in mind you must know roots PW in order to run ceni.. In VSIDO default you must change the root PW to know it by running:

Code: [Select]
sudo passwd root

6
  • Updated VSIDO to latest Debian SID kernel – 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

________________________________


After nearly a year, I have made some changes..

There is only the x64 and x64_uEFI versions now and forevermore

We are up to kernel 4.19 and I anticipate going to 5 in the next month

The only known issues I am aware of is that grub stalls during the install with the following message

Code: [Select]
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000000 microseconds
I think it is an installer issue related to what @filip fixed in locating the drives, I think the grub part of the installer also cannot find the drives but does the install fine anyway

I also have a new machine now, a uEFII machine donated to VSIDO by Luke / lwfitz so I can do all real time testing now onto HW

I also want to thank jedi, whose friendship and patience are one of the rocks behind VSIDO

Enjoy and please let me know of any issues

7
General Support / uEFI and grub2
« on: March 22, 2019, 12:15:32 AM »
Back story is simple, I have been away for a while and caught up with almost everything regarding the VSIDO build but there seems to be a big change in what ever grub uEFI uses (i know it is grub-efi-amd64) but something is completely different

Before (and still with legacy x64 VSIDO) to make sure eth0 was the correct name of the network interface all we had to do was make sure net.ifnames=0 is on the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub file

That has not changed, and as a matter of fact the line is there on a liveCD but what appears to have changed is grub-efi-amd no longer reads /etc/default/grub

The proof is this.. When you boot to the test uEFI ISO that is now available and tab to edit the grub line and add net.ifnames=0 to  the Linux (kernel) line it does in fact boot correctly with eth0 as the network interface name

So the question is simple

When you do add that parameter on a liveCD boot, what exactly is it being written to?

This all works as it should on Legacy x64 VSIDO which is also in that directory suggesting that it is definitely a uefi grub issue only

8
Hello all.. I wanted to share with everyone a discussion in chat I had with Zephyr.. This is it

Hello  Zephyr..! I am well and thank you for asking.. I am working nearly 7 days a week and although it is good to be working again it exhausts me.. I am doing more physical work now than I have ever done.. I am all right but it takes just about all my time..

The real issue with VSIDO is not so much lack of time or effort, it is/was with Debian
About 6 months ago I lost a HD that basically took me out for about a week.. No big deal, I just let VSIDO builds get away from me.. that week turned into a month and when I did try to start with the rebuilds Debian had so much crap that they were including (GCC 5,6,7,8) it caused the ISO to balloon to 400 MB more than when I was up to date.. It pissed me off, but I have started from ground zero before and was happy to do that.. that is about the time that my work started 6-7 days a week plus all my responsibilities here taking care of my invalid mother..

Needless to say I have not had the time, I do want to and will get back to rebuilding VSIDO again but I need some time to do that.. when I do get that time, rest assured, VSIDO will rock once again

Apologies to all in not talking about this sooner but in some ways I actually did need a break

Thanks for understanding

Cheers!


9
  • Updated VSIDO to latest Debian SID kernel – 4.15.0-3-amd64 #1 SMP Debian 4.15.17-1 (2018-04-19)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

10
General Support / 10 gig log files
« on: April 19, 2018, 01:57:39 AM »
My syslog and daemon.log both grew to 10 gig a piece and basically froze me out of a log in due to the file system running out of space.. after I cleared the logs I could get back in.. Both were too big to open with any editor (TWSS) so I have no idea what caused it.. This is a new install (reinstall) of the build system that had only been up for a day.. I am going to log back in and see if they begin to grow again, but so far they have not and I am at a loss.. never have I seen anything remotely close to this one.. On searches for solutions on google, there have been many instances of the syslog and kernel.log growing and on most there seemed to be an SSD involved which is what I am installed on

Any ideas?

11
  • Corrected an issue with the installer with the help of Filip. Removed dependencies on Debian-MultiMedia repo
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

12
VSIDO Discussions / Debian Bullshit
« on: March 21, 2018, 01:55:54 AM »
So I filed this bug report today

Straight forward, an update killed the ability to run any kind of apt-get update, dist-upgrade or install of any kind.. apt was broken

The response and closing of the bug makes it pretty clear where Debian is still stuck up their own asses

Quote
That's because you use packages from Debian Multimedia (dmo), which
breaks the dependency/file replacement resolution process of apt by
unnecessarily increasing the version number (1:1.12 > 1.14).

I resolved it by pretty much eliminating the multimedia repos and reinstalled the gstreamer stuff from SID

It did not sit well with me today... I never have understood the need to place blame on the end user when reporting an obvious bug

13
I've Got a Life / Aging and things...
« on: February 28, 2018, 02:11:30 AM »
I'll be 58 tomorrow...

Played 36 holes of golf today and played better than I ever have.. Pro level stuff

Hopefully it stays consistent all year.. Golf is a strange game.. The minute you think you have it all figured out it disappears like a fart in the wind

14
General Support / Be wary of NPM update
« on: February 23, 2018, 04:32:17 AM »
A bug in npm (Node Package Manager), the most widely used JavaScript package manager (something I have never heard of),  will change ownership of crucial Linux system folders, such as /etc, /usr, /boot

Guess we're lucky the crazy ass developer of VSIDO has never heard of it either...  ???

15
VSIDO Discussions / Testdisk Photorec and recovering deleted files
« on: February 22, 2018, 01:30:30 AM »
I want to relate a little story that will detail a gotcha, an OH FUCK, and some new info I have gleaned on recovering deleted files

1 - What happened

As most of you know I use grsync, a gui front end for rsync.. I swear by it.. I don't use it that often anymore (use ftp just as easily between systems and smart phone).. lately though I had been building up a nice supply of mp3's from one system using Pithos Fly (standard on VSIDO)

So I setup grsync to transfer a shit ton of new mp3's to this my main multimedia server.. I simply created a new one and this is what it looks like


 

See that one little area that says  Delete on destination?  When I reversed this and created it new, by default this is set to ON (checked) .. Why? Idiotic IMO to have something setup so dangerous that does not say 'ARE YOU SURE YOU WANT THIS?'.. But I missed it.. and you can guess what happens

Anyway, enough bitching about grsync, I still love it but the point of the above is.. be careful... When I set the reverse (this server and my main mp3 loacation) once I executed it started deleting files.. I noticed it right away and killed it but within 3 seconds 2000 files had been deleted

That's the gotcha and OH FUCK moment...

2 - Recovery .. I did some research and found out about testdisk which includes the app photorec.. I booted the VSIDO LiveCD.. installed test disk, and mounted a recovery location (Very important because you don't have enough room with the 1 gig in the liveCD session)

I basically followed the instructions from this site, selected mp3 as the targeted files and restored 4500 of them to the designated mounted recovery location (another partition).. I then used Puddletag to re-tag the files (the files are restored in a numeric naming convention based on the file structure they are found on)...

Did I get back the exact same thing? No.. but I did learn some new things, and did locate the files and restore them.. just not in the same directory structure..

It was an interesting learning experience.. and this bastardized How To just might help some folks down the road

Enjoy..  ???

Pages: [1] 2 3 ... 29