On Tue, 3 Nov 2020 11:48:41 +1030
Brett Lymn wrote:
> On Mon, Nov 02, 2020 at 12:34:27PM +0100, BERTRAND Jol wrote:
> >
> > I refuse Seagate, Samsung and other WD in my servers or
> > workstations, and I refuse SMR technology also.
> >
>
> I have heard this sort of thing from many people
On Mon, Nov 02, 2020 at 12:34:27PM +0100, BERTRAND Jol wrote:
>
> I refuse Seagate, Samsung and other WD in my servers or workstations,
> and I refuse SMR technology also.
>
I have heard this sort of thing from many people over the years, they
get bitten by a few disk failures and form a
Jaromír Doleček writes:
> Le lun. 2 nov. 2020 à 14:36, Greg Troxel a écrit :
>> I don't see that this hypothesis is supported by any evidence, compared
>> to some tiny interaction betwween netbsd and stub/qemu that leads to not
>> enabling DMA. If you can explain why you think that, please
On Mon 02 Nov 2020 at 08:39:00 +, Riccardo Mottola wrote:
> I checked SMART status, it looks a little worrying:
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
> 5 100 36 yes online positiveReallocated sector count13
Le lun. 2 nov. 2020 à 14:36, Greg Troxel a écrit :
> I don't see that this hypothesis is supported by any evidence, compared
> to some tiny interaction betwween netbsd and stub/qemu that leads to not
> enabling DMA. If you can explain why you think that, please do.
Full dmesg would go a long
Hi!
on my HP genuine AMD laptop, I always had issues with the Radeon
displaying garbage. It happened with 9.0, 9.99 kernels and also now with 9.1
What changed is that today I was logged in remotely and could check
"dmesg" and see this:
[ 19618.256460] warning:
John Nemeth writes:
> } >> I have heard that the issue with with qemu "stub domains" and with
> } >> those, NetBSD ends up with PIO on disks and is thus unusably slow.
> } >>
> } >> https://wiki.xen.org/wiki/QEMU_vs_qemu-traditionnal_Feature_Comparison
> } >
> } > So running a HEAD GENERIC,
On Mon, Nov 02, 2020 at 11:13:01AM +0100, BERTRAND Joël wrote:
> Riccardo Mottola a écrit :
> > Then this is the data for the third day (each time I did a power-off
> > reboot, so it is not continuous operation, I shut down the laptop at night)
> >
> > SMART supported, SMART enabled
> > id value
joel.bertr...@systella.fr (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) writes:
>Hardware ECC Recovered was always high (and in constant increase).
That's a feature of modern high capacity drives. The only difference is
if and how such things are reported.
--
--
Michael van
riccardo.mott...@libero.it (Riccardo Mottola) writes:
>> Also use atactl to check the smart status of the disk.
>How reliable is that data?
It's what the manufacturer tells you.
> 1 58 34 yes online positiveRaw read error rate 27218486
>195 580 no online
> FWIW, I had the same experience with file servers. Seagate comes last
> when I have to order the list of manufacturers from which to buy.
> Western Digital, it depends on the series---but if a disk is bad,
> it is bad from the very beginning (unusable on arrival). I had good
> experience with
Riccardo Mottola a écrit :
> Then this is the data for the third day (each time I did a power-off
> reboot, so it is not continuous operation, I shut down the laptop at night)
>
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
> 1 60
Hi Martin,
On 2020-10-30 14:51:28 + Martin Husemann
wrote:
On Fri, Oct 30, 2020 at 03:41:55PM +0100, Riccardo Mottola wrote:
A lot of errors and the system is not bootable anymore! I get:
NetBSD MBR boot
Non-System disk or disk error
This is very early MBR boot sector
13 matches
Mail list logo
