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.

Failed USB And Now Lost Drive

Featured Replies

Hi all, my USB stick died I managed to re format it and reinstall unraid.

 

I had a backup of the stick but it was taken prior to an extra disk being added.

 

The server came up and all the disks where re assigned that where there before when I took the backup of the flash but the disk that was added after the backup was taken is not assigned.

 

If I stop the array and assign the disk it comes up with a blue icon next to it.

 

If I try and start the array it gives a warning the disk needs to be cleared.

 

How can I get the drive back online without loosing data and or access the drive to get the data of it?

Hi all, my USB stick died I managed to re format it and reinstall unraid.

 

I had a backup of the stick but it was taken prior to an extra disk being added.

 

The server came up and all the disks where re assigned that where there before when I took the backup of the flash but the disk that was added after the backup was taken is not assigned.

 

If I stop the array and assign the disk it comes up with a blue icon next to it.

 

If I try and start the array it gives a warning the disk needs to be cleared.

 

How can I get the drive back online without loosing data and or access the drive to get the data of it?

You must set a new disk configuration.  (and unRAID will then subsequently re-calculate parity)

 

Whatever you do, do NOT format the new  drive.  It should be recognized as having a file-system on it once you set a new disk configuration.,

 

Since you did not bother to tell us what version of unRAID you are running, I cannot give you specific instructions for your version,.

  • Author

Gday its version 4.7

Gday its version 4.7

there is a bug in 4.7 where when setting up a completely new flash drive (as you are) an existing disk will show as unformatted.    If that happens, do not panic, and do not format the disk. (do not press the Format button)

 

Post back for more guidance.  The partition start pointer on that disk might need to be pointed to the correct starting sector for it to properly mount the disk and not have it show as unformatted.

  • Author

Hey, yes its definetly 4.7....

 

The usb is the same one just re formatted and new install with a backup of an old config file prior to this one drive being added.

 

I am guessing and I could be completely wrong but I thought it was not reconised as this drive was not in the system when I took the backup?

 

What should I do exactly?

  • Author

I just had a look in Unmenu and its coming up as "New Disk"

 

I also check vold_id in ssh and came back with this -

 

unknown or non-unique volume type (--probe-all lists possibly conflicting types)

 

Hey, yes its definetly 4.7....

 

The usb is the same one just re formatted and new install with a backup of an old config file prior to this one drive being added.

 

I am guessing and I could be completely wrong but I thought it was not reconised as this drive was not in the system when I took the backup?

 

What should I do exactly?

Log in on either the system console, or via telnet as "root"

 

Then type:

initconfig

respond to its prompt with

Yes

(with a capital "Y" and lower case "es")

When you then refresh the unRAID web-interface all disks should show "blue"

When you start the array, a parity sync will begin.

 

 

  • Author

Okay, this sounds dangerous  :P....

 

I am just going to backup some important files first before I do this.....

 

 

 

 

  • Author

Okay I did that and one drive the one that was missing initially comes up as "Unformatted".

 

A parity check is i place thought.

 

Is this correct?

Okay I did that and one drive the one that was missing initially comes up as "Unformatted".

 

A parity check is i place thought.

 

Is this correct?

yes, it is correct.

 

Now to run a few tests to see how the disk showing as unformatted is actually partitioned.

 

See here: http://lime-technology.com/forum/index.php?topic=15385.0

 

Specifically, need to see the output of

fdisk -l /dev/sdX

for that disak and also for

dd if=/dev/sdX count=195 | od -c -A d |  sed  30q

 

replacing /dev/sdX with the actual device name of your disk showing as unformatted.

 

You can do this while the parity check is under way.

Please make sure to post back your results.  Would definitely like to hear what happens as I can see this happening to me.

  • Author

# fdisk -l /dev/sde

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
1 heads, 63 sectors/track, 46512336 cylinders
Units = cylinders of 63 * 512 = 32256 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               2    46512336  1465138552+  83  Linux
Partition 1 does not end on cylinder boundary.

 

# dd if=/dev/sde count=195 | od -c -A d |  sed  30q
195+0 records in
195+0 records out
99840 bytes (100 kB) copied, 0.00160348 s, 62.3 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   ?  \0  \0  \0 361   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0099840

 

The parity sync is still running at 80% and drive is unformatted still.....

# fdisk -l /dev/sde

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
1 heads, 63 sectors/track, 46512336 cylinders
Units = cylinders of 63 * 512 = 32256 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               2    46512336  1465138552+  83  Linux
Partition 1 does not end on cylinder boundary.

 

# dd if=/dev/sde count=195 | od -c -A d |  sed  30q
195+0 records in
195+0 records out
99840 bytes (100 kB) copied, 0.00160348 s, 62.3 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   ?  \0  \0  \0 361   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0099840

 

The parity sync is still running at 80% and drive is unformatted still.....

please post the output of

fdisk -lu /dev/sde

 

(I neglected to ask you to use the "u" option to give the starting sector.)

 

The parity sync will do nothing to fix the unformatted drive.  That will have to be a set of steps you take, but first we need to figure out where the partition really starts.

 

Joe L.

I expected to see something like this:

0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  U 252

0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

*

0097792 376  \v  G  \a  e  \a  -  \0  \a 212 267 001 022  \0  \0  \0

0097808  \0  \0  \0  \0  \0      \0  \0  \0 004  \0  \0  % 254 227  \

