local.bin Posted October 11, 2016 Share Posted October 11, 2016 Hi there I am in a position now of not being able to startup. The system boots and goes to the command line, when about a second after reaching the command line I get a segfault and although I can get to telnet, the gui does not load. I have tried in safe mode and the same thing occurs. Any help or direction would be much appreciated please. Thanks in advance. syslog.txt Link to comment
JorgeB Posted October 11, 2016 Share Posted October 11, 2016 You need to start in maintenance mode and run xfs_repair on disk4. If array is set to autostart disable it by editing disk.cfg on your flash drive (in the config folder): change startArray="yes" to "no" Then: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS Link to comment
local.bin Posted October 11, 2016 Author Share Posted October 11, 2016 Hi johnnie.black Thanks for the fast reply Can I do that from the command line, as I am only familiar with seeing that mode on the gui, that I cannot reach. Edit: Ok think I understand, in the the array was set to auto start, so hopefully now I can get to the gui to enter maintenance mode. Link to comment
local.bin Posted October 11, 2016 Author Share Posted October 11, 2016 So I am no getting the following; root@Tower-64:~# xfs_repair -v /dev/md4 Phase 1 - find and verify superblock... - block cache size set to 3055480 entries Phase 2 - using internal log - zero log... zero_log: head block 1607585 tail block 1602099 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Am I able to only mount md4? Link to comment
local.bin Posted October 11, 2016 Author Share Posted October 11, 2016 Thanks, yes, had just used -L and all seems to be back up agaian. Thanks. If I had lost any data should unraid have gone into a restore mode to restore that data from parity? It hasn't so can I assume all my data is in tact... Link to comment
JorgeB Posted October 11, 2016 Share Posted October 11, 2016 Parity can be used to restore a failed disk, not a corrupt filesystem, that always need to be fixed using the filesystem repair tools. Link to comment
itimpi Posted October 11, 2016 Share Posted October 11, 2016 Thanks, yes, had just used -L and all seems to be back up agaian. Thanks. since you had to use the -L option to xfs_repair there is a faint chance metadata applying to the last file or so has been lost. However in my experience that is rare. If I had lost any data should unraid have gone into a restore mode to restore that data from parity?No - that is not the way parity works. You might want to read the user documentation to get a better understanding of how parity works. When you get file system corruption then this is normally also reflected in the parity disk. It hasn't so can I assume all my data is in tact... it is always worth checking you do not have a lost+found folder after running a xfs_repair. Link to comment
local.bin Posted October 11, 2016 Author Share Posted October 11, 2016 Thanks both. I had checked lost+found and it had one file of zero length, so I had assumed I was ok....naively or not! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.