is it just me or is there a large number of issues coming up with the most recent upgrades relating to disk mounting issues due to corruption or mismatched partition records or similar... I wonder if there are some proactive/preventative checks/scans that could be done ahead of upgrading, that might help identify, mitigate or correct these sorts of things before people upgrade and find out the hard way... e.g. file system checks in maintenance mode? or similar?

1 hour ago, warpspeed said:

is it just me or is there a large number of issues coming up with the most recent upgrades relating to disk mounting issues due to corruption or mismatched partition records or similar...

There are some cases where pools are failing to mount, Unraid 7.1 uses lsblk to get the partition details, this is part of the uitl-linux package, and in some cases the lsblk output is not showing all the fields, half the times the issue is caused by having an old zfs signature on the device(s), that can be easily resolved by wiping it, but the other half root cause is currently unknown, there's an open issue with the package maintainers, but no progress for now, the easiest way to test may be to just upgrade, and if one or more pools don't mount after, grab the diags, post a bug report and downgrade, but you can also test before updating by looking at the output of the command below for all pool devices (7.0.0 or newer required):

 

lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/sdX

or

lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/nvmeXn1

 

This is OK:

May 12 11:37:48 DXP-2800 emhttpd: /bin/lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/nvme0n1 2>&1
May 12 11:37:48 DXP-2800 emhttpd: disk 	nvme0n1 	1000204886016 dos
May 12 11:37:48 DXP-2800 emhttpd: part 1 nvme0n1p1 2048 1000203837440 dos 0x83

 

This one is not, it's missing the PARTN (1) and PARTTYPE (0x83), these are typically the ones that have a dual signature and can be easily fixed, they are caused by a recent util-linux change:

root@Test5:~# lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/sdk
disk sdk 	120034123776 dos
part sdk1 2048 	120033075200 dos

 

This one is also not OK, it's missing PTTYYPE (dos), and the cause is unknown at the moment:

May 12 11:37:48 DXP-2800 emhttpd: /bin/lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/nvme1n1 2>&1
May 12 11:37:48 DXP-2800 emhttpd: disk 	nvme1n1 	1000204886016
May 12 11:37:48 DXP-2800 emhttpd: part 1 nvme1n1p1 2048 1000203837440 0x83

 

I believe that LT may also be considering no longer using lsblk for this in a future release, if there's no quick fix for the current issues from the util-linux maintainers.

I fell at the first hurdle trying to update Pro, 7.1.0

When I try to backup the Flash drive, after a couple of seconds I get:

 

 Creation error

 Insufficient free disk space available

 

Which is confusing!  Which disk is it trying to use?  The Flash drive is 16GB with 1.57GB in use, the array disks have not less than 218GB free - where's it trying to put the backup, and how do I solve this, please?

 

4 minutes ago, HDRW said:

Creation error

 Insufficient free disk space available

How much RAM do you have?

4 minutes ago, JorgeB said:

How much RAM do you have?

8GB, showing 14% in use

 

30 minutes ago, HDRW said:

8GB, showing 14% in use

Please create a new bug report and post the diagnostics.

7 hours ago, HDRW said:

I fell at the first hurdle trying to update Pro, 7.1.0

When I try to backup the Flash drive, after a couple of seconds I get:

 

 Creation error

 Insufficient free disk space available

 

Which is confusing!  Which disk is it trying to use?  The Flash drive is 16GB with 1.57GB in use, the array disks have not less than 218GB free - where's it trying to put the backup, and how do I solve this, please?

 

It's creating the backup and storing it in RAM I believe.

7 hours ago, JorgeB said:

Please create a new bug report and post the diagnostics.

Done!

Just adding a positive outcome: Updated yesterday from 7.0.0 (after backup, plugin/docker updates) and it went smoothly.

I especially appreciate how snappy my Docker page loads now. I also switched back from ipvlan to macvlan, and that's working totally fine. I was worried about doing this from v6 issue reports.

Thanks Unraid Devs

20 hours ago, JorgeB said:

lsblk -lnbo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE /dev/sdX

This one didnt work for me without taking out PARTN (6.12.15).

