I know it won't help anymore, but for reference:
If you are having this issue you may have had a crash or non-clean shutdown and need to repair buckets.
Please take a look at this wiki:
https://wiki.splunk.com/Community:PostCrashFsckRepair
"splunk fsck --all" should show you what buckets are bad, you can either remove them, or try to repair the bucket
Useful options are: --include-hots, --log-to--splunkd-log & --ignore-read-error
USAGE
Supported modes are: scan, repair, clear-bloomfilter, check-integrity, generate-hash-files
:= --one-bucket|--all-buckets-one-index|--all-buckets-all-indexes
[--index-name= ] [--bucket-name= ] [--bucket-path= ]
[--include-hots]
[--local-id= ] [--origin-guid= ]
[--min-ET= ] [--max-LT= ]
:= [--try-warm-then-cold] [--log-to--splunkd-log] [--debug] [--v]
fsck repair [--bloomfilter-only]
[--backfill-always|--backfill-never] [--bloomfilter-output-path= ]
[--raw-size-only] [--metadata] [--ignore-read-error]
fsck scan [--metadata] [--check-bloomfilter-presence-always]
fsck clear-bloomfilter
fsck check-integrity
fsck generate-hash-files
fsck check-rawdata-format
fsck minify-tsidx --one-bucket --bucket-path= --dont-update-manifest|--home-path=
Notes:
The mode verb 'make-searchable' is synonym for 'repair'.
The mode 'check-integrity' will verify data integrity for buckets created with the integrity-check feature enabled.
The mode 'generate-hash-files' will create or update bucket-level hashes for buckets which were generated with the integrity-check feature enabled.
The mode 'check-rawdata-format' verifies that the journal format is intact for the selected index buckets (the journal is stored in a valid gzip container and has valid journal structure
Flag --log-to--splunkd-log is intended for calls from within splunkd.
If neither --backfill-always nor --backfill-never are given, backfill decisions will be made per indexes.conf 'maxBloomBackfillBucketAge' and 'createBloomfilter' parameters.
Values of 'homePath' and 'coldPath' will always be read from config; if config is not available, use --one-bucket and --bucket-path but not --index-name.
All constraints supplied are implicitly ANDed.
Flag --metadata is only applicable when migrating from 4.2 release.
If giving --include-hots, please recall that hot buckets have no bloomfilters.
Not all argument combinations are valid.
If --help found in any argument position, prints this message & quits.
... View more
