Hello!

 

During the update I deleted my usb drive. Now r9 is running but none of my drives are assigned. Great! Is there any possibility to find out which drive is part of which slot.

 

Thanks!

I'm guessing you don't have a backup screenshot of your unraid, or your flash backup as per the upgrade instructions?

 

http://lime-technology.com/wiki/index.php?title=UnRAID_Server_Version_5.0-beta_Release_Notes

 

 

 

 

No...that would be easy.:-(

 

Maybe there is a possibilty to do it by telnet? I don't know.

 

Last resort would be putting every drive on my windows box and copy back all the data. That would be a real pain.

 

 

No...that would be easy.:-(

 

Maybe there is a possibilty to do it by telnet? I don't know.

 

Last resort would be putting every drive on my windows box and copy back all the data. That would be a real pain.

Is the array still up on the old release, or have you rebooted?  If still running the older release, before you deleted everything, log in via telnet and type:

cat /proc/mdcmd | strings | grep -i id

DiskId.0 is the parity disk, DiskId.1 is disk1, etc.  They are all listed there with their model/serial numbers.

 

Might also want to do

fdisk -lu /dev/sdX

on each of your disks and capture the output for reference.  It will tell you if the partition start is on sector 64, or 63, or 1.

 

Then, load a new version of unRAID onto the flash drive, assign the disks back to their respective slots.  If you are using any of the paid versions of unRAID, you'll need to put the .key file back on the flash drive too.  Then, you'll need to re-create any users, and perform any local configuration of permissions, etc.

 

Your situation is not much different than one where the flash drive dies, or the family dog eats it, or the two-year-old child takes it and you cannot find where they hid it.

 

Joe L.

Thanks Joe!

 

No...sorry but I restarted the server with a newly formated  usb drive (r9a on it). It is now up and running and showing the disks as unassigned:

 

root@Tower:/mnt# fdisk -lu /dev/sda

 

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes

1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sda1              63  2930277167  1465138552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

This is for sda. I can see that it starts at 63.

 

And:

 

root@Tower:/mnt# cat /proc/mdcmd | strings | grep -i id

mdState=ERROR:NO_RAID_DISKS

mdNumInvalid=0

mdInvalidDisk=0

diskId.0=

rdevId.0=

diskId.1=

rdevId.1=

diskId.2=

rdevId.2=

diskId.3=

rdevId.3=

diskId.4=

rdevId.4=

diskId.5=

rdevId.5=

diskId.6=

rdevId.6=

diskId.7=

rdevId.7=

diskId.8=

rdevId.8=

diskId.9=

rdevId.9=

diskId.10=

rdevId.10=

diskId.11=

rdevId.11=

diskId.12=

rdevId.12=

diskId.13=

rdevId.13=

diskId.14=

rdevId.14=

diskId.15=

rdevId.15=

diskId.16=

rdevId.16=

diskId.17=

rdevId.17=

diskId.18=

rdevId.18=

diskId.19=

rdevId.19=

diskId.20=

rdevId.20=

diskId.21=

rdevId.21=

diskId.22=

rdevId.22=

diskId.23=

rdevId.23=

 

Now I have to know to which slot the drive should be assigned. How can I figure that out?

 

Thanks again!

All the disks, including the parity drive will show some partitioning.  Record the result of fdisk -lu /dev/sdX for all.  (You might need it later)

 

Safest way to identify the drives involves using unMENU  (the add-on many install to aid in the management of the array)

Some will say just assign the disks to the array, but I suspect there is a bug that overwrites the MBR record when the super.dat file is missing as it is in your case, therefor, I suggest you identify the disks using unMENU.  Do not assign the disks to the unRAID array just yet.

 

Since no drives are assigned to the array, all the drives should show on the unMENU "Disk-Management" page as not assigned to the array.

Drives with file-systems should have a "Mount" button.  Mount each in turn (they will be mounted as read-only) then share the drive on your LAN.  Based on the contents, identify what is on it.  DO NOT WRITE TO ANY DISK, DO NOT RE-MOUNT THEM AS WRITABLE.

 

If you do not want to install unMENU, you can attempt to mount each of the disks in turn yourself by typing the following commands:

mkdir -p /tmp/mountpoint

mount -r -t reiserfs /dev/sdX1 /tmp/mountpoint

(Note, you always mount the first partition, which is the device name with a trailing "1" as shown in the example above.  /dev/sdX1, not /dev/sdX.)

 

if it mounts, you can see the contents by typing

ls -l /tmp/mountpoint

 

Then, un-mount the disk by typing

umount /dev/sdX1

(note, it is umount, not unmount)

 

 

The parity disk will not be able to be mounted. (It does not have a file-system on it)  Only one drive should be un-mountable. (the parity drive)

 

Un-share and un-mount each data drive once you have examined the contents.

 

then, once all are un-mounted, assign the drives in the unRAID disk assignment screen and start the array.

Okay:

 

1. Wrote down all information on my disks: fdisk -lu /dev/sdX

2. Installed unmenu

3. Mounted sda

 

On telnet I can see:

 

root@Tower:/mnt/disk/sda1# ls

Backup/  Music/  Photo/  Video/

 

This folder structure will be found on every drive on my array.

 

Question:

 

I don't really get, how I figure out which drive should be assigned to which slot on the unRAID-GUI.

 

So far I understand:

 

I can't assign a drive to a slot which it hasn't been assigned on my old installation (before formatting the USB drive). This will result in data loss.

 

However:

 

sdn is found as parity drive.

 

Thanks!

 

Bye.

 

 

So far I understand:

 

I can't assign a drive to a slot which it hasn't been assigned on my old installation (before formatting the USB drive). This will result in data loss.

You understand incorrectly (for your situation.) You can assign any data disk to any possible data slot, even if not used previously, as you are setting a new initial configuration, but with existing data)

Thank you VERY much. The array is up and running and starting the parity-sync right now. To avoid such a stressful experience in the future I made a screenshot of my disks and saved it on a save place.

 

Have a nice weekend!

 

Thanks!

 

Also back up your flash.