Hi Nick!

> I'd start by seeing if there are any firmware updates
ooooooowkey, im kinda confused, but there is no openbsd related firmwares
lmao http://www.goplextor.com/Support/Downloads

>  Boot from a bsd.rd, and
>   # dd if=/dev/zero bs=1m of=/dev/rsdXc
I'll try it after work!

2017-01-21 7:26 GMT+03:00 Nick Holland <n...@holland-consulting.net>:

> On 01/20/17 21:21, Asbel Kiprop wrote:
> > Hi!
> > I got new Plextor ssd disk
> > root :: /home/ME : dmesg | grep sd0
> > sd0 at scsibus1 targ 0 lun 0: <ATA, PLEXTOR PX-256S2, 1.01> SCSI3
> 0/direct
> > fixed naa.5002303100b98e54
> > sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin
> ...
> > But now:
> >
> > newfs sd0a
> > /dev/rsd0a: 5122.2MB in 10490368 sectors of 512 bytes
> > 26 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each
> > super-block backups (for fsck -b #) at:
> > newfs: wtfs: write error on block 32: Input/output error
> >
> > and this in dmesg:
> > ahci0: attempting to idle device
> > atascsi_disk_sync_done: error
> >
> >
> > What is my problem?
>
> Got me, so far you seem to be a reasonable person, and you include a
> dmesg with your problem report, so how horrible can you be? :)
>
> oh, the disk.  right. sorry.
>
> Well...  I'd start by seeing if there are any firmware updates for your
> SSD from the manufacturer.  Seems to be that SSDs and "enterprise grade"
> disks are big on needing firmware updates.  Hopefully, my sarcastic and
> snarky tone over "ship first, engineer later" design was conveyed.
>
> After that ... you might want to try writing something to the entire
> disk before using it.  Boot from a bsd.rd, and
>    # dd if=/dev/zero bs=1m of=/dev/rsdXc
> This may help pre-lock-out any bad spots before trying to use them.
> (and yes, it says "write error", but on a file system, a write is often
> preceded by a read, and if the read fails, the write will be unable to
> be relocated.  Or maybe I'm the one with problems.)
>
> I'm not convinced this will help you, but it has helped me.  Really
> seemed to settle down some SSDs that I'd been fighting with.
>
> Nick.

Reply via email to