Hi All,

 

The subject says it all. Can this be done at all?

 

Running 5.0-rc13, with 5 data and 1 parity disk (all 3 TB) cache is 2 TB. There were files on the cache disk which were not moved and some permanent . folders.

 

Attached please find my syslog. I would be extremely grateful if someone could walk me through the steps required to retrieve those files.

 

Thanks.

syslog.zip

See check disk file systems in my sig

 

Hi,

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband Samurai

See check disk file systems in my sig

 

Thank you dgaschk, that does help.

 

However I have one noob question for you, since this is a cache drive what would it be md1/md2 etc? Attaching a screenshot of my main page and disk status. Cache is sdg on that - does that mean anything?

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband - that is what started all this, I have had issues with emhttp crashing and tower not being accessible even via console either (hard reboot is the only option) from RC16 onwards and that still continues with 5.0 (I have tried stock on 5.0 still this happens), I tried and reverted back to RC13 and then this un-formatted issue happened.

 

Thanks for all your help.

OK apparently I am not the only one having this issue.

 

I just tried to upgrade to final 5.0 and can not start the server back.

I am using 3 disk setup basic version.

the only thing installed was unMenu and SNAP.

I have removed SNAP, not sure how to un-install unMenu

but I have edited the go file and remove everything

 

the server boots, I can access the main page one time, but as soon as I start the array it become unaccessible from anywhere but console.

where I can only issue the reboot command.

the old flash setup works just fine.

 

 

 

OK apparently I am not the only one having this issue.

 

I just tried to upgrade to final 5.0 and can not start the server back.

I am using 3 disk setup basic version.

the only thing installed was unMenu and SNAP.

I have removed SNAP, not sure how to un-install unMenu

but I have edited the go file and remove everything

 

the server boots, I can access the main page one time, but as soon as I start the array it become unaccessible from anywhere but console.

where I can only issue the reboot command.

the old flash setup works just fine.

 

Mine is the same except for the fact that after starting the array I cannot access it even via console, so I have to hard reboot every time (which I hate to do, but this is the only option unfortunately). I have tried removing all the plugins renaming the config/plugins, boot/extra, boot/plugin etc and reverted to stock go file. I haven't tried removing UU though. But problem still exists. Not sure why.

well my next step is to simply get the brand new fresh setup on flash drive

and recreate the array and shares manually and see if it works.

I wonder if I create a new share and point to the existing folder, it should keep the data, I think.

 

See check disk file systems in my sig

 

Thank you dgaschk, that does help.

 

However I have one noob question for you, since this is a cache drive what would it be md1/md2 etc? Attaching a screenshot of my main page and disk status. Cache is sdg on that - does that mean anything?

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband - that is what started all this, I have had issues with emhttp crashing and tower not being accessible even via console either (hard reboot is the only option) from RC16 onwards and that still continues with 5.0 (I have tried stock on 5.0 still this happens), I tried and reverted back to RC13 and then this un-formatted issue happened.

 

Thanks for all your help.

 

Use /dev/sdg1 to check the cache disk. Do not forget the trailing number 1.

OK apparently I am not the only one having this issue.

 

I just tried to upgrade to final 5.0 and can not start the server back.

I am using 3 disk setup basic version.

the only thing installed was unMenu and SNAP.

I have removed SNAP, not sure how to un-install unMenu

but I have edited the go file and remove everything

 

the server boots, I can access the main page one time, but as soon as I start the array it become unaccessible from anywhere but console.

where I can only issue the reboot command.

the old flash setup works just fine.

 

The go file should not be empty. See my sig.

OK apparently I am not the only one having this issue.

 

I just tried to upgrade to final 5.0 and can not start the server back.

I am using 3 disk setup basic version.

the only thing installed was unMenu and SNAP.

I have removed SNAP, not sure how to un-install unMenu

but I have edited the go file and remove everything

 

the server boots, I can access the main page one time, but as soon as I start the array it become unaccessible from anywhere but console.

where I can only issue the reboot command.

the old flash setup works just fine.

 

Start a new thread.

well my next step is to simply get the brand new fresh setup on flash drive