I wonder if these would be useful added into the Upgrade Assistant or Fix Common Problems

1 hour ago, warpspeed said:

This one didnt work for me without taking out PARTN (6.12.15).

Right, forgot to mention, the full command only works with 7.0.0 or newer, will edit the post.

Update from 7.0.1 to 7.1.2 went mostly ok.

The first reboot attempt failed and I was asked to reboot the server by pressing "enter" on the keyboard.

But the second reboot went ok, and so far it seems the device updated to Unraid OS 7.1.2 without other issues.

I all, i upgraded my 3 servers and on of them as a problem, i lost all my drive... i need help please, what i did wrong ???

i did revert to the previous upgrade but nothing appeared back.

Edited May 22, 20251 yr by AndreB

3 hours ago, AndreB said:

i need help please

Please create a new thread in General support with details and your diagnostics.

https://forums.unraid.net/forum/55-general-support/

When trying to upgrade, I get: boot device shows 556597248 free but upgrade needs 828638589

I assume I need to either clear up some space or get a new flash drive. Is there anything on the flash drive that is safe to delete prior to upgrade? There is a "previous" folder. I assume this is an old backup? Can I delete the contents of this folder?

Thank you.

5 hours ago, patm95 said:

There is a "previous" folder. I assume this is an old backup? Can I delete the contents of this folder?

It will have the previous release you were using, and yes, you can delete that.

9 hours ago, patm95 said:

There is a "previous" folder. I assume this is an old backup? Can I delete the contents of this folder?

Make a Backup of the Flash Drive first. Then you can roll back easily if you have to.

22 hours ago, AndreB said:

I all, i upgraded my 3 servers and on of them as a problem, i lost all my drive... i need help please, what i did wrong ???

i did revert to the previous upgrade but nothing appeared back.

Have you tried using another browser to access the GUI, or clear the cache of your browser and restart. Just to clear that out.

Edited May 23, 20251 yr by MartyMcfly

Yes all five of them, edge, brave, Opera, Firefox and Chrome all the same problem no drive...

and safe mode i see all drive but i can't do anything here so i rebooted in and all is the same no Drive

After several hard lock ups and after one of my NVME drives showing 'Unmountable disk present', my main cache drive that holds my appdata is now giving me the same error. I have no logs or any indication as to what may have caused it other than the latest update 7.1.2.

Everything happened out of the blue. I looked around and have seen a few other people having similar issues on 7.1.2 and I am at a complete loss since i had to format my family Minecraft servers and backups on the first NVME drive that had this happen.

I would greatly appreciate any methods or advice as to how to possibly resolve the issue or if this is something that is being looked to potentially save others from a similar fate. I am super bummed at the moment about not having my Home Assistant up as well as not having my game servers anymore.

Best of luck everyone and store back ups separately! I know this but.....yeah...

All the best!

2 hours ago, LoveyDov3 said:

After several hard lock ups and after one of my NVME drives showing 'Unmountable disk present', my main cache drive that holds my appdata is now giving me the same error.

Please create a new the on the general support forum and post the diagnostics.

3 hours ago, AndreB said:

and safe mode i see all drive but i can't do anything here so i rebooted in and all is the same no Drive

If it works in safe mode, it suggests a plugin is the problem, you can try to disable them all and re-enable one by one, if you need more help, please start a new thread on the general support forum.

I just want to report a bug.

When I restart a VM the whole Unraid Server is restarting/crashing. Downgraded to 7.0.1 and restarting works without problems.

upgrade from 7.0.1

I see this now in my unassigned historical devices list. I'm sure they are safe to remove (?), but don't know why they show up there in the first place. Is this something to do with the update or maybe do I have another issue?

Other than this, update went smooth and all is working as expected so far.

13 hours ago, wirenut said:

upgrade from 7.0.1

I see this now in my unassigned historical devices list. I'm sure they are safe to remove (?), but don't know why they show up there in the first place. Is this something to do with the update or maybe do I have another issue?

Other than this, update went smooth and all is working as expected so far.

This is probably related to Unassigned Devices, not base Unraid.

But you should be able to hide those with a toggle :