luksak Posted October 10, 2016 Author Share Posted October 10, 2016 Well, I have to buy another disk and rebuild two disks... Lets try this: The error of sfdisk suggests to use the --no-reread option to ignore that the disk is in use. I did so and got this: sfdisk /dev/sdc1 --no-reread /dev/sdc1: device contains a valid 'reiserfs' signature; it is strongly recommended to wipe the device with wipefs( if this is unexpected, in order to avoid possible collisions Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Disk /dev/sdc1: 2.7 TiB, 3000592932352 bytes, 5860533071 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. Since I have a backup I could try this on the new disk. Could you tell me what I have to do now? Quote Link to comment
JorgeB Posted October 10, 2016 Share Posted October 10, 2016 Could you tell me what I have to do now? Don't know, because sfdisk is not detecting the existing partition, nor its starting sector, output should look similar to this: Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F6042B07-7C4A-4781-83EE-991D98AE6CD1 Old situation: Device Start End Sectors Size Type /dev/sdb1 64 5860533134 5860533071 2.7T Linux filesystem Type 'help' to get more information. Quote Link to comment
luksak Posted October 11, 2016 Author Share Posted October 11, 2016 Oh ok. Maybe I could try a clean unRAID install? Quote Link to comment
JorgeB Posted October 11, 2016 Share Posted October 11, 2016 That or you can try that disk alone on another using a unRAID trial key. Quote Link to comment
luksak Posted October 17, 2016 Author Share Posted October 17, 2016 Ok, I'll try that. Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 It took me some time to get a screen because my array runs headless otherwise... So on a fresh unRAID install i have the same issue with sfdisk: root@Tower:~# sfdisk /dev/sda1 /dev/sda1: device contains a valid 'reiserfs' signature; it is strongly recommended to wipe the device with wipefs( if this is unexpected, in order to avoid possible collisions Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... FAILED This disk is currently in use - repartitioning is probably a bad idea. Umount all file systems, and swapoff all swap partitions on this disk. Use the --no-reread flag to suppress this check. Quote Link to comment
RobJ Posted December 27, 2016 Share Posted December 27, 2016 I've never used sfdisk, so I'd rather rely on johnnie.black's experience here. But I noticed that you are using sda1 instead of sda, and in my experience, fdisk tools (and probably fdisk variants like sfdisk) work on drives, managing their partitions. Both are devices but sda is a drive device and sda1 is a partition device on sda. I also noticed that earlier (October 10) you used sdc1 not sdc. Johnnie.black's example used sdb, not sdb1. It also appears to be busy this time, something using it, so you want to be sure you are selecting the right drive, and that it's not part of an unRAID array (or the array is stopped). Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 I've never used sfdisk, so I'd rather rely on johnnie.black's experience here. But I noticed that you are using sda1 instead of sda, and in my experience, fdisk tools (and probably fdisk variants like sfdisk) work on drives, managing their partitions. Both are devices but sda is a drive device and sda1 is a partition device on sda. I also noticed that earlier (October 10) you used sdc1 not sdc. Johnnie.black's example used sdb, not sdb1. It also appears to be busy this time, something using it, so you want to be sure you are selecting the right drive, and that it's not part of an unRAID array (or the array is stopped). Good catch! That's why you're getting the busy error, I hadn't noticed your were using sdx1. Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 Oh wow... sorry for that. So looking good now: root@Tower:~# sfdisk /dev/sda Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9C418D6E-79F2-4D4F-B0FF-8E2B17D3E4F7 Old situation: Device Start End Sectors Size Type /dev/sda1 64 5860533134 5860533071 2.7T Linux filesystem Type 'help' to get more information. >>> What do I need to input? Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 type 64 and press enter. Then type write and enter to apply changes. When done repost the output of: sfdisk /dev/sda Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 Do I need to input /dev/sda1 first? root@Tower:~# sfdisk /dev/sda Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9C418D6E-79F2-4D4F-B0FF-8E2B17D3E4F7 Old situation: Device Start End Sectors Size Type /dev/sda1 64 5860533134 5860533071 2.7T Linux filesystem Type 'help' to get more information. >>> 64 Created a new GPT disklabel (GUID: 2D06916A-72D7-4FFE-B87D-9984BE4C2BCB). Sector 64 already used. Failed to add partition: Numerical result out of range /dev/sda1: Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 It's been so long I don't remember exactly what should happen, but don't remember that error, let me do it again and I'll post later. Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 Ok, great thank you! /dev/sda1 doesn't work. Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 Looks like sfdisk can't start a GPT partition on sector 64, lets use parted instead, if the disk is still sda type: parted /dev/sda resizepart 1 100% When done repost the output of: sfdisk /dev/sda Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 Ok, how do I install parted? Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 This is how far i got: $ wget http://mirrors.slackware.com/slackware/slackware-current/slackware/l/parted-3.2-i586-2.txz $ installpkg parted-3.2-i586-2.txz $ parted /dev/sda resizepart 1 100% bash: /usr/sbin/parted: cannot execute binary file: Exec format error What am I doing wrong? Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 Install the unassigned devices plugin, I though it was part of unRAID but it comes with that. http://lime-technology.com/forum/index.php?topic=45807.0 Quote Link to comment
luksak Posted December 27, 2016 Author Share Posted December 27, 2016 Somhow the 1 parameter isn't accepted: parted /dev/sda resizepart 1 100% Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 1953504000 blocks) or continue with the current setting? parted: invalid token: 1 Fix/Ignore? Quote Link to comment
JorgeB Posted December 27, 2016 Share Posted December 27, 2016 Try to fixit by typing F, then type the parted command again to make sure the partition was resized. Quote Link to comment
luksak Posted December 28, 2016 Author Share Posted December 28, 2016 Ok, here is what happened: parted /dev/sda resizepart 1 100% Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 1953504000 blocks) or continue with the current setting? parted: invalid token: 1 Fix/Ignore? F Partition number? Partition number? 1 End? [3001GB]? Information: You may need to update /etc/fstab. Was Partition number 1 right? What should I do now? Quote Link to comment
JorgeB Posted December 28, 2016 Share Posted December 28, 2016 Run the same parted command again. Quote Link to comment
luksak Posted December 28, 2016 Author Share Posted December 28, 2016 Ok, this time it went through without any warnings: $ parted /dev/sda resizepart 1 100% Information: You may need to update /etc/fstab. Here is the output of sfdisk /dev/sda: $ sfdisk /dev/sda Welcome to sfdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9C418D6E-79F2-4D4F-B0FF-8E2B17D3E4F7 Old situation: Device Start End Sectors Size Type /dev/sda1 64 7814037134 7814037071 3.7T Linux filesystem Type 'help' to get more information. Should I run reiserfsck again? Quote Link to comment
JorgeB Posted December 28, 2016 Share Posted December 28, 2016 Not yet, now is the critical part, if it doesn't work all this work was for nothing, so good luck! resize_reiserfs /dev/sda1 Don't forget the 1 now. Quote Link to comment
luksak Posted December 28, 2016 Author Share Posted December 28, 2016 $ resize_reiserfs /dev/sda1 resize_reiserfs 3.6.24 resize_reiserfs: run reiserfsck --check first Running reiserfsck --check /dev/sda1 now. Quote Link to comment
luksak Posted December 28, 2016 Author Share Posted December 28, 2016 This was the output: $ reiserfsck --check /dev/sda1 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/sda1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Wed Dec 28 03:25:52 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/sda1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Aborted Doesn't look too good... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.