and recreate the array and shares manually and see if it works.

I wonder if I create a new share and point to the existing folder, it should keep the data, I think.

 

The shares will be added with default settings automatically.

See check disk file systems in my sig

 

Thank you dgaschk, that does help.

 

However I have one noob question for you, since this is a cache drive what would it be md1/md2 etc? Attaching a screenshot of my main page and disk status. Cache is sdg on that - does that mean anything?

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband - that is what started all this, I have had issues with emhttp crashing and tower not being accessible even via console either (hard reboot is the only option) from RC16 onwards and that still continues with 5.0 (I have tried stock on 5.0 still this happens), I tried and reverted back to RC13 and then this un-formatted issue happened.

 

Thanks for all your help.

 

Use /dev/sdg1 to check the cache disk. Do not forget the trailing number 1.

 

Thank you. Will run reiserfsck and see if it fixes it all good.

See check disk file systems in my sig

 

Thank you dgaschk, that does help.

 

However I have one noob question for you, since this is a cache drive what would it be md1/md2 etc? Attaching a screenshot of my main page and disk status. Cache is sdg on that - does that mean anything?

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband - that is what started all this, I have had issues with emhttp crashing and tower not being accessible even via console either (hard reboot is the only option) from RC16 onwards and that still continues with 5.0 (I have tried stock on 5.0 still this happens), I tried and reverted back to RC13 and then this un-formatted issue happened.

 

Thanks for all your help.

 

Use /dev/sdg1 to check the cache disk. Do not forget the trailing number 1.

 

No errors found on check, should I still run --fix-fixable?

See check disk file systems in my sig

 

Thank you dgaschk, that does help.

 

However I have one noob question for you, since this is a cache drive what would it be md1/md2 etc? Attaching a screenshot of my main page and disk status. Cache is sdg on that - does that mean anything?

 

Just wanted to ask if you have upgraded to Release 5 yet?

 

Sideband - that is what started all this, I have had issues with emhttp crashing and tower not being accessible even via console either (hard reboot is the only option) from RC16 onwards and that still continues with 5.0 (I have tried stock on 5.0 still this happens), I tried and reverted back to RC13 and then this un-formatted issue happened.

 

Thanks for all your help.

 

Use /dev/sdg1 to check the cache disk. Do not forget the trailing number 1.

 

No errors found on check, should I still run --fix-fixable?

 

No. That would be a mistake.

Disable all add-ons or update to version 5 and start in safe mode. Is the drive still not mounting?

 

Upgrade to version 5. It has a change that may address this.

Disable all add-ons or update to version 5 and start in safe mode. Is the drive still not mounting?

 

Upgrade to version 5. It has a change that may address this.

 

Did that and it is now running in safe mode and the drive is showing up formatted and all data is accessible, so Thank you for that dgaschk.

 

Now how do I got about installing a few plugins that I need - say SAB, CouchPotato, SickBeard, Plex etc - all these and more were installed before but I can live with these and UU probably. Do I have to start installing these from scratch and configure them again, or is there a way I can just copy some .cfg files over from my rc13 backup and have them working as as they used to?

Disable all add-ons or update to version 5 and start in safe mode. Is the drive still not mounting?

 

Upgrade to version 5. It has a change that may address this.

 

Did that and it is now running in safe mode and the drive is showing up formatted and all data is accessible, so Thank you for that dgaschk.

 

Now how do I got about installing a few plugins that I need - say SAB, CouchPotato, SickBeard, Plex etc - all these and more were installed before but I can live with these and UU probably. Do I have to start installing these from scratch and configure them again, or is there a way I can just copy some .cfg files over from my rc13 backup and have them working as as they used to?

 

If you know which files to copy then you can, otherwise reinstall.

Would the plg files in the boot/config/plugins and the cfg files be all that I need?

 

Sent from my SCH-I535 using Tapatalk now Free

 

Would the plg files in the boot/config/plugins and the cfg files be all that I need?

 

Sent from my SCH-I535 using Tapatalk now Free

 

Yes. The cfg files will tell the plug-ins where to install everything/which port to run, etc.