Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

secrets.tdb corrupted 4 times, is this common or bad USB drive?

Featured Replies

So, I've been doing a bit of migrations and upgrades over the last week or so.  I changed out the underlying system, as in motherboard, cpu, case, etc., but drives remained the same, including the USB key.  When I migrated to the new hardware, long story short, /config/secrets.tdb was corrupted on the USB key; shares worked fine before, but I couldn't re-assign the drive slots.  Deleting the file (well, letting Windows ChkDsk do that for me) seemed to make the world a better place.

 

Fast forward to today, I pre-cleared a couple disks on another system, put them in to the new UnRAID box, replaced/upgraded the parity drive, all seems well.  Shut down to put in another pre-cleared drive, add those to the array, allow UnRAID to format, and no shares are available.  Reboot and the config is reset to previous (the drives I added are not in the array), although no shares are available again.  After fussing with it for a while, /config/secrets.tdb seems to be corrupted again.  Delete it (well, chkdsk in Windows again) and all seems well, though reverted back to the previous config, although I can now make changes and the shares are available (But, annoyingly, my pre-cleared drives are no longer pre-cleared and UnRAID wants to clear them before adding them to the array.)

 

So, I can't guarantee that the secrets.tdb file wasn't corrupted in the first place before I migrated to the new hardware, but the system was working fine.  Subsequent to the first corruption I can say that each shutdown has been a clean shutdown through the web management, but the secrets.tdb file corrupted anyway (I want to say that there's only been, probably, 3 shutdowns of that hardware between the first corruption and the second.)

 

I see multiple forum posts here from people that appeared to have corrupted secrets.tdb files and deleting it seems to have "fixed" their problems.

 

Is this common?  Should I be worried about my USB key?

 

It's a no-name thumb drive, a freebee left over from a trade show, in fact, but it's very physically small, so well suited for it's current use.  Other ones from the same run (I ended up with a bunch of them) seem fine in other uses, such as multiple ESXi hosts I have running off them.

 

(edited to update title)

  • Author

Oh, and I'm on Version 4.7 on a Celeron D, Intel DQ965GF motherboard, 2GB of RAM.  6 drives on local SATA, 3 drives on Silicon Image PCI SATA card.  USB key is connected to the rear ports off the motherboard, not a front panel port or anything.  No plugins or any other software, straight UnRAID 4.7.

  • Author

And it did it a 3rd time, now.  After a clean shutdown to physically move a drive for temperature reasons, all drives are still in the same SATA ports as earlier.  UnRAId started like usual, but no SMB shares.  Shut down clean, ChkDsk in Windows, with a full scan, this time, finds the one file error and fixes it.  Secrets.tdb was removed, another FOUND.00x folder in the root of the flash drive.

 

Attaching a SysLog from the semi-failed bootup.

matguy-unraid-syslog-1-14-2013.txt

The flash has a file system error. Run checkdisk in a PC.

  • Author

The flash has a file system error. Run checkdisk in a PC.

 

...Deleting the file (well, letting Windows ChkDsk do that for me) seemed to make the world a better place...

 

...Delete it (well, chkdsk in Windows again)...

...ChkDsk in Windows, with a full scan, this time, finds the one file error and fixes it.  Secrets.tdb was removed, another FOUND.00x folder in the root of the flash drive....

  • Author

3rd time wasn't a charm, just did it for the 4th time.

 

I shut it down cleanly to physically move it from my work bench to upstairs where my other servers live.  Put it in its spot and it start up like normal.  I get downstairs, log in, drives show up as they should, array is started... but the share doesn't seem accessible.  Check syslog:

 

Jan 20 19:06:03 Tower kernel: FAT: Filesystem error (dev sdj1)
Jan 20 19:06:03 Tower kernel:     fat_get_cluster: invalid cluster chain (i_pos 18060)
Jan 20 19:06:03 Tower kernel:     File system has been set read-only

 

Pull the USB drive, run a Check Disk, file fragments saved to Found.003.  Put back in my UnRAID box, all is well.

 

I guess the next test is to see if it does it on a power failure rather than a clean shut-down.

I'd say get a new flash drive.  That one seems to be dying.

 

Joe L.

  • Author

I'd say get a new flash drive.  That one seems to be dying.

 

Joe L.

And how does one transfer a license?

I'd say get a new flash drive.  That one seems to be dying.

 

Joe L.

And how does one transfer a license?

Send an e-mail to [email protected]

Explain the problem, include a link to this thread, supply a new GUID from a flash drive where you've loaded the free version of unRAID.  Tom has been very understanding. 

 

Joe L.

  • Author

I'll go pick up a new drive tomorrow, rather than trust one of these freebee drives again.

 

It's always good to have an excuse to go to Fry's.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.