P_K

hi all, I'm using unraid for long time but last 2-3 months I got a very annoying issue. I have dockers with couchpotato and sickrage which use deluge to download Movies/TV Series to a disk that is not in the array (managed by unassigned devices plugin). After either couchpotato or sickrage detects the download is complete it then copies the downloaded file to the cache disk (2 x 500 Gb SSD's (btrfs)). Overnight, the mover then moves those files to a disk in the array. This all worked fine for years but since 2-3 months some of the files are not copied completely. As an example, the movie Lady Bird was just downloaded on the disk out of the array. It's size is 7,04GB : Couchpotato copied it : But after the copy size is much smaller, only 1,61 GB : Couchpotato logs don't show any issue. Also, same happens with some copies from SickRage so I don't think it's an application issue. Unraid logs also don't show anything at the time of the copy (12:45) (at 12:18 I restarted deluge docker. 12:47 I opened a console session from GUI). Full unraid log : tower-syslog-20180317-1337.zip I'm quite honestly lost with this. First I expected the Mover but as can be seen above the issue happens already before moving. Is there any way I can check further what can cause this?

I'm moving my disks from ReiserFS to XFS after upgrading to 6.4. I follow the procedure from here : http://lime-technology.com/wiki/index.php/File_System_Conversion when copying disk3 to disk9, the rsync stopped after 10 hours more or less (earlier then I expected) : sent 1,270,465,325,294 bytes received 705,847 bytes 33,832,630.68 bytes/sec total size is 1,270,152,418,034 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] I don't have all the output rsync produced before that so cannot 'see previous errors'. My syslog shows this : Jan 22 08:10:22 Tower kernel: REISERFS warning (device md3): jdm-20001 reiserfs_xattr_get: Invalid magic for xattr (user.org.netatalk.supports-eas.bCcdQh) associated with [2 2112 0x0 SD] The strange thing however is that disk3 has 1.95Tb on it while disk9 now only has 1.27Tb. Seems that big part is not copied... Should I start over and maybe use the --log-file=/path/to/log option on the rsync this time to see if I get errors during the copy? Any other advise ?

In this post, it was said that 6.4 Mover would be generalized to move contents of any device to any other device or device set. Is that indeed the case in 6.4 ? Can the mover now be used to migrate disks from ReisterFS to XFS ?

Yes, I do indeed. See attachment.

