JorgeB
-
Posts
67,416 -
Joined
-
Last visited
-
Days Won
705
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
Then only a reiserfs maintainer could help, best bet is probably using a data recovery software, all data should be recoverable.
-
Do you still get an error if you do: reiserfsck --rebuild-sb /dev/mdX Looks fine to me. Xfs is probably the best option for most users.
-
For some reason there's no SMART report for disk7.
-
Should already be fixed, it was a journal problem.
-
https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
-
It's an option, you could also make a clone with dd to another disk before starting.
-
rm -r "*" -
Update to latest Unraid, some earlier release have a bug in the reiser tools, latest reiserfsck is 3.6.27
-
Merely doing this on a regular SATA controller would be perfectly safe (except your parity getting out of sync like mentioned), so something is missing here, but the only solution I see now (except for disks 2 and 4 if reiserfsck works) would be to rebuild the reiserfs superblock, then each disk will likely need reiserfsck --rebuild-tree.
-
On the other server were they used on a RAID controller?
-
You are absolutely sure disks all disks were reiserfs? A reseirfs superblock is missing from most disks, this either means they are not reiser or something destroyed or moved the original superblock, e.g. using the disks on some RAID controllers. A superblock is being found for disks 2 and 4 and ruining reiserfsck should fix them, though there some are some older releases that include a buggy reiserfsck, don't remember now which ones, so best to update to latest Unraid first.
-
Did you ever use ddrescue before? If yes delete the log file (/boot/ddrescue.log) or use a different name.
-
Likely the same as this, if you like you can add your experience there, better chance of getting noticed by LT.
-
It will work and it's IT mode only, so no need for flashing, though it might still need a firmware update if it's on a very old one, but that's very easy. like a BIOS update. As for the price it's about right for a new one, you might look on ebay for used server pulls, I got two some time ago for around $75 each, with cables.
-
Use " or escape the spaces with \, e.g.: "/mnt/path to folder" or /mnt/path\ to\ folder/
-
Unless the disks were mounted read only this will make your parity out of sync. Please post the diagnostics: Tools -> Diagnostics
-
That's a long time, doubt it will finish if it hasn't yet. Other disks being read is normal since you have turbo write enable.
-
This might help with the crashing.
-
Anyone can post in the Feature Requests forum, just not the sub-forums.
-
Those are usually flash drive related, run chkdsk on it.
-
Reboot, try ddrescue again (re-check disk identifiers, they could change), and if it fails post new diags.
-
That would make it impossible to use different size disks or still access disks individually on a different system if needed, and you already have FreeNAS for that. You can't create a zfs pool of multiple zfs filesystems.
-
Single Disk cannot be accessed but is still "green"
JorgeB replied to kr4sv's topic in General Support
Possibly a problem with the SASLP, do you have another controller you could use? SASLP/SAS2LP are not recommended for a long time. -
Go to Bradcom's support site and download the firmware package, instructions are inside, you need to boot with a DOS flash drive, or install the HBA in a Windows PC to do the update.
-
Delete this folder
