theboing
-
Posts
9 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by theboing
-
-
49 minutes ago, JorgeB said:
Unraid can give an invalid partition error for various reasons like the MBR not conforming to what is expected or the partition not being the correct size, and that can happen when you for example change from a raid controller to a non raid controller or vice-versa, but in your case there are no partitions, so something else happened, if just the partitions are missing but the data is still there you can try unassigning one of the unmountable disks and starting the array, Unraid will recreate the partition and as long as the disks weren't wiped it might be able to rebuild it correctly, check if the emulated disk mounts and data looks correct, if it does, and only if it does, you can rebuild on top, then repeat for the other disks.
I think parity was fine. I didnt think I could rebuild 3 "failed" drives. Do the other drives need to be in the same positions as they were when parity was built? Because I have no idea in which order the used to be in that array back then.
-
It does not look like it, see screenshot.
-
The controller was flashed to IT mode already before the the pendrive broke and working fine then. All 7 drives are connected to this controller. I tried to hook up the troubled drives directly to the mainboard already: same result.
-
Dear Community,
The old machine stopped working (1 or 2 years ago) since the pendrive broke. Upon replacing the pendrive I figured the board was also toast. This weekend (with some spare hardware) I made an attempt to get it all working. The old array has 8 HDDs connected to a IBM m1015 flashed to IT-Mode.
Not knowing the parity drive I added all old drives (4x3TB and 3x8TB) to a new array without parity drive selected. All except one 8TB drive were detected so I assume this is the parity drive. I shut down the array and proceeded to put the new server together (borrowed pieces - doesn’t matter - had to change things) and some hours of swapping hardware pieces in and out I could get my 4 new harddrives to work (its SAS drives, I thought I bought SATA - NARF). In this process the SAS controller of the old array was swapped in and out too.
Once the new server had been put together and seemed to work I reconnected all the old drives to my IBM m1015 SAS controller and started unRaid.
I selected all the drives but the parity and started the array. For some reason 3of the 3TB drives could not be mounted (Unmountable: Unsupported partition layout)
- My guts tell me they didn’t break all together in a matter of hours.
- SMART gives some warning about age, yes.
- They are all Samsung drives, the other 3TB drive is Toshiba.
- They probably are REISERFS, maybe BTRFS, I don’t remember
- Reiserfsck -check gives Unknown code er3k 127, maybe the superblock is toast, maybe it’s not reiserfs
- I have read in the forums some people experience unmountable problems after upgrading unRaid, but I can not tell the exact version I am coming from (at least 1-2 years or more old)
At this point I am more than willing to ask for advice. Tower diagnostics attached.
My current best idea to solve the issue would be to ddrescue one of the unmountable drives to one of the still not used (much bigger) new drives and then start to tinker with reiserfs and BTRFS rescue tools. Since this will be a try and error approach, maybe it is possible to ddrescue into some form of virtual harddrive and tinker on this one. Has anyone experience with this? Any other advice? Is downgrading worth trying?
TLDR: Migrating an old array with broken pendrive and mainboard to a new one, upgrading UnRaid in the process, suddenly 3 drives are not recognized anymore (Unmountable: Unsupported partition layout).
Yes, redundancy is no backup - I know - I am working on it..
Cheers,
boing
-
Thanks for your reply, I see your point and that's why I used to use the exact device you suggest. However that's not my point here. I already bought the fast thing, and I can't give it back, also usb3 is not my problem.
The USB stick I bought is treated as SCSI drive and the unraid installer does not see it as USB stick. That thing appears to be an external hard drive squeezed into the shape of a USB stick.
I hope I could express my problem better this time and I'm afraid I know the answer already.
Is there a reason why unraid won't install to external hard drives?
-
Hi all,
my USB Drive broke and for replacement I thought "This time don't use the shabby old drive laying around, get a new one and make sure it has good reading speed". So I bought a corsair voyager gtx 128 gb usb 3.0 drive, which was tested in the 400MB/s range.
Turns out this device looks like USB stick, walks like one, talks like one, but isn't one. Internally it works more like an external SSD with a USB interface. Windows detects it as SCSI drive and the unraid installer won't let me install to it.
I wasn't aware of this pitfall, won't happen again, but now I have it and I have no other purpose for it. Can I use it somehow anyways to boot unraid from it?
Thanks in advance!
-
I have the exact same issue after rebooting.
192.168.x.y refused to connectTelnet works. I can also reach plugins.
Could you solve it somehow?
-
Is there any chance to get a second instance running?
Unmountable: Unsupported partition layout after hardware changes
in General Support
Posted
I will definetly try this. Right now I am preclearing the new drives and will wait for that to finish. Then I will swap all old drives back in.
Does it matter if I connect them to the IBM m1015 controller (IT mode) or the board?
Just to be sure:
- I will create an array with all old drives and make sure to check "parity already valid"
- I will start the array and 3 drives will be unmountable
- I will stop the array and unassign 1 unmountable drive
- I will start the array again and check on the now emulated drive for files
If I find some files there, is it safe to assume its all there?