0097824 204 003  \0  \0 036  \0  \0  \0  \0  \0  \0  \0  \0 020 314 003

0097840 220  \0 002  \0  R  e  I  s  E  r  2  F  s \0  \0  \0

0097856 003  \0  \0  \0 005  \0 217 016 002  \0  \0  \0 204  ]  \0  \0

0097872 001  \0  \0  \0 353 300 256 263 242 347  N 347 264 362 315 364

0097888 345  V 253 366  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

0097904  \0  \0  \0  \0  \a  \0 036  \0 255 262 303  M  \0  N 355  \0

0097920  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0

 

But I see no evidence of a reiserfs file system being on that disk.  Are you sure this disk was part of your array and assigned as a protected disk?  Did it have files on it?    (it had been previously been formatted in the unRAID server) How sure are you of that?

  • Author

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1              63  2930277167  1465138552+  83  Linux
Partition 1 does not end on cylinder boundary.

 

Hey Joe, I am dam sure it was in the array :)

 

Could I have lost all the files in what happended with the USB key??

 

And does it look like I have lost everything on the disk?

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1              63  2930277167  1465138552+  83  Linux
Partition 1 does not end on cylinder boundary.

 

Hey Joe, I am dam sure it was in the array :)

 

Could I have lost all the files in what happended with the USB key??

 

And does it look like I have lost everything on the disk?

I don't know yet. 

 

The fdisk command shows it is partitioned as "un-aligned" with the partition starting on sector 63.

 

Do you know (or remember) if it was part of the array prior to the 4k-aligned option was available?

Do you think it might have been set up for 4k-aligned? 

 

For you to have lost everything, it would had had to be written to (cleared) by unRAID.  Since you did not start the array (based on what you reported) it should not have been cleared.  If however you did start the array with that "disk will be cleared" warning, it would explain why I do not see the ReiserFS string where expected in the output of the "dd" command.

 

Are you absolutely sure the disk is /dev/sde ??? 

type

ls -l /dev/disk/by-id

to confirm via model/serial number

 

If so, let's read a bit more of the disk using "dd" to see what is there up further.

 

dd if=/dev/sde count=250 | od -c -A d |  sed  50q

 

After you entered the "initconfig" command, did all the indicators on the unRAID web-page turn blue when you refreshed it?

 

Did the warning about clearing drives go away?  (I'm hoping you answer that it did go away.)

 

Joe L.

  • Author

This is the response from the command:

 

 

 dd if=/dev/sde count=250 | od -c -A d |  sed  50q
250+0 records in
250+0 records out
128000 bytes (128 kB) copied, 0.00235361 s, 54.4 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   ?  \0  \0  \0 361   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0128000

 

 

The device is correct, I dont recall starting the array when that one disk was displaying incorrectly but judging from this it looks like i must have. However I dont not recall sitting through a clear of the disks that would have taken awhile :-)

 

All blue lights went green and the check started normally but just that one drive showing as unformatted.

 

The paity thing from running initconfig is now complete but as you would know the drive still shows as unformatted.

 

The 4 K option i am not sure of but the drive was only added a couple of weeks ago.

 

Apologies for the delay, been offsite from the server and thank you for your continued assistance.

Well, the "dd" command is finding nothing on that disk... (literally... it is all zeros once past the first block that holds the MBR and partitioning information.)

 

You can try one or two more "dd" commands to see if it is just the initial part of the drive that is zeroed.

dd if=/dev/sde bs=32768 count=5000 | od -c -A d |  sed  50q

or, the check entire drive  (will take 5 or 6 hours to complete)

dd if=/dev/sde bs=32768 | od -c -A d |  sed  50q

  • Author

Thanks.

 

So is it possible to restore the data to the drive by >

 

1) Format the disk

 

2) Rebuild it from parity as a new drive

 

If this is possible how do I go about it and is there alot of risk to loosing data on the other disks?

 

Thanks again!

  • Author

dd if=/dev/sde bs=32768 count=5000 | od -c -A d |  sed  50q
5000+0 records in
5000+0 records out
163840000 bytes (164 MB) copied, 13.4816 s, 12.2 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   ?  \0  \0  \0 361   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
163840000

 

Would seem the drive is empty :(

 

I am also guessing from doing the initconfig and initiating a parity sync there is know no way to restore the drives contents?

dd if=/dev/sde bs=32768 count=5000 | od -c -A d |  sed  50q
5000+0 records in
5000+0 records out
163840000 bytes (164 MB) copied, 13.4816 s, 12.2 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   ?  \0  \0  \0 361   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
163840000

 

Would seem the drive is empty :(

 

I am also guessing from doing the initconfig and initiating a parity sync there is know no way to restore the drives contents?

unfortunately, true...    :(
  • Author

Bummer...

 

So should I pre clear the disk and then just add it to the array?

 

Cheers for all help!

  • Author

I am thinking of upgrading to version 5 before I re add the disk....

 

If there is any time to do it now is the time :)....

 

Can you advise what version of the 5 series is the most stale and how would I go about upgrading?

 

And is there any chance I will loose data in the upgrade or is it straight forward to upgrade from 4.7 - 5?

 

Cheers for all the help thus far as well!

I would get your array stable with 4.7 first...just to be safe.  Then it is an easy upgrade. 

 

RC4 is the most stable...but, what is your hardware?

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.