How to fill a device with zeros, without overwriting the bytes that are already zeros? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionHow to wipe a partition quickly with value zero?Cryptsetup: pre-fill the partition with random datahow to use dd to fill drive with 1'sWhy is dd reading from and writing to the same disk?Is it feasible to fill a ntfs partition/device pre install with zeroess?How large is the img that dd creates?How to overwrite beginning of a device with random bits or zeros?I have killed my HDDIs it necessary to fill a device with zeroes before writing an ISO to it?How to dd a TrueOS installer to USB, on LinuxHow to set the passphrase that different keys are discriminable

How does debian/ubuntu knows a package has a updated version

The logistics of corpse disposal

How do I keep my slimes from escaping their pens?

Do I really need recursive chmod to restrict access to a folder?

Is the Standard Deduction better than Itemized when both are the same amount?

Can I cast Passwall to drop an enemy into a 20-foot pit?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

Bete Noir -- no dairy

Generate an RGB colour grid

Why did the rest of the Eastern Bloc not invade Yugoslavia?

Why do people hide their license plates in the EU?

String `!23` is replaced with `docker` in command line

Extract all GPU name, model and GPU ram

What does this icon in iOS Stardew Valley mean?

How come Sam didn't become Lord of Horn Hill?

What exactly is a "Meth" in Altered Carbon?

At the end of Thor: Ragnarok why don't the Asgardians turn and head for the Bifrost as per their original plan?

Using audio cues to encourage good posture

When were vectors invented?

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

Why do we bend a book to keep it straight?

Coloring maths inside a tcolorbox

Why is my conclusion inconsistent with the van't Hoff equation?

Output the ŋarâþ crîþ alphabet song without using (m)any letters



How to fill a device with zeros, without overwriting the bytes that are already zeros?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionHow to wipe a partition quickly with value zero?Cryptsetup: pre-fill the partition with random datahow to use dd to fill drive with 1'sWhy is dd reading from and writing to the same disk?Is it feasible to fill a ntfs partition/device pre install with zeroess?How large is the img that dd creates?How to overwrite beginning of a device with random bits or zeros?I have killed my HDDIs it necessary to fill a device with zeroes before writing an ISO to it?How to dd a TrueOS installer to USB, on LinuxHow to set the passphrase that different keys are discriminable



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








5















I have a USB flash drive usb 3, the reading speed is much more than the writing speed.
Let's say that 99% of the flash memory is already full with zeros, and I would like to fill it with zeros until 100%, by overwriting all the memory flash with zeros dd if=/dev/zero of=/dev/FLASH.



This process is going to be long, and it will minimize the life expectancy of the flash drive.



I thought, maybe it would be much quicker to check which areas are non-zero, and overwrite only those non-zertos areas with zeros?



Are there anyways of doing this? If it is interesting, I would need all this for security reasons.










share|improve this question
























  • Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

    – RonJohn
    Sep 16 '18 at 16:55











  • dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

    – mikst
    Sep 16 '18 at 17:22











  • who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

    – Jasen
    Sep 16 '18 at 20:45












  • @RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

    – Slok
    Sep 17 '18 at 14:51











  • @Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

    – Slok
    Sep 17 '18 at 14:51

















5















I have a USB flash drive usb 3, the reading speed is much more than the writing speed.
Let's say that 99% of the flash memory is already full with zeros, and I would like to fill it with zeros until 100%, by overwriting all the memory flash with zeros dd if=/dev/zero of=/dev/FLASH.



This process is going to be long, and it will minimize the life expectancy of the flash drive.



I thought, maybe it would be much quicker to check which areas are non-zero, and overwrite only those non-zertos areas with zeros?



Are there anyways of doing this? If it is interesting, I would need all this for security reasons.










share|improve this question
























  • Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

    – RonJohn
    Sep 16 '18 at 16:55











  • dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

    – mikst
    Sep 16 '18 at 17:22











  • who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

    – Jasen
    Sep 16 '18 at 20:45












  • @RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

    – Slok
    Sep 17 '18 at 14:51











  • @Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

    – Slok
    Sep 17 '18 at 14:51













5












5








5








I have a USB flash drive usb 3, the reading speed is much more than the writing speed.
Let's say that 99% of the flash memory is already full with zeros, and I would like to fill it with zeros until 100%, by overwriting all the memory flash with zeros dd if=/dev/zero of=/dev/FLASH.



This process is going to be long, and it will minimize the life expectancy of the flash drive.



I thought, maybe it would be much quicker to check which areas are non-zero, and overwrite only those non-zertos areas with zeros?



