# I did something stupid

**URL:** <https://discourse.beets.io/t/i-did-something-stupid/1850>\
**Category:** Help\
**Created:** [September 7, 2021, 2:00am UTC](https://discourse.beets.io/t/i-did-something-stupid/1850 "2021-09-07T02:00:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![apastuszak](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@apastuszak](https://discourse.beets.io/u/apastuszak)\
**Post date:** [September 7, 2021, 2:00am UTC](https://discourse.beets.io/t/i-did-something-stupid/1850/1 "2021-09-07T02:00:37Z")

</div>

Earlier this year, I bought a NAS and moved all my music from the internal hard drive to the NAS.

So, all my music used to be in /mnt/storage/music\_library

I mounted the NAS to /mnt/music and did an rsync from the old location to the new location. I then created symlink that liked /mnt/music to /mnt/storage/music\_library.

THEN, I really did something stupid. I didn’t read the documentation. Instead I just went into the config.yaml and edited:

`directory: /mnt/storage/music_library`

and changed it to:

`directory: /mnt/music`

And I went on my merry way importing more music. So, now I have a bunch of music in the database that thinks it’s at /mnt/storage/music\_library and other music that thinks it’s at /mnt/music.

I’m trying to clean this up.

Should I:

1. Delete the database and reimport everything using `beet import -AWC`
2. Create a new directory on the NAS. Mount it on the server and do a `beet move`

---

<div class="post-metadata">

**Author:** ![jackwilsdon](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/jackwilsdon/32/10_2.png) [@jackwilsdon](https://discourse.beets.io/u/jackwilsdon)\
**Post date:** [September 7, 2021, 7:05am UTC](https://discourse.beets.io/t/i-did-something-stupid/1850/2 "2021-09-07T07:05:35Z")

</div>

The SQL in [this comment](https://github.com/beetbox/beets/issues/133#issuecomment-674716637) might be of help - it updates the paths directly in the beets database.

I’d take a backup of your DB first though!