I restarted the server as the load in top went up to 50. The diagnostics files are taken after the reload (before reload I couldn't access the gui to take them). Hopefully they are still useful. tower-diagnostics-20170121-2053.zip

cachedirs is installed but I turned it off long time ago as I had some issues with it. This is an i5 processor with 16Gb of memory.

This morning I got a notification (from PlexPy) that my Plex server is down. I tried to open the unraid webpage to check but it doesn't open. I can ssh into the server and can see in top that shfs uses 100% cpu. Any ideas to bring my server back to normal? unraid 6.2.4 with several dockers.

A while ago I tried to preclear 2 disks. One worked and something went wrong for the other so I had to start preclear again (don't remember the exact details though). I noticed now (several weeks later) in the logs the following after a startup : Dec 9 10:04:46 Tower preclear.disk: Resuming preclear of disk 'sdm' sdm was the disk that had issues with the preclear before but 'sdm' doesn't exist anymore now (there is no disk labeled sdm anymore). That disk is now sdk and is part of the cache pool. Seems preclear still thinks it has to do something. Is it possible/needed to stop this?

That worked, thanks a lot. Got indeed rid of the errors now that my UD disk is not mounted on /mnt/user anymore.

Yes, that's what I thought indeed (that it must get out of /mnt/user). I'm not sure however how to 'remove it, delete it from the list'... I had the drive unmounted but the only thing I can do then is to click the red X next to the partition. If I hover over that it says 'delete partition'. I'm afraid I'm going to lose the data on that disk if I do so. I don't see another option to remove that disk from UD.

I was already on 2016.12.04 for Unassigned Devices. I stopped my array which unmounted that disk and started it again : same issue.

Picking this back up as I still have the errors. Didn't look into them much as all seems to be working. I didn't remove the Unassigned Devices. I think however I know what the issue is. The mount point for a disk I added in Unassigned Devices is /mnt/user/Torrents_3Tb. I read that this is wrong and it should be /mnt/disks/... Correct ? My 'Torrents_3Tb' is showing up as a user share under the Share tab of unraid. I guess that's where the errors come from. (see attached screenshots). Question : is there an easy way to change that mount point without deleting all the data on that partition ?

Thanks! Adding iommu=pt to the append line of my syslinux.cnf file fixed it.

Hi all, unRAID : 6.1.9 MB : ASUSTeK COMPUTER INC. - P8B75-M LE Controller : startech.com 4 port PCIe SATA III 6Gbps Raid controller card with heatsink Added that 4 port Sata card to my unRAID and connected 2 Samsung EVO 850 500Gb SSD's to it. During boot there are errors and the 2 SSD's don't show up (cannot add them). I see following in the logs : Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata18: limiting SATA link speed to 1.5 Gbps Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13: limiting SATA link speed to 3.0 Gbps Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: limiting SATA link speed to 3.0 Gbps Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: reset failed, giving up When I move one of the SSD's to another controller then it shows up. If I move a drive that was on another controller before to the new one, that drive doesn't show up anymore. So it seem the controller has an issue. Anybody can assist on this? Logs attached. tower-syslog-20161018-2127.zip

anybody an idea about this? Would be appreciated. I upgraded to 6.1.7 in the meantime but errors keep coming.

unRaid 6.1.6 several dockers and plugins Recently (I think since I added a disk with the 'unassigned devices' plugin, I'm getting following every minute in the log : Jan 14 11:33:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available Jan 14 11:33:01 Tower emhttp: shareColor.7 not found Jan 14 11:34:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available Jan 14 11:34:01 Tower emhttp: shareColor.7 not found Jan 14 11:35:01 Tower emhttp: get_filesystem_status: getxattr: /mnt/user/Torrents_3Tb No data available Jan 14 11:35:01 Tower emhttp: shareColor.7 not found Everything _seems_ to be working fine but would like to know what this is. I restarted my server and attach a log from after restart. I stopped all dockers between 06:56 and 07:00 but the messages kept on coming in the log. tower-syslog-20160114-1149-1.zip

I'm new to this plugin. Trying to use it on my 6.1.4 unRaid to add a disk that I got from a friend (it has content and he claims it was formatted as NTFS). The disk shows up in Unassigned Devices but there is no Mount button : https://www.dropbox.com/s/uilwyrsc1r2dux5/Unassigned%20Devices.png?dl=0 fdisk -l for this disk gives this : Disk /dev/sdc: 4000.8 GB, 4000787030016 bytes 256 heads, 63 sectors/track, 484501 cylinders, total 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 Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. Any idea how to mount this disk?

Seems to run fine on my 6.1.2 Very useful plugin! Thanks!

unraid 5.0-rc11 (was going to upgrade to 5.0 but found some errors I first want to fix before upgrading) Got many errors in the smart report of my parity drive last week so I swapped it for a new one. Parity was build again and a (non correcting) parity check done. It found some errors. I did another parity check and had the errors corrected. Then I did another (non correcting) check : this time no errors. But now, (1 day later), I get following in my syslog when I try to browse in finder through some folders on my server : Sep 1 20:30:16 Tower shfs/user: shfs_write: write: (5) Input/output error Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/VMware/Temporary Items/.AppleDouble/.Parent (30) Read-only file system5 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_3 Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/VMware/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower kernel: REISERFS error (device md4): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 100302848 is corrupted: first bit must be 1 0 S 0 0.0 0:00.00 scsi_eh_4 Sep 1 20:30:16 Tower kernel: REISERFS (device md4): Remounting filesystem read-only Sep 1 20:30:16 Tower kernel: REISERFS warning (device md4): clm-6006 reiserfs_dirty_inode: writing inode 1726 on readonly FS Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Software/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Pictures/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/NeedsToBeSorted/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Music/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Movies/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Books and Magazines/.AppleDesktop/.volinfo (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/Network Trash Folder/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/Temporary Items/.AppleDouble/.Parent (30) Read-only file system Sep 1 20:30:16 Tower shfs/user: shfs_open: open: /mnt/disk4/Backup/.AppleDesktop/.volinfo (30) Read-only file system Found this page : http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems and ran a check : reiserfsck --check /dev/md4 Output : root@Tower:~# reiserfsck --check /dev/md4 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md4 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 Sun Sep 1 20:45:02 2013 ########### Replaying journal: Trans replayed: mountid 155, transid 11186, desc 3991, len 1, commit 3993, next trans offset 3976 Trans replayed: mountid 155, transid 11187, desc 3994, len 1, commit 3996, next trans offset 3979 Trans replayed: mountid 155, transid 11188, desc 3997, len 1, commit 3999, next trans offset 3982 Trans replayed: mountid 155, transid 11189, desc 4000, len 9, commit 4010, next trans offset 3993 Trans replayed: mountid 155, transid 11190, desc 4011, len 1, commit 4013, next trans offset 3996 Trans replayed: mountid 155, transid 11191, desc 4014, len 8, commit 4023, next trans offset 4006 Trans replayed: mountid 155, transid 11192, desc 4024, len 8, commit 4033, next trans offset 4016 Trans replayed: mountid 155, transid 11193, desc 4034, len 9, commit 4044, next trans offset 4027 Replaying journal: Done. Reiserfs journal '/dev/md4' in blocks [18..8211]: 8 transactions replayed Checking internal tree.. \/ 1 (of 4|/ 80 (of 170\/ 61 (of 156|bad_path: The left delimiting key [32 33 0x57001 IND (1)] of the node (100302849) must be equal to the first element's key [15950 15964 0x4c5fe001 IND (1)] within the node. / 62 (of 156/bad_path: The left delimiting key [32 33 0x44b001 IND (1)] of the node (100302850) must be equal to the first element's key [15950 15964 0x4ea22001 IND (1)] within the node. / 63 (of 156-bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (173) to the block (100301865), which is in tree already bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (174) to the block (100301862), which is in tree already bad_indirect_item: block 100302851: The item (15950 15964 0x4ee26001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (221) to the block (100301849), which is in tree already ... bad_indirect_item: block 102191267: The item (85 86 0x1fdecd001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (202) to the block (100302798), which is in tree already bad_indirect_item: block 102191267: The item (85 86 0x1fdecd001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (203) to the block (100302799), which is in tree already finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 4 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sun Sep 1 20:54:30 2013 ########### root@Tower:~# I read that this --rebuild-tree is last resort only. Can I run it or should I do something else first? syslog.txt

System log snippets are not useful. Another thread with syslogs with these symlink errors is http://lime-technology.com/forum/index.php?topic=25558.0. Unfortunately, it's clouded with other issues, but check the last syslog. Lots of addons to complicate this, and one of them may be causing it. Thanks for the helpful response. I'm not running any plugins, but I'll take a look through for "symlink error" in the forum. Wasn't sure how to even describe this error before. I have never seen messages like that before. As mentioned earlier, I can not help you without the full system log. I had the same messages 2-3 weeks ago when I upgraded to rc10 from rc8a. The messages kept appearing even after reboot. I searched the forums back then and found this : http://lime-technology.com/forum/index.php?topic=24622.msg220139#msg220139 I decided to try without plugins first before asking for help on the forums so I ran with a stock go file and no plugins enabled for 24 hours. Didn't see the messages anymore. I then enabled Simplefeatures. 24 hours running : no messages. Enabled Plex and tried for 24 hours : nothing. Last plugin to enable again was Plex updater : even with that one in (now running all plugins again) I didn't see the messages anymore. Unfortunately, I didn't save a syslog when they were appearing... So the 'issue' fixed itself for me...

I've been reading a bit in this topic and found the following : http://lime-technology.com/forum/index.php?topic=4068.msg48756#msg48756 "The current "normalized" read error rate is 108, prior to the preclear, it was 117. The worst ever measured over the lifetime of the drive was "99" The failure threshold is "006" If the normalized read error rate goes BELOW "006" then the drive is considered to be failing. All drives have internal read errors. They are all designed to re-read on an error. As long as the normalized error rate is above the threshold, you are fine. Nobody except the manufacturer knows how to interpret the "raw" values in the right-most column (and they don't tell anybody)" So in case of my drive (post above) it would be : current normalized read error rate : 200 before : 200 Worst value ever : 200 Threshold : 051 Disk is perfectly fine at this moment. I should only worry if the current normalized value goes below 051. Raw value of 2 : just ignore it as we don't know what it means (only WD knows). Is this is a correct understanding?

Want to use a new 3Tb drive as my new Parity drive. Did 4 cycles of preclear on it. It seems ok except for the Raw_Read_Error_Rate which is at 2 while it was 0 at the start of preclear. Is this a concern? start : Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Vendor Specific SMART Attributes with Thresholds: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 44 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 194 Temperature_Celsius 0x0022 125 121 000 Old_age Always - 25 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 end : Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ============================================================================ Jan 25 06:50:31 Tower preclear_disk-diff[8717]: == Jan 25 06:50:31 Tower preclear_disk-diff[8717]: == S.M.A.R.T Final Report for /dev/sdi Jan 25 06:50:31 Tower preclear_disk-diff[8717]: == Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Disk: /dev/sdi Jan 25 06:50:31 Tower preclear_disk-diff[8717]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: === START OF INFORMATION SECTION === Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Device Model: WDC WD30EFRX-68AX9N0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Serial Number: WD-WMC1T0071253 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Firmware Version: 80.00A80 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: User Capacity: 3,000,592,982,016 bytes Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Device is: Not in smartctl database [for details use: -P showall] Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ATA Version is: 9 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ATA Standard is: Exact ATA specification draft version not indicated Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Local Time is: Fri Jan 25 06:50:30 2013 CET Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART support is: Available - device has SMART capability. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART support is: Enabled Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: === START OF READ SMART DATA SECTION === Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART overall-health self-assessment test result: PASSED Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: General SMART Values: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Offline data collection status: (0x00)^IOffline data collection activity Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^Iwas never started. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Self-test execution status: ( 0)^IThe previous self-test routine completed Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^Iwithout error or no self-test has ever Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^Ibeen run. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Total time to complete Offline Jan 25 06:50:31 Tower preclear_disk-diff[8717]: data collection: ^I^I (41640) seconds. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Offline data collection Jan 25 06:50:31 Tower preclear_disk-diff[8717]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^IAuto Offline data collection on/off support. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISuspend Offline collection upon new Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^Icommand. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^IOffline surface scan supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISelf-test supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^IConveyance Self-test supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISelective Self-test supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART capabilities: (0x0003)^ISaves SMART data before entering Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^Ipower-saving mode. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISupports SMART auto save timer. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Error logging capability: (0x01)^IError logging supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^IGeneral Purpose Logging supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Short self-test routine Jan 25 06:50:31 Tower preclear_disk-diff[8717]: recommended polling time: ^I ( 2) minutes. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Extended self-test routine Jan 25 06:50:31 Tower preclear_disk-diff[8717]: recommended polling time: ^I ( 255) minutes. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Conveyance self-test routine Jan 25 06:50:31 Tower preclear_disk-diff[8717]: recommended polling time: ^I ( 5) minutes. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SCT capabilities: ^I (0x70bd)^ISCT Status supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISCT Error Recovery Control supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISCT Feature Control supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ^I^I^I^I^ISCT Data Table supported. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART Attributes Data Structure revision number: 16 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Vendor Specific SMART Attributes with Thresholds: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 150 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 194 Temperature_Celsius 0x0022 123 121 000 Old_age Always - 27 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART Error Log Version: 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: No Errors Logged Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART Self-test log structure revision number 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SMART Selective self-test log data structure revision number 1 Jan 25 06:50:31 Tower preclear_disk-diff[8717]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 1 0 0 Not_testing Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 2 0 0 Not_testing Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 3 0 0 Not_testing Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 4 0 0 Not_testing Jan 25 06:50:31 Tower preclear_disk-diff[8717]: 5 0 0 Not_testing Jan 25 06:50:31 Tower preclear_disk-diff[8717]: Selective self-test flags (0x0): Jan 25 06:50:31 Tower preclear_disk-diff[8717]: After scanning selected spans, do NOT read-scan remainder of disk. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jan 25 06:50:31 Tower preclear_disk-diff[8717]: == Jan 25 06:50:31 Tower preclear_disk-diff[8717]: ============================================================================ Jan 25 06:50:31 Tower preclear_disk-diff[8717]:

What you just described is basically the "Stable" and "Beta" model just with different names. But worse, he would still need a beta version for both the bugifxes in Stable as well as while testing the new features in "F" (aka beta .. .so a beta to a beta which is [drum roll] "Alpha") That just sounds like a recipie for pain and confusion. This is not the same as the current stable/beta model. In the current 'stable' (4.x) new features are introduced all the time, example : Changes from 4.7-beta1 to 4.7 ----------------------------- No changes (except version string). Changes from 4.6 to 4.7-beta1 ----------------------------- Feature: Advanced Format drive support - partition 1 may now be aligned on 4K boundry (sector 64) The big difference with the current model is that in the stable release NO new features are introduced, no new hardware is supported, no newer kernel version is introduced, no never version of samba, ... Another difference is also that when working on the features release, bugs are still being fixed in the stable release (the big complaint of most people was that 5 is beta and 4.7 contains some critical bugs). About needing a beta for bugfixes, I don't see why that is needed, not in stable, not in features.

My suggestion : Release a final 5.0 now. Make it more stable by ONLY adding bugfixes to it : 5.1, 5.2, 5.3, ... NO new features or new hardware, ONLY bugfixes!!! Make a separate 5.0F version (F from Features) with new features and support for new hardware (that MB with slow write speads would not be supported in 5.0). Those who want, can run 5.xF on their server to test the new features. While working on 5.xF, don't neglect to add bugfixes to 5.x At a certain point in time. 5.x will be quite stable and 5.xF will have several new features/hardware that should have been tested a lot. At that moment, turn 5.xF into 6.0 and start the cycle again. In 6.x the new features introduced in 5.xF will again become more and more stable. People wanting a stable release go for 5.x and can move to 6.x once they feel 6.x is stable enough (starting from 6.4/6.5/...). People who want some new features (or need them due to hardware support) have to go with 5.xF, 6.xF, ...

2 servers with Realtek nics upgraded successfully : Jan 12 14:51:57 Tower kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 14:51:57 Tower kernel: r8168 0000:03:00.0: irq 42 for MSI/MSI-X Jan 12 14:51:57 Tower kernel: eth%%d: RTL8168F/8111F at 0xf845e000, 30:85:a9:40:44:e0, IRQ 42 Jan 12 14:51:57 Tower kernel: eth0: Identified chip type is 'RTL8168F/8111F'. Jan 12 14:51:57 Tower kernel: r8168 Copyright (C) 2012 Realtek NIC software team Jan 12 13:01:35 Tower2 kernel: r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded Jan 12 13:01:35 Tower2 kernel: r8168 0000:03:00.0: irq 45 for MSI/MSI-X Jan 12 13:01:35 Tower2 kernel: eth%%d: RTL8168E/8111E at 0xf8506000, bc:ae:c5:c2:cc:e4, IRQ 45 Jan 12 13:01:35 Tower2 kernel: eth0: Identified chip type is 'RTL8168E/8111E'. Jan 12 13:01:35 Tower2 kernel: r8168 Copyright (C) 2012 Realtek NIC software team 'New Permissions' still running on one of them.