Are there anyways of doing this? If it is interesting, I would need all this for security reasons.










share|improve this question
















I have a USB flash drive usb 3, the reading speed is much more than the writing speed.
Let's say that 99% of the flash memory is already full with zeros, and I would like to fill it with zeros until 100%, by overwriting all the memory flash with zeros dd if=/dev/zero of=/dev/FLASH.



This process is going to be long, and it will minimize the life expectancy of the flash drive.



I thought, maybe it would be much quicker to check which areas are non-zero, and overwrite only those non-zertos areas with zeros?



Are there anyways of doing this? If it is interesting, I would need all this for security reasons.







security dd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 16 '18 at 16:04







user88036

















asked Sep 16 '18 at 15:30









SlokSlok

282




282












  • Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

    – RonJohn
    Sep 16 '18 at 16:55











  • dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

    – mikst
    Sep 16 '18 at 17:22











  • who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

    – Jasen
    Sep 16 '18 at 20:45












  • @RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

    – Slok
    Sep 17 '18 at 14:51











  • @Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

    – Slok
    Sep 17 '18 at 14:51

















  • Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

    – RonJohn
    Sep 16 '18 at 16:55











  • dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

    – mikst
    Sep 16 '18 at 17:22











  • who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

    – Jasen
    Sep 16 '18 at 20:45












  • @RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

    – Slok
    Sep 17 '18 at 14:51











  • @Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

    – Slok
    Sep 17 '18 at 14:51
















Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

– RonJohn
Sep 16 '18 at 16:55





Does the device have a file system on it? And files? Mainly, though, if this is a one-time affair, then dd if=/dev/zero of=/dev/FLASH would be a heck of a lot faster than writing a program to read the drive one block at a time, comparing it to zeros, and rewriting it if it is.

– RonJohn
Sep 16 '18 at 16:55













dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

– mikst
Sep 16 '18 at 17:22





dd if=/dev/zero of=/dev/FLASH is not secure enough for legal/compliance purposes, if that is a concern readmoar on secure erase.

– mikst
Sep 16 '18 at 17:22













who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

– Jasen
Sep 16 '18 at 20:45






who do you need to be secure from? what sort of budget does the attacker have? writing zeros to a flash drive may only hide the data.

– Jasen
Sep 16 '18 at 20:45














@RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

– Slok
Sep 17 '18 at 14:51





@RonJohn imagine that there is no file system. I want to be 100% that there are only zeros on the flash drive, regardless of whether there is a file system there or not.

– Slok
Sep 17 '18 at 14:51













@Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

– Slok
Sep 17 '18 at 14:51





@Jasen filling the flash drive with zeros I consider sufficient in my circumstances.

– Slok
Sep 17 '18 at 14:51










1 Answer
1






active

oldest

votes


















4














Security reasons aside, let's do it. We can (ab)use GNU ddrescue.



To detect sectors of zeros --generate-mode is useful.




When ddrescue is invoked with the --generate-mode option it operates in "generate mode", which is different from the default "rescue mode". That is, if you use the --generate-mode option, ddrescue does not rescue anything. It only tries to generate a mapfile for later use.



[…]



ddrescue can in some cases generate an approximate mapfile, from infile and the (partial) copy in outfile, that is almost as good as an exact mapfile. It makes this by simply assuming that sectors containing all zeros were not rescued.



[…]



ddrescue --generate-mode infile outfile mapfile



(source)



Let's pretend your device is outfile from previous ddrescue run. We cannot use it as infile (because ddrescue refuses to work when infile and outfile are the same file), we need a dummy one, /dev/zero will do. We should know the physical sector size of your device and use it with -b option. This command may help:



lsblk -o NAME,PHY-SeC /dev/FLASH


Here I assume it's 512.



ddrescue -b 512 --generate-mode /dev/zero /dev/FLASH flash.map


Now flash.map describes every sector either as non-tried (?) or as finished (+), depending on whether it was full of zeros or not. The next step is to fill non-zero sectors with zeros; --fill-mode is perfect for this job:




When ddrescue is invoked with the --fill-mode option it operates in "fill mode", which is different from the default "rescue mode". That is, if you use the --fill-mode option, ddrescue does not rescue anything. It only fills with data read from infile the blocks of outfile whose status character from mapfile coincides with one of the type characters specified as argument to the --fill-mode option.




(source)



We must use the same -b value as with --generate-mode, additionally --force to overwrite the output device. This is the command:



ddrescue -b 512 --force --fill-mode=+ /dev/zero /dev/FLASH flash.map


This time /dev/zero is not just a dummy argument, it's the actual source of data (zeros) written to the device.



