Hi Andrew, * It is a good idea to backup whatever you can, before you do anything else.
* Once you have that out of the way, try $btrfs scrub start /dev/sda3 * I personally haven't used btrfs much, but I believe it may be better to try a $btrfs check --repair /dev/sda3 before you do the fsck as Kim suggested. -Manoj.C -Manoj.C On Wed, Jan 15, 2020 at 12:16 PM Kim Oldfield via luv-main < [email protected]> wrote: > Hi Andrew, > > To run a file system check on sda3 boot from a rescue disk an run: > > fsck -n /dev/sda3 > > This will tell you the problems with the filesystem on the partition > > If the data on sda3 is critical to you, or there is major corruption, then > you should backup the raw partition before trying to repair. > > To repair the partition run: > > fsck /dev/sda3 > > And answer "y" when asked to fix each problem. > > Regards > Kim > > On 15/1/20 11:54 am, Andrew Greig via luv-main wrote: > > Hi Manoj, > > Thank you for your response. I have had a look at those links, and they > are quite a bit "over my head", so I wonder if I should use the rescue disk > to facilitate shifting my ~/working directory to my RAID disks. (Nothing > else is of any consequence) and then use a Ubuntu 18.10 DVD to upgrade the > distribution and hopefully create a new GRUB on (in old terms) /dev/sda3 > > Thoughts? > > Thanks > > Andrew Greig > On 15/1/20 9:57 am, Manoj C Menon wrote: > > Hi Andrew, > > From the logs it looks like your sda3 partition (btrfs) is corrupt. > > Perhaps you could boot from a rescue CD/flash drive and try some of the > suggestions on these pages? > > https://www.suse.com/support/kb/doc/?id=7018133 > https://bbs.archlinux.org/viewtopic.php?id=248361 > > > -Manoj.C > > On Wed, Jan 15, 2020 at 12:17 AM Andrew Greig via luv-main < > [email protected]> wrote: > >> Hi All, >> >> I have discovered a Ubuntu Boot-Repair -Disc which avoids syntax issues, >> I was unable to come up with a satisfactory syntax for the commands >> needed to solve this problem. Suitably chastened I have located a laptop >> which has Thunderbird so now I can keep the thread on the list. My >> attempts to communicate from a tablet produced a pile of crap. >> >> I downloaded and burned a Disk-Repair-Disk for Ubuntu >> >> I have run the recommended steps to repair GRUB 2.8, but nothing has >> been achieved. >> >> I did request the log be sent to a paste bin just in case, and as it is >> a few pages of text here is the link. >> >> http://paste.ubuntu.com/p/pNsZCYF5QZ/ >> >> The last line acknowledges the failure to achieve a result. >> >> This machine is critical to my work, and I had considerable assistance >> earlier in 2019 to achieve a RAID system on this machine, for which I am >> truly grateful. >> >> I would appreciate any assistance with this problem. >> >> Andrew Greig >> >> _______________________________________________ >> luv-main mailing list >> [email protected] >> https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main >> > > _______________________________________________ > luv-main mailing > [email protected]https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main > > > _______________________________________________ > luv-main mailing list > [email protected] > https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main >
_______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
