tr0910

57K re-allocated sectors?? Just precleared a Seagate 3tb that had been in use for several years and was working fine. I ran mymain and discovered there were 57240 reallocated sectors. I quickly replaced this drive thinking it was dying, but a preclear doesn't note anything else wrong with it. I have never seen this level of reallocated sectors before. Is it safe to use? 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 57240 sectors had been re-allocated before the start of the preclear. 57240 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.

I'm not reporting a bug, but more wanting to start a debate about what should this plugin report in cases where the number of reallocated sectors is not zero and actually is increasing. We need Joe L and the other drive experts to weigh in... 1. Case where the number of reallocated sectors is zero before and zero after - no debate. Drive is good 2. Some reallocated sectors, but they are stable and not increasing. - Some debate, should the plugin report this?? 3. Some reallocated sectors and more are found during the preclear. - The drive is not healthy. Should it be used? Is it dying??

The wiki for converting drives had the rsync command as follows rsync -avPX /mnt/disk15 /mnt/disk5 When I run that I get a folder called disk15 on disk5 Isn't this the correct command? rsync -avPX /mnt/disk15/ /mnt/disk5/ I updated the wiki...

Rather than Preclear Successful, it should have told me that Preclear was successful, but your disk is starting to fail. The plugin reports ST3000DM001-9YN166_W1F0MED2 Preclear Successful ... Total time 24:27:20 ... Pre-Read time 7:06:20 (117 MB/s) ... Zeroing time 5:11:10 (160 MB/s) ... Post-Read time 12:08:51 (68 MB/s) But it doesn't note that the disk is beginning to fail (the number of reallocated sectors is not zero and increasing ) : 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 384 sectors had been re-allocated before the start of the preclear. 400 sectors are re-allocated at the end of the preclear, a change of 16 in the number of sectors re-allocated.

Even with the same file system it is possible. I had 2 rfs disks replicated daily with rsync for the last 2 years where the destination disk was smaller than the source even after a successful rsync. This started my exploration into Bitrot and bunker, as my files had no md5 hashes. We proved that it is possible to have the same contents with differing free space on rfs.

I know I tried that at first and it didn't work, but must have fat fingered it. I too can confirm it works.

I have observium installed, but the login is not working. On hub.docker.com it says Browse to http://your-host-ip:8668 and login with user and password observium But I don't get it to work. Is login supposed to be root / observium ?

Resurrect unmenu to install them?

Sorry, I didn't. Trying it again now I get preclear starting, but with the double prompt for "Yes" again. See below. root@SandBox:/boot# preclear_disk.sh -D /dev/sdo Pre-Clear unRAID Disk /dev/sdo ################################################################## 1.15 smartctl may not be able to run on /dev/sdo. however this should not affect the clearing of a disk. smartctl exit status = 4 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Seagate Product: ST4000DM000-1F21 Revision: R001 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Logical block size: 512 bytes Rotation Rate: 10000 rpm Logical Unit id: 0x0004d927010a4812 Serial number: W30036FJ Device type: disk Transport protocol: Fibre channel (FCP-2) Local Time is: Wed Jun 17 14:50:44 2015 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 30 C Drive Trip Temperature: 25 C Manufactured in week 30 of year 2002 Specified cycle count over device lifetime: 4278190080 Accumulated start-stop cycles: 256 Elements in grown defect list: 0 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 0 0 0 0 0 0.000 0 write: 0 0 0 0 0 0.000 0 Non-medium error count: 0 Device does not support Self Test logging$ Do you wish to continue? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes Disk /dev/sdo: 4000.8 GB, 4000787030016 bytes 64 heads, 32 sectors/track, 3815447 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdo1 1 4294967295 2147483647+ 0 Empty ######################################################################## invoked as ./preclear_disk.sh -D /dev/sdo ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'):

Neither do I. Try using -D option and see if it works without SMART. Running preclear_disk.sh -d /dev/sdo Give the same help screen as running with nothing at all.

I've never knew there was an areca option for preclear. I don't know what the areca,N/E means below... root@SandBox:/boot# preclear_disk.sh -d areca /dev/sdo Pre-Clear unRAID Disk /dev/sdo ################################################################## 1.15 smartctl may not be able to run on /dev/sdo with the -d areca option. however this should not affect the clearing of a disk. smartctl exit status = 1 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdo: Unknown device type 'areca' =======> VALID ARGUMENTS ARE: ata, scsi, sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbsunplus, marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, cciss,N, auto, test <======= Use smartctl -h to get a usage summary$ Do you wish to continue? (Answer Yes to continue. Capital 'Y', lower case 'es'):