After ddrescue finishes, invoke sync. Now /dev/FLASH is filled with zeros.






share|improve this answer

























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f469399%2fhow-to-fill-a-device-with-zeros-without-overwriting-the-bytes-that-are-already%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    Security reasons aside, let's do it. We can (ab)use GNU ddrescue.



    To detect sectors of zeros --generate-mode is useful.




    When ddrescue is invoked with the --generate-mode option it operates in "generate mode", which is different from the default "rescue mode". That is, if you use the --generate-mode option, ddrescue does not rescue anything. It only tries to generate a mapfile for later use.



    […]



    ddrescue can in some cases generate an approximate mapfile, from infile and the (partial) copy in outfile, that is almost as good as an exact mapfile. It makes this by simply assuming that sectors containing all zeros were not rescued.



    […]



    ddrescue --generate-mode infile outfile mapfile



    (source)



    Let's pretend your device is outfile from previous ddrescue run. We cannot use it as infile (because ddrescue refuses to work when infile and outfile are the same file), we need a dummy one, /dev/zero will do. We should know the physical sector size of your device and use it with -b option. This command may help:



    lsblk -o NAME,PHY-SeC /dev/FLASH


    Here I assume it's 512.



    ddrescue -b 512 --generate-mode /dev/zero /dev/FLASH flash.map


    Now flash.map describes every sector either as non-tried (?) or as finished (+), depending on whether it was full of zeros or not. The next step is to fill non-zero sectors with zeros; --fill-mode is perfect for this job:




    When ddrescue is invoked with the --fill-mode option it operates in "fill mode", which is different from the default "rescue mode". That is, if you use the --fill-mode option, ddrescue does not rescue anything. It only fills with data read from infile the blocks of outfile whose status character from mapfile coincides with one of the type characters specified as argument to the --fill-mode option.




    (source)



    We must use the same -b value as with --generate-mode, additionally --force to overwrite the output device. This is the command:



    ddrescue -b 512 --force --fill-mode=+ /dev/zero /dev/FLASH flash.map


    This time /dev/zero is not just a dummy argument, it's the actual source of data (zeros) written to the device.



    After ddrescue finishes, invoke sync. Now /dev/FLASH is filled with zeros.






    share|improve this answer





























      4














      Security reasons aside, let's do it. We can (ab)use GNU ddrescue.



      To detect sectors of zeros --generate-mode is useful.




      When ddrescue is invoked with the --generate-mode option it operates in "generate mode", which is different from the default "rescue mode". That is, if you use the --generate-mode option, ddrescue does not rescue anything. It only tries to generate a mapfile for later use.



      […]



      ddrescue can in some cases generate an approximate mapfile, from infile and the (partial) copy in outfile, that is almost as good as an exact mapfile. It makes this by simply assuming that sectors containing all zeros were not rescued.



      […]



      ddrescue --generate-mode infile outfile mapfile



      (source)



      Let's pretend your device is outfile from previous ddrescue run. We cannot use it as infile (because ddrescue refuses to work when infile and outfile are the same file), we need a dummy one, /dev/zero will do. We should know the physical sector size of your device and use it with -b option. This command may help:



      lsblk -o NAME,PHY-SeC /dev/FLASH


      Here I assume it's 512.



      ddrescue -b 512 --generate-mode /dev/zero /dev/FLASH flash.map


      Now flash.map describes every sector either as non-tried (?) or as finished (+), depending on whether it was full of zeros or not. The next step is to fill non-zero sectors with zeros; --fill-mode is perfect for this job:




      When ddrescue is invoked with the --fill-mode option it operates in "fill mode", which is different from the default "rescue mode". That is, if you use the --fill-mode option, ddrescue does not rescue anything. It only fills with data read from infile the blocks of outfile whose status character from mapfile coincides with one of the type characters specified as argument to the --fill-mode option.




      (source)



      We must use the same -b value as with --generate-mode, additionally --force to overwrite the output device. This is the command:



      ddrescue -b 512 --force --fill-mode=+ /dev/zero /dev/FLASH flash.map


      This time /dev/zero is not just a dummy argument, it's the actual source of data (zeros) written to the device.



      After ddrescue finishes, invoke sync. Now /dev/FLASH is filled with zeros.






      share|improve this answer



























        4












        4








        4







        Security reasons aside, let's do it. We can (ab)use GNU ddrescue.



        To detect sectors of zeros --generate-mode is useful.




        When ddrescue is invoked with the --generate-mode option it operates in "generate mode", which is different from the default "rescue mode". That is, if you use the --generate-mode option, ddrescue does not rescue anything. It only tries to generate a mapfile for later use.



        […]



        ddrescue can in some cases generate an approximate mapfile, from infile and the (partial) copy in outfile, that is almost as good as an exact mapfile. It makes this by simply assuming that sectors containing all zeros were not rescued.



        […]



        ddrescue --generate-mode infile outfile mapfile



        (source)



        Let's pretend your device is outfile from previous ddrescue run. We cannot use it as infile (because ddrescue refuses to work when infile and outfile are the same file), we need a dummy one, /dev/zero will do. We should know the physical sector size of your device and use it with -b option. This command may help:



        lsblk -o NAME,PHY-SeC /dev/FLASH


        Here I assume it's 512.



        ddrescue -b 512 --generate-mode /dev/zero /dev/FLASH flash.map


        Now flash.map describes every sector either as non-tried (?) or as finished (+), depending on whether it was full of zeros or not. The next step is to fill non-zero sectors with zeros; --fill-mode is perfect for this job:




        When ddrescue is invoked with the --fill-mode option it operates in "fill mode", which is different from the default "rescue mode". That is, if you use the --fill-mode option, ddrescue does not rescue anything. It only fills with data read from infile the blocks of outfile whose status character from mapfile coincides with one of the type characters specified as argument to the --fill-mode option.




        (source)



        We must use the same -b value as with --generate-mode, additionally --force to overwrite the output device. This is the command:



        ddrescue -b 512 --force --fill-mode=+ /dev/zero /dev/FLASH flash.map


        This time /dev/zero is not just a dummy argument, it's the actual source of data (zeros) written to the device.



        After ddrescue finishes, invoke sync. Now /dev/FLASH is filled with zeros.






        share|improve this answer















        Security reasons aside, let's do it. We can (ab)use GNU ddrescue.



        To detect sectors of zeros --generate-mode is useful.




        When ddrescue is invoked with the --generate-mode option it operates in "generate mode", which is different from the default "rescue mode". That is, if you use the --generate-mode option, ddrescue does not rescue anything. It only tries to generate a mapfile for later use.



        […]



        ddrescue can in some cases generate an approximate mapfile, from infile and the (partial) copy in outfile, that is almost as good as an exact mapfile. It makes this by simply assuming that sectors containing all zeros were not rescued.



        […]



        ddrescue --generate-mode infile outfile mapfile



        (source)



        Let's pretend your device is outfile from previous ddrescue run. We cannot use it as infile (because ddrescue refuses to work when infile and outfile are the same file), we need a dummy one, /dev/zero will do. We should know the physical sector size of your device and use it with -b option. This command may help:



        lsblk -o NAME,PHY-SeC /dev/FLASH


        Here I assume it's 512.



        ddrescue -b 512 --generate-mode /dev/zero /dev/FLASH flash.map


        Now flash.map describes every sector either as non-tried (?) or as finished (+), depending on whether it was full of zeros or not. The next step is to fill non-zero sectors with zeros; --fill-mode is perfect for this job:




        When ddrescue is invoked with the --fill-mode option it operates in "fill mode", which is different from the default "rescue mode". That is, if you use the --fill-mode option, ddrescue does not rescue anything. It only fills with data read from infile the blocks of outfile whose status character from mapfile coincides with one of the type characters specified as argument to the --fill-mode option.




        (source)



        We must use the same -b value as with --generate-mode, additionally --force to overwrite the output device. This is the command:



        ddrescue -b 512 --force --fill-mode=+ /dev/zero /dev/FLASH flash.map


        This time /dev/zero is not just a dummy argument, it's the actual source of data (zeros) written to the device.



        After ddrescue finishes, invoke sync. Now /dev/FLASH is filled with zeros.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 19 '18 at 7:38

























        answered Oct 29 '18 at 23:29









        Kamil MaciorowskiKamil Maciorowski

        1,75711030




        1,75711030



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f469399%2fhow-to-fill-a-device-with-zeros-without-overwriting-the-bytes-that-are-already%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -dd, security

            Popular posts from this blog

            Word for a person who has no opinion about whether god existsWord for having a definite opinion while simultaneously withholding judgment?What's the opposite of “newcomer? Is ”veteran" OK?What do you call an “atheist” who might believe in an afterlife?What's a word for someone who wants to voice opinions but not have them challenged?Word for someone who dismisses contrary opinions as irrational?Somone who thinks they are overly special/out of the ordinaryIs there a word, phrase or idiom for “a person who is incapable of thinking about the future”?The belief that a god is human-likeA word for a non-famous person/thing you have heard a lot aboutAdjective for a person who enjoys taking care of their appearance

            What was this official D&D 3.5e Lovecraft-flavored rulebook?What was this set of RPG tools called?As a first-time DM should I let my players play complex character classes and roles?Nymph's Kiss and the RelationshipWhat was the name of this Cleric Prestige Class that shapes metal with its bare hands?Are the 3.5e Dragonlance books third party or official works?What's up with the domain Vile Darkness?What was this 80s book about RPGs?What was the name of this Werewolf band?What book had Rituals to “upgrade” animal companions to keep them viable at higher levels?What was this RPG that had rules for player-owned businesses?

            2017 IndyCar Series Contents Series news Teams and drivers Schedule Season summary Footnotes References External links Navigation menu"INDYCAR: Initial 2018 bodywork concepts unveiled"the original"IndyCar confirms switch to Performance Friction brakes in 2017""AJ Foyt Racing will switch to Chevy"the original"Carlos Munoz, Conor Daly will drive for AJ Foyt Racing""Zach Veach's Indy 500 Debut Confirmed with Foyt""No mass exodus from Honda after Ganassi switch""Ex-F1 driver Sato joins Andretti Autosport for 2017 IndyCar season""IndyCar's Ryan Hunter-Reay, sponsor DHL paired through 2020""hhgregg and Andretti Autosport announce partnership for key races in 2016""INDYCAR: Rossi re-signs with Andretti"the original"McLaren Formula 1 - Fernando Alonso to race at Indy 500 with McLaren, Honda and Andretti Autosport""Shank will finally take part in Indy 500 with Harvey, Andretti | MotorSportsTalk""Andretti adds Jack Harvey to Indy 500 field""Ganassi switches to Honda power for 2017""INDYCAR: Chilton returns to Ganassi"the original"IndyCar silly season: Who's going where in 2017?""INDYCAR: Kanaan, NTT Data return to Ganassi"the original"Kimball to remain at Ganassi for 2017""Coyne confirms Bourdais for 2017 IndyCar season""Davison to sub for Bourdais in Indy 500"the original"Gutierrez confirmed for Detroit IndyCar debut""Gutierrez returns with Coyne for rest of 2017 season""Vautier to drive for Coyne at Texas"the original"INDYCAR: Coyne confirms Jones for 2017"the original"Pippa Mann returns to Coyne for Indy 500""Karam, Dreyer & Reinbold teaming up again for Indianapolis 500""Pigot to return to Ed Carpenter Racing""Hildebrand confirmed as full-time Ed Carpenter driver""Veach to replace injured Hildebrand at Barber"the originalNew Team Harding Racing Enters Chaves for 101st Indianapolis 500"Juncos Racing Announces Entry in 101st Running of the Indianapolis 500 :: Juncos Racing""Juncos confirms Pigot for Indy 500""Saavedra confirmed in Juncos' second 500 entry"the original"Lazier confirms Indy 500 run after son's USF2000 debut"the original"Claman DeMelo to race for RLLR at Sonoma"the original"Rahal signs Servia and ace engineer for 2017""IndyCar: Aleshin returns with Schmidt"the original"Aleshin replaced by Saavedra for Toronto""Jack Harvey will pilot SPM No. 7 car at Watkins Glen, Sonoma""Jay Howard confirmed in Tony Stewart's supported SPM Indy entry""INDYCAR: Newgarden to wave the flag at Penske"the original"Pagenaud opts for No. 1 in 2017"the original"Penske confirms Newgarden for 2017""Montoya to stay with Team Penske in 2017""Target leaving IndyCar after 27 seasons with Chip Ganassi""Cavin: IndyCar could see complete driver/team shakeup in 2017""End of the road for KV Racing?""KV Racing confirms closure, equipment sold to Juncos""Juncos confirms IndyCar Series entry"the original"Juncos readies IndyCar program, aims for '17 500"the original"Harding Racing to add Texas, Pocono to schedule"the original"Sato signs with Andretti Autosport for 2017""INDYCAR: Aleshin in Doubt at SPM"the original"Long Beach notebook: JR Hildebrand breaks hand""Hildebrand cleared to return at Phoenix"the original"Bourdais to undergo surgery on multiple fractures""Aleshin loses Schmidt Peterson IndyCar ride""Saavedra in at SPM for Pocono, Gateway"the original"Bourdais to make return at Gateway"the original"The IndyCar Grand Prix no longer is sponsored by Angie's List""2017 IndyCar Series rulebook""2017 Verizon IndyCar Series Official Rulebook"Official websiteeeeee