Jump to content
allanp81

Syslog full of "blk_partition_remap: fail for partition 1"

13 posts in this topic Last Reply

Recommended Posts

I just noticed that my syslog has been showing the following for the last week:

 

Jun 22 04:52:28 downloadbox kernel: blk_partition_remap: fail for partition 1
Jun 22 04:52:28 downloadbox kernel: XFS (sda1): metadata I/O error: block 0x75513e80 ("xfs_trans_read_buf_map") error 5 numblks 32
Jun 22 04:52:28 downloadbox kernel: XFS (sda1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.

My server seems ok although around midnight last night I did get a few emails claiming that my cache disk was nearly full that seems to be fine once I got up this morning and apart from the email notifications I can't see any errors relating to this in the syslog. I also can't find any references to what sda1 thinks it is, as there is no sda1 listed under system devices.

downloadbox-syslog-20180629-0845.zip

Share this post


Link to post

Unfortunate even the complete syslog on the diags rotated and oldest entry is from July 22 but already shows the same error, we need to see the beginning of the syslog and when the error started, so reboot and if/when the error comes back grab and post new diags.

Share this post


Link to post

Ok, that's not great, I'm almost too scared to reboot in case it doesn't come back!

Share this post


Link to post
5 minutes ago, allanp81 said:

I'm almost too scared to reboot in case it doesn't come back!

It should comeback fine and most likely without the error

Share this post


Link to post
10 minutes ago, johnnie.black said:

It should comeback fine and most likely without the error

 

I've rebooted and so far no errors in the log at all. Will keep an eye on it and post the full diagnostics if it errors again. Thanks for your help.

Share this post


Link to post

Same with me, this happens every so often

I have formatted my USB to clean it up thinking it was the concern, but clearly, it hasn't helped 
anyone know what the issue may be ? 

 

Flash    DataTraveler_3.0 - 15.5 GB

This has seemed to happen since I switched from my original flash drive to this one as I needed more room than my original one from Unraid

 

Jul 23 13:43:41 UnRAID kernel: blk_partition_remap: fail for partition 1
Jul 23 13:43:41 UnRAID kernel: blk_partition_remap: fail for partition 1

unraid-diagnostics-20180723-1751.zip

Edited by bombz

Share this post


Link to post
8 hours ago, bombz said:

Same with me, this happens every so often

Try a different USB port, preferably USB 2.0

Share this post


Link to post

I have changed USB port to 3.0 as I was on the 2.0 header
I also changed the boot device which I think may have been messing it up (but we will see)

I was on:
UEFI - Kingston Flash

Changed to:
Legacy - Kingston Flash

Array is  in parity sync now.... again. As whenever this issue happens I have to use the 'powerdown ' command from console, which then shows 'unclean shutdown' when I boot (When this error happens).

I will know in a few days I am sure if I am running into concerns. 

Share this post


Link to post
17 minutes ago, bombz said:

I have changed USB port to 3.0 as I was on the 2.0 header

USB 3.0 port is not recommended, if you were already on USB 2.0 it can be a failing flash drive (USB 3.0 flash drives are also not recommended as they usually have a much higher failure rate)

Share this post


Link to post

Ah OK. Well, I do have other flash drives here (2.0) This was what I had handy at the time as I couldn't upgrade to 6.0 at the time. I was still using my original USB for years that I bought from UnRaid (version 4.5 era).

I will get a 2.0 device going tonight and request a new key. Thank you for the heads up.

Share this post


Link to post

[SOLVED] (so far)

Interesting.
Parity finished.
I stopped the server to give it a fresh shutdown and reboot and saw this:
Jul 24 18:06:46 UnRAID emhttpd: error: send_file, 139: Broken pipe (32): sendfile: /usr/local/emhttp/logging.htm

 

I think I am going to swap to a USB 2.0 and re-key tonight

Edit:
USB 2.0 Key made bootable.... waiting on reg info (fingers crossed!)

Edit:
Seems the new key has been holding strong. 

Edited by bombz

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now