Date: Mon, 25 Jun 2012 16:24:10 -0500 From: Denver Hull <denverh@comcast.net> To: freebsd-usb@freebsd.org Subject: Re: Seagate FreeAgent GoFlex 1.5TB external HDD problems Message-ID: <4FE8D6FA.4080109@comcast.net> In-Reply-To: <CAGG2AkLFP9piWgByq6e=uwxiD_8sd4tQKHOCaps3dwFCPLs-Cw@mail.gmail.com> References: <CAGG2Ak%2BXmWvCb3PQoqPXAW7iC0PAQ=GNV79MhhGHjLO4GmWgdw@mail.gmail.com> <201206241533.08745.hselasky@c2i.net> <CAGG2Ak%2Bz3%2B=jcZ6Znws9BLCZX=Ja%2B24n8MLeWfLNO-%2BoJseVDQ@mail.gmail.com> <201206251700.39759.hselasky@c2i.net> <4FE883DC.3080003@comcast.net> <CAGG2AkLFP9piWgByq6e=uwxiD_8sd4tQKHOCaps3dwFCPLs-Cw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
maxim naumov wrote: > On Mon, Jun 25, 2012 at 4:29 PM, Denver Hull<denverh@comcast.net> wrote: > > >> storage device. If you're interested, I can either send you the source, or >> make it available by ftp. Might be easier than cobbling something up from >> scratch. >> > Denver, that is very considerate of you. please do send me the source. > I was going to use iozone but so far couldn't figure out how to make > it work on block devices. I am also going to try msdosfs on that drive > in the meantime. > > /max > > The source is available here: http://irresistible-images.com/files/diskrand/diskrand.tgz For instructions, just type diskrand with no parameters. If you have any trouble with it let me know. It's been a while since I used it, but I can probably still figure it out. To build it, use gmake in the parent (diskrand) directory. It will figure out your platform and build diskrand in the appropriate subdirectory: BSD, LINUX, SGI, etc. Optional gmake targets you can use are all, clean, install. You may need to use clean first, then install. For FreeBSD, install puts the executable in /usr/local/bin. It's mostly a tool to check for data corruption, so the normal use automatically includes an initial data fill over the specified range unless you disable it with -n. The data consists of a pattern based on the LBA. Data compare errors result in an output of all the data that didn't match, then it stops. Other errors will also cause it to stop. Reads always include a verification of the data, and writes are always a data pattern based on the LBA. It's unique for each LBA, but always the same for a specific LBA. In normal operation everything after the initialization is random: the starting LBA, the size of the transfer, whether it's a read or write. You can override any of that with the command-line switches. You can run multiple copies of diskrand on one device by assigning a different range within the device for each copy. You can get a lot of I/O activity going with that method. I guess that's about all. Let me know if you have any questions. Thanks, Denver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FE8D6FA.4080109>