Confirm, duplicate entry gone, but the 2.2tb issue is still there. Areca connected drives are not working with this plugin, they must be started from the command line. Because the Areca doesn't respond to smartctrl, the preclear script asks twice for you to press "Yes" before continuing the preclear. This different response confuses the plugin, and it appears to never start. Here is the first response at the command line. Pre-Clear unRAID Disk /dev/sdo ################################################################## 1.15 smartctl may not be able to run on /dev/sdo with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 2 smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$ Do you wish to continue? (Answer Yes to continue. Capital 'Y', lower case 'es'):

Here is more... root@SandBox:/boot# php -r "$(curl -skL http://bit.ly/1QXfVsq)" UNRAID DISKS: /dev/sde /dev/sdh /dev/sdn /dev/sdd /dev/sdl /dev/sdg /dev/sdf /dev/sdj /dev/sdk /dev/sda /dev/sdc /dev/sdi UNRAID CACHE: /dev/sdb Discarded: => /dev/disk/by-id/ata-SAMSUNG_HD203WI_S1UYJ1CZ415039 (/dev/sdk) Unassigned disk: /dev/disk/by-id/ata-ST4000DM000-1F2168_W30036FJ Discarded: => /dev/disk/by-id/ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ1999111 (/dev/sdl) Discarded: => /dev/disk/by-id/ata-WDC_WD30EZRX-00DC0B0_WD-WMC1T0416128 (/dev/sdn) Discarded: => /dev/disk/by-id/scsi-ARC1280V2_0000000475159536 (/dev/sde) Discarded: => /dev/disk/by-id/scsi-HD204UI_S2H7J1AZC09470 (/dev/sdd) Discarded: => /dev/disk/by-id/scsi-HD204UI_S2H7J1AZC09473 (/dev/sda) Discarded: => /dev/disk/by-id/scsi-SATA_SAMSUNG_HD203WIS1UYJ1CZ415039 (/dev/sdk) Unassigned disk: /dev/disk/by-id/scsi-SATA_ST4000DM000-1F2_W30036FJ Discarded: => /dev/disk/by-id/scsi-SATA_WDC_WD30EZRS-00_WD-WCAWZ1999111 (/dev/sdl) Discarded: => /dev/disk/by-id/scsi-SATA_WDC_WD30EZRX-00_WD-WMC1T0416128 (/dev/sdn) Discarded: => /dev/disk/by-id/scsi-ST3000DM001-9YN1_S1F01ZG4 (/dev/sdg) Discarded: => /dev/disk/by-id/scsi-ST3000DM001-9YN1_W1F115DE (/dev/sdj) Discarded: => /dev/disk/by-id/scsi-ST3000DM001-9YN1_W1F11605 (/dev/sdf) Discarded: => /dev/disk/by-id/scsi-ST4000DM000-1F21_S30030A6 (/dev/sdh) Discarded: => /dev/disk/by-id/scsi-ST33000651AS_9XK0P1JR (/dev/sdc) Discarded: => /dev/disk/by-id/scsi-WD20EARS-00MVWB0_WD-WMAZA3609021 (/dev/sdb) Discarded: => /dev/disk/by-id/scsi-WD30EZRX-00MMMB0_WD-WCAWZ2195094 (/dev/sdi) Discarded: => /dev/disk/by-id/usb-SanDisk_Cruzer_Fit_4C532000060115108162-0:0 (/dev/sdo) Array ( [0] => Array ( [device] => /dev/sdm [type] => ata [partitions] => Array ( [0] => Array ( [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ [device] => /dev/sdm1 [part] => 1 [label] => ST4000DM000 1F2168 W30036FJ [fstype] => [target] => [size] => 2199023255040 [used] => 0 [avail] => 2199023255040 [mountpoint] => /mnt/disks/ST4000DM000_1F2168_W30036FJ [owner] => user [automount] => [shared] => 1 [command] => [command_bg] => ) ) [temperature] => 37 [size] => 4000787030016 [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ ) [1] => Array ( [device] => /dev/sdm [type] => ata [partitions] => Array ( [0] => Array ( [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ [device] => /dev/sdm1 [part] => 1 [label] => ST4000DM000 1F2168 W30036FJ [fstype] => [target] => [size] => 2199023255040 [used] => 0 [avail] => 2199023255040 [mountpoint] => /mnt/disks/ST4000DM000_1F2168_W30036FJ [owner] => user [automount] => [shared] => 1 [command] => [command_bg] => ) ) [temperature] => 37 [size] => 4000787030016 [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ ) )

