gnollo
-
Posts
687 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by gnollo
-
-
Yes copying the config folder across worked well, server up and running, will now test emby
-
5 minutes ago, johnnie.black said:
In case you still need that you just need to copy the config folder.
Thanks Johnnie Black I will do that as soon as Rufus has done its business.
-
Tried to do the same on the original flash, once completed, windows announced that there were problems on the flash, and asked to scan and fix, which I did.
Now trying rufus on it again, this time I added
- check device for bad blocks
- unticked quick format
-
Using Rufus, I created a syslinux 6.04 bootable flash with it, on a 32 Gig Sandisk key making sure I ticked compatibility with old motherboards.
Then I copied the unraid files for a brand new installation from the zip install file.
This time it has done it, so it looks like some of the files on the flash that I was using are corrupted.
What do I copy across to get the server back up and running?
I plan to follow the same process on the flash which is registered, so I can copy across the key for a start.
-
I created a new flash drive, and copied the content of the old key, also fails.
-
Just tried pulling each ram stick out one at a time, still getting kernel panic
Sent from my SM-A520F using Tapatalk -
Just tried booting in "unRAID OS Safe Mode no plugins, no GUI)", same result
-
I moved the server from a room to another, and now it won't boot because of kernel panic.
I checked all the connection, and they seem in place.
Never had this before so I am unsure what to do next.
Any help appreciated. Screenshot of the screen attached
-
Just completed a parity check, 0 errors, everything is looking good.
-
and diagnostics attached
-
Parity rebuild completed. Duration 1 day, 2 hr, 55 min, 32 sec Speed 103.2 MB/s errors 0 Status OK
-
Thanks trurl, I will incorporate that in my monthly routines, and post a syslog once parity has been constructed in 17 hours time.
-
Hi trurl, thanks for commenting, it' useful because I never really paid attention to what type of parity check is in progress. That particular parity check started upon booting automatically after an unclean shutdown due to a power outage, which type would that be, in your opinion?
I don't regularly perform parity checks, which I guess I should start doing on a regular basis. Which type of parity checks should I perform and how often would you suggest?
This drive that has filesystem issues used to be the parity drive. I bought a new 10TB drive to replace a drive that was showing pending sectors, but as it was the largest drive I have, it ended up becoming a copy of the old parity (bit more history in the thread below). I rebuild the drive with pending sectors using the old parity as replacement (8TB drive). So the drive was rebuild over two months ago. I still have the replaced drive, and I used Checksum Compare, a windows app, to check all the movie files across the old and replacement drive, which gave thumbs up for all the files.
-
Started a fresh new config, parity date rebuild in progress, 28 hours to go.
-
So I guess next step is new configuration? This time I just calculate parity from scratch? Does this overcome the system file corruption?
Sent from my SM-A520F using Tapatalk -
Just loaded the drive in unassigned devices, and I can access folders and download files.
-
Failed to open the device '/dev/md2': Unknown code er3k 127
-
9 minutes ago, johnnie.black said:
Though not sure it will work since now unlike in the previous diags it's not detecting a valid reiser filesystem, if reiserfsck doesn't work check if the old disk mounts with UD, if yes and no new data was written since it got disabled it might be better to do a new config and re-sync parity instead.
What is UD? I have started the array in maintenance mode and clicked on CHECK for drive 2.
It says "running" below the following message "reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md2 Will put log info to 'stdout'"
-
Thanks Joe, do I put the disk back in? How do I peform a filesystem check? Sorry but I am really out of my depth with this issue.
-
Ok replaced the cable, still no mounting and no drive access after starting the array.
Then I actually removed the drive physically from the server.
And rebooted it.
The UI still shows "Disk 2 not installed Unmountable: No file system"
And I cannot see a folder next to it.
And I cannot see data being emulated, or a drive being emulated.
No read errors now.
Diagnostics which I just donwloaded also attached.
-
Ok turned the server off until I replace the cable.
-
No folder for me to click on the right side of the WebUI either
-
I will swap cables later on, can't access that room for another 3 hours. Why cant I access the emulated data? Is parity also fuxored?
-
I did move the drive with read errors just now from the third Norco, so perhaps I have cabling issues on that one, so i will swap cables on that drive next.
I am now running 10 drives in two cages, trying to reduce elements of errors and so i could double up on the power connectors.
Kernel Panic - Not Syncing: VPF: Unable to mount root fs on unknown-block [SOLVED]
in General Support
Posted
Everything works well, solved