I first tried resetting sdc using "GPT" and "ext3" settings. Chose ext3 just because the RAID volume is that for consistency, even though it doesn't matter once added to the array.
Log from Web GUI of resetting sdc:
- Code: Select all
NAS server in Setup Mode
(re-)Start the setup task : Reset internal disk(s)
Started on: 14 June 2017, 01:00:50
Ended at: 14 June 2017, 01:01:25
Setup task reset.sh is now running
Found disk: sdc(W1F086KE)
Delete the partiton table on sdc: OK
Create a new partiton gpt table on sdc:
=>Creating gpt partition table succeeded
Format partition sdc8 with file system ext3:
=>mke2fs 1.42.11 (09-Jul-2014)
Filesystem too small for a journal
Discarding device blocks: done
Creating filesystem with 1024 1k blocks and 128 inodes
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
=>Fail (set ext3 file system on sdc8 failed)
It also gave this pop-up window after failure:
https://drive.google.com/open?id=0B5x7lw1_KgjVMjkyVmZKcmVYZlEContents of file mentioned by "More detail in:"
- Code: Select all
root@HvyMtlNAS:/ # cat /etc/.setup.fs/setupjob.log
<b>Setup task reset.sh is now running</b><br>
Found disk: sdc(W1F086KE) <br>
Delete the partiton table on sdc: OK<br>
Create a new partiton gpt table on sdc: <br>
=>Creating gpt partition table succeeded<br>
Format partition sdc8 with file system ext3: <br>
=>mke2fs 1.42.11 (09-Jul-2014)
Filesystem too small for a journal
Discarding device blocks: done
Creating filesystem with 1024 1k blocks and 128 inodes
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
=><span style="color:red;"><b>Fail (set ext3 file system on sdc8 failed)</b></sp an><br>
<br><b>Setup task reset.sh is restarting</b><br>
Found disk: sdc(W1F086KE) <br>
Format partition sdc8 with file system ext3: <br>
=>mke2fs 1.42.11 (09-Jul-2014)
Filesystem too small for a journal
Discarding device blocks: done
Creating filesystem with 1024 1k blocks and 128 inodes
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
=><span style="color:red;"><b>Fail (set ext3 file system on sdc8 failed)</b></sp an><br>
root@HvyMtlNAS:/ #
So then I retried it using settings of "GPT" and "ext4" and it was successful. Log from Web GUI of resetting sdc:
- Code: Select all
Setup task reset.sh is now running
Found disk: sdc(W1F086KE)
Delete the partiton table on sdc: OK
Create a new partiton gpt table on sdc:
=>Creating gpt partition table succeeded
Format partition sdc8 with file system ext4:
=>mke2fs 1.42.11 (09-Jul-2014)
Creating filesystem with 732566129 4k blocks and 183148544 inodes
Filesystem UUID: f3ab0e89-a1e4-4df6-acab-3416a77eff71
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
=>Formatting sdc8 succeeded
Update partition type on sdc8: OK
Remove orphan shares: OK
Setup task reset.sh is ended
I'm not sure what about ext3 it didn't like, but I thought I'd gather all the info from it in case it would be helpful to you for development. Ext4 reset finished pop-up:
https://drive.google.com/open?id=0B5x7lw1_KgjVNmh6M2EyVGctRzAFor the ext4 setting this was the contents of file mentioned by "More detail in:"
- Code: Select all
root@HvyMtlNAS:/ # cat /etc/.setup.fs/setupjob.log
<b>Setup task reset.sh is now running</b><br>
Found disk: sdc(W1F086KE) <br>
Delete the partiton table on sdc: OK<br>
Create a new partiton gpt table on sdc: <br>
=>Creating gpt partition table succeeded<br>
Format partition sdc8 with file system ext4: <br>
=>mke2fs 1.42.11 (09-Jul-2014)
Creating filesystem with 732566129 4k blocks and 183148544 inodes
Filesystem UUID: f3ab0e89-a1e4-4df6-acab-3416a77eff71
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
=>Formatting sdc8 succeeded<br>
Update partition type on sdc8: OK<br>
Remove orphan shares: OK<br>
<b>Setup task reset.sh is ended</b><br>
root@HvyMtlNAS:/ #
After adding sdc it is showing recovery status in Disk Setup initially:
- Code: Select all
clean, degraded, recovering completed: 0.0%, estimated time: 3149.5min
And then a few minutes later it showed (slow) progress:
- Code: Select all
clean, degraded, recovering completed: 0.2%, estimated time: 3194.1min
Something I noticed in the changelog for 17.0 and again in the edit menu of the RAID array is ext4. Can I use the convert feature (obviously after the RAID is healthy again) to convert the format type from ext3 to ext4 WITHOUT losing data? Thought of this because of the benefits the changelog mentioned.