April 13, 201214 yr For the past months or so, I've been having a hard time with my server. I am new unraid owner, and I don't really know anything about using Linux code ect. I'm to the point where I am thinking of dumping unraid and go with WHS. So, I am going to give it a week to try to fix this and the other issues (slow transfer speeds and being able to download packages, but unable to install via unmenu) I notice this new line in my system log Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. What does it mean? My other question, can I just keep whatever data is on my data drive, reformat the parity drive, wipe out the flash drive, and re-start everything from scratch? Will this solve anything. syslog-2012-04-13.txt
April 13, 201214 yr Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. What does it mean? This is a reference to the built in read-only NTFS driver. Is there an NTFS format drive in the system? The syslog is only 10 minutes long and does not indicate any problems. Post the out put of "ifconfig" and "ethtool eth0".
April 13, 201214 yr Author Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. What does it mean? This is a reference to the built in read-only NTFS driver. Is there an NTFS format drive in the system? The syslog is only 10 minutes long and does not indicate any problems. Post the out put of "ifconfig" and "ethtool eth0". All my drives have been precleared prior to being put in the array. All the drive where NTFS prior to being precleared. NIC info (from ethtool) Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes NIC driver info (from ethtool -i) driver: r8169 version: 2.3LK-NAPI firmware-version: bus-info: 0000:02:00.0 Ethernet config info (from ifconfig) eth0 Link encap:Ethernet HWaddr 00:e0:4d:c6:d2:e0 inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1892 errors:0 dropped:0 overruns:0 frame:0 TX packets:2013 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:209373 (204.4 KiB) TX bytes:1380834 (1.3 MiB) Interrupt:26 Base address:0x4000
April 13, 201214 yr For the past months or so, I've been having a hard time with my server. I am new unraid owner, and I don't really know anything about using Linux code ect. I'm to the point where I am thinking of dumping unraid and go with WHS. So, I am going to give it a week to try to fix this and the other issues (slow transfer speeds and being able to download packages, but unable to install via unmenu) I notice this new line in my system log Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. What does it mean? My other question, can I just keep whatever data is on my data drive, reformat the parity drive, wipe out the flash drive, and re-start everything from scratch? Will this solve anything. The built-in ntfs driver is a read-only driver. You can use it to read an NTFS file-system, but not write to one. You must install ntfs-3g to be able to both read and write to an NTFS file system. Joe L.
April 13, 201214 yr Author For the past months or so, I've been having a hard time with my server. I am new unraid owner, and I don't really know anything about using Linux code ect. I'm to the point where I am thinking of dumping unraid and go with WHS. So, I am going to give it a week to try to fix this and the other issues (slow transfer speeds and being able to download packages, but unable to install via unmenu) I notice this new line in my system log Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. What does it mean? My other question, can I just keep whatever data is on my data drive, reformat the parity drive, wipe out the flash drive, and re-start everything from scratch? Will this solve anything. The built-in ntfs driver is a read-only driver. You can use it to read an NTFS file-system, but not write to one. You must install ntfs-3g to be able to both read and write to an NTFS file system. Joe L. Joe L., I saw that scrip in the package manager within unmenu, but I just wanted to make sure I needed it before I start installing more script in my server. I am currently using all of my 6 sata ports from my mobo, and I am planning on buying more hard drives (3tb hdds), but I also want to move to the unraid version 5.0b14. So, I just want to make sure everything is running correctly prior to making that move. Anyway, I will install that NTFS script so that issue can be resolved. Thanks you. PS. Do, I have to run another parity check to make sure the NTFS script worked? If not how do I check the script worked.
April 13, 201214 yr There is no reason the install an additional NTFS driver unless you plan to write to NTFS format drives in the system. A pre-cleared drive is no longer NTFS formatted.
April 13, 201214 yr Author There is no reason the install an additional NTFS driver unless you plan to write to NTFS format drives in the system. A pre-cleared drive is no longer NTFS formatted. That's what I though too, but for some reason or another that's what I am getting.
April 13, 201214 yr True, and an NTFS formatted drive would never be part of the parity protected array. neither NTFS driver has anything to do with parity. The kernel is just issuing a status message that the NTFS driver is in READ/ONLY mode. (The driver is so old and never had the ability to write files. Since ntfs-3g was developed there was never any incentive to go back and re-write the read-only driver, so nobody in the Linux world has made it able to write files.) The ntfs-3g driver is able to read and write NTFS formatted disks, but most people have no need for writing to NTFS disks. They are mostly interested in data migration TO unRAID, which only needs read capability of the NTFS file-system. The unMENU package is there for those who need to WRITE to NTFS formatted drives. Joe L
April 13, 201214 yr There is no reason the install an additional NTFS driver unless you plan to write to NTFS format drives in the system. A pre-cleared drive is no longer NTFS formatted. That's what I though too, but for some reason or another that's what I am getting. As stated this line in informational. However, I do not have this line in any of my syslogs, neither 4.7 or 5b14. Could there be an NTFS format drive in the system or some add-on causing this driver to load?
April 13, 201214 yr I get the line once in a while... http://lime-technology.com/forum/index.php?topic=13178.msg124911#msg124911
April 13, 201214 yr Author I get the line once in a while... http://lime-technology.com/forum/index.php?topic=13178.msg124911#msg124911 I ended up installing the ntfs-3g script, and I haven't seen that message again. Now, I've got other errors.
April 18, 201214 yr Author I'm still getting this Tower kernel: NTFS driver 2.1.29 [Flags: R/O MODULE] error. I'm not sure why even after installing the ntfs-3g script. Will this go away if I update to 5b14?
April 18, 201214 yr Author It's NOT an error. It is informational. Damn informational commercials! Thanks.
Archived
This topic is now archived and is closed to further replies.