I fear I just now wrecked a brand new 4TB drive. As per the manual, I replaced a 2TB drive with the new 4TB. but after powering up the unit, I was not able to reach the webGUI. For some (stupid) reason I decided to reboot the unit (running 5.05). But again - no webGUI. After putting back the "old" 2TB drive, the system runs perfect again. Having read some threads, I think that I interrupted the process that expands reiserfs to the replacement disk.

 

I would be very grateful for feedback on whether and how I could save my new disk.

 

Thank you.

How large is your parity drive?

Do you have a console (monitor and keyboard)? Are you sure it is booting into unRAID?

Thank you.

 

Parity is also 4TB.

 

I'm not 100% sure, but when I telnet to the box, MC will show all drives (including disk1 - the new 4TB drive). At the moment the unit is headless, but if need be I could try to get a keyboard and monitor from friends or family.

 

Again, many thanks and Happy New year!

Normally what happens when you replace an existing drive is the GUI will show the array stopped and the old disk will show as missing. Then you can select the new drive and then start the array, which will rebuild the new disk with the contents of the old disk. The "expansion" you mention will not happen until you select the new disk and start the array so if you never got the GUI the array should not have started.

 

Post a syslog.

I left the unit with the 4GB drive powered on for several hours, still nothing. After a reboot of the system (with 4GB) still nothing. Again, I can telnet without any problems and strangely enough disk1 (=4TB) shows up. I checked for a syslog, but the only one I find is the most recent one when the "olds drive was in the unit. It seems as if no syslog is created.

 

Do I really need a console even if I can telnet to the unit?

 

Again, many thanks for your kind support for this n00b   

The current syslog is in /var/log.

 

cat /var/log/syslog

 

to view it in your telnet session then maybe you can copy/paste it somewhere for posting, or

 

cat /var/log/syslog > /boot/syslog.txt

 

to write it to the flash.

 

Thanks @trurl!

 

As per your instructions the current syslog attached. I hope that the experts can make something out of this.

 

Take care

 

 

EDIT:

I feel so stupid and sincerely apologize for taking your time. It turns out that I was trying to replace the cache drive. So stupid! Mind you, when building the (16 drive) unit I was keen on labeling the brackets. But then you still have to mind the labels when you start the replacement. I'm very sorry.

 

Anyway, Happy New year!

syslog_.txt.zip