Here it is... root@SandBox:/boot# php -r "$(curl -skL http://bit.ly/1QXfVsq)" Array ( [0] => Array ( [device] => /dev/sdm [type] => ata [partitions] => Array ( [0] => Array ( [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ [device] => /dev/sdm1 [part] => 1 [label] => ST4000DM000 1F2168 W30036FJ [fstype] => [target] => [size] => 2199023255040 [used] => 0 [avail] => 2199023255040 [mountpoint] => /mnt/disks/ST4000DM000_1F2168_W30036FJ [owner] => user [automount] => [shared] => 1 [command] => [command_bg] => ) ) [temperature] => 37 [size] => 4000787030016 [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ ) [1] => Array ( [device] => /dev/sdm [type] => ata [partitions] => Array ( [0] => Array ( [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ [device] => /dev/sdm1 [part] => 1 [label] => ST4000DM000 1F2168 W30036FJ [fstype] => [target] => [size] => 2199023255040 [used] => 0 [avail] => 2199023255040 [mountpoint] => /mnt/disks/ST4000DM000_1F2168_W30036FJ [owner] => user [automount] => [shared] => 1 [command] => [command_bg] => ) ) [temperature] => 37 [size] => 4000787030016 [serial] => ST4000DM000-1F2168_W30036FJ [serial_short] => W30036FJ ) )

Here is the output... Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in Command line code on line 33

That is from the unassigned drives page. Both the preclear plugin and unassigned drives show the preclear process happening. But why are there 2 lines listed. Only 1 drive is being cleared and only 1 drive is unassigned. I hadn't even noticed the 2.2tb issue.

Like this...

Yes, at the beginning of the preclear. If it stood still, there's a unknown bug there. After much installing and deinstalling, it seems to be working, except for one thing. I now have 2 lines showing up for the disk that is being precleared. I installed the unassigned devices plugin, and it too has 2 lines showing up listing the preclearing drive. I haven't rebooted and installed 6final yet. Still on rc5. Want me to try anything?

I get a pop up that gets as far as the this but it seems it doesn't get the "Yes" input: Device Boot Start End Blocks Id System /dev/sdo1 1 4294967295 2147483647+ 0 Empty ######################################################################## invoked as /boot/config/plugins/preclear.disk/preclear_disk.sh -c 1 /dev/sdo ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): In fact if I invoke it from a terminal session in putty, it wants me to enter the "Yes" twice before it starts clearing.... Update: It was attached to my 24 port Areca controller, not the motherboard ATA ports. Once I hooked it to the motherboard, it seems to be working OK

OK, just updated successfully and all 4 files in the preclear.disk folder now have respectable sizes. I started a preclear. Now on the Settings->Preclear Disk screen I have one line for disk sdo and at the far right side, only a Starting.... followed by a big red X Is this expected status behavior for a running preclear?

Same results here when installing the plugin. 2 files are downloaded blank. wget -O /boot/config/plugins/preclear.disk/libevent-2.0.21-x86_64-1.txz http://mirrors.slackware.com/slackware/slackware64-14.1/slackware64/l/libevent-2.0.21-x86_64-1.txz wget them manually results in the same 0 byte file. Where should we get these files from?

I have several areca cards and I would like to see them better supported by unRaid. Temp display is the main lack today on v6 dashboard. I have to load the web interface of the areca cards to see temperatures. They provide me with a way to use my older smaller 2tb disks in a raid0 parity disk configuration. Showing temperatures where multiple disks are combined would be even more helpful.

Yes, you are right. It was so easy to reinstall them. All good again. Thanks for the tip.

How do I get unRaid to reconnect to my dockers? After a power bump, my cache drive was unmountable. See: http://lime-technology.com/forum/index.php?topic=39960.0 I was not able to get the cache disk mounted so I could , so clobbered the xfs log and did an xfs_repair -L /dev/sdb1. Now we are running again (6rc2), but docker is claiming that I have no docker containers installed. I beg to differ as my appdata folder is still intact with about 10 dockers in it and my docker.img file is also there. What is the way to recover from this error?

Has anybody tried it and owncloud to the point they can compare and contrast the two? What I see so far. OwnCloud supports more granular user based management. Tonido seems to be a simpler product, easier to set up and access remotely. but I'm sure there are many more differences.