[ubuntu-za] Fwd: Re: UBUNTU TERUGVOER

Frans de waal meesterarend at gmail.com
Fri Mar 29 21:44:06 UTC 2019


On Fri, 29 Mar 2019, 23:39 Bruce Pieterse, <dev at santura.co.za> wrote:

> > Many thanks Bruce.
> >
> > Would the fact that his Windows installation on the same hard drive
> > is still running fine, alter your opinion about a potentially damaged
> > HDD in any way?
>
> It's really hard to say whether the entire disk or just a portion of
> the disk might be unreadable. I would say, that where Ubuntu resides on
> the disk at the moment, is where part of the drive is now unreadable.
> One way to tell is if Windows locks up from time to time, then parts of
> the disk where Windows resides are also damaged.  For me that indicates
> that the drive is on the way out. If Windows is fine, then you _might_ be
> in luck with a fresh install.
>
> My response was purely from experience with having a similar problem a
> few times over the years. The disk would just disappear then
> reappear a number of times in the OS and would take ~5-15 seconds to be
> mounted by the kernel again (root partition was not on these disks). I
> could see this by doing a tail -f /var/log/syslog or journalctl -f, for
> systemd nowadays, and you would see the same "I/O error, dev sda, <sector
> number> like the ones in your screenshot. A few weeks later, they stopped
> working or were to unreliable to put data on.
>
> This is also why I use the disks app in gnome for all hdd problems, just
> for the smart data I can view there... I'm sure there's other ways though.
> > He has downloaded an Iso image of Ubuntu and we will be booting from
> > that shortly to see what we can achieve in terms of repairs,
> > otherwise we will just do a fresh install, fortunately he has backups
> > of the important data on the drive.
>
> Best of luck! Let us know how it goes so we can help further if need
> be.
>
> > Best wishes,
> >
> > Jan
> >
> >
> >
> >
> > On 2019/03/29 18:46, Bruce Pieterse wrote:
> > > Hi,
> > >
> > > Unfortunately, the drive has sectors that are no longer readable by
> > > the kernel. This can be seen with "Buffer I/O error on /dev/sda5.
> > > logical block ..." output.
> > >
> > > At the top of the screenshot, it says that it is already trying to
> > > recover the journal for the file system, but is unable to read
> > > (READ DMA EXT) that portion of the disk.
> > >
> > > If it was affected by load shedding then I would recommend getting
> > > a new drive, doing a fresh install and try to copy as much of the
> > > data off this problematic drive as possible from an external drive
> > > docking bay/case.
> > >
> > > I'm not sure what type of disk this is e.g. Seagate, Western
> > > Digital etc, but you could try run the respective manufacturers
> > > disk tools to see if it can fix the drive. From my experience, the
> > > Buffer I/O error normally indicates failure of the drive.
> > >
> > > I hope this helps.
> > >  --
> > >
> > > All the best,
> > >
> > > Bruce
> > >
> > > On Fri, 2019-03-29 at 12:36 +0100, frank.kusel at tuta.io wrote:
> > > > Of miskien:
> > > >
> > > > /sbin/fsck -yf /dev/sda5
> > > >
> > > >
> > > > 29 Mar 2019, 10:56 by wesley.werner at gmail.com:
> > > > > Jan, my raai is David moet file system checker hardloop:
> > > > >
> > > > > fsck -yf /dev/sda5
> > > > >
> > > > >
> > > > >
>
> https://askubuntu.com/questions/885062/root-file-system-requires-manual-fsck
> > > > >
> > > > > --
> > > > > Regards
> > > > > Wesley Werner
> > >
> >
>
>
> --
> ubuntu-za mailing list
> ubuntu-za at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-za/attachments/20190329/93604aba/attachment-0001.html>


More information about the ubuntu-za mailing list