Tried to backup flash > corrupted thumbdrive

[aglyons]

This is a brand new Samsung Flash drive. I've had the system for about two weeks.

 

6.10 is released and it was advised to take a backup of the original flash. So I did. The file would start to DL but stop after a minute or so.

 

The webUI became non-responsive so I had to restart via SSH (powerdown -r).

 

Tried to backup again and the same thing happened. The file would start to DL but stall. WebUI again non-responsive.

 

Restart again via SSH and now the system will not come back up. It's sitting at;

 

/var/tmp/indent.cfg: line 35: unexpected EOF while looking for matching `"'

/var/tmp/ident.cfg: line 36: syntax error: unexpected end of file


Welcome to Linux 5.10.28-Unraid x86_64 (tty1)
(none) login:

 

Tried a full powerdown of the system and still won't come back up again.

Edited May 18, 2022 by aglyons

[trurl]

Put flash in PC and checkdisk, while there make a backup, try booting from USB2 port.

[aglyons]

10 minutes ago, trurl said:

Put flash in PC and checkdisk, while there make a backup, try booting from USB2 port.

 

Thanks, Ill try that. I did try safe mode with GUI. The built-in Firefox loading localhost failed to load any page. That would tell me that unRaid was not running. Something is borked.

[aglyons]

chkdsk reported no errors.

 

I only have three USB ports on the Dell R510. The external USB ports are home to a UPS and keyboard. The internal USB was my boot connection. It's been stable ever since I first installed everything.

 

I've made a BIN backup image of the thumbdrive. Will try to start it up again.

[aglyons]

No go,

 

System is screwed. How can I get this back up with the current config working?

[aglyons]

I managed to get the system started again.

 

I took a look at the ident.cfg file, specifically lines 35 and 36.

 

 

I deleted line 35 and line 36. Added a LF so that there was an empty line 35. I decided this due to the default ident.cfg file being formatted that way. I'm not sure what line 35 board" was supposed to be or if it was added by a plugin update.

 

Somehow this file was changed during the backup process that hung the system.

 

I'm not sure if I should go forward with an update to 6.10 at this point or if there are any other diagnostics I can do to make sure the system is stable enough to upgrade.

 

Edited May 18, 2022 by aglyons

[trurl]

6 hours ago, aglyons said:

what line 35 board

Probably corruption of that file.

 

6 hours ago, aglyons said:

any other diagnostics

Attach diagnostics to your NEXT post in this thread

[aglyons]

Diagnostics.....

knoxx-diagnostics-20220518-0949.zip

 

Some lines in the syslog that jump out to me

172

285

392

406

629

927-931

967

 

Edited May 18, 2022 by aglyons

[trurl]

Lots of things during startup are normal, just the result of linux/Unraid trying to figure out your hardware.

 

You have duplicate lines in your go file, you should clean that up.

[aglyons]

15 minutes ago, trurl said:

Lots of things during startup are normal, just the result of linux/Unraid trying to figure out your hardware.

 

You have duplicate lines in your go file, you should clean that up.

 

 

How could I get duplicate lines in the go file? I've never edited that myself. This could only have to come from plugins being installed.

Edited May 19, 2022 by aglyons

[trurl]

I seriously doubt any plugin added anything to your go file

 

Here is the standard contents of go:

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

 

After those lines, your go has:

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &

#rsync daemon
rsync --daemon --config=/boot/config/rsyncd.conf

 

So, not only duplicate starting of emhttp, but another line that you must have added as some point.

 

16 minutes ago, trurl said:

you should clean that up