June 16, 201313 yr Copied from here: http://lime-technology.com/forum/index.php?topic=27936.msg247877#msg247877 FWIW... Partition format: MBR: 4K-aligned File sytem type: unknown All of my disks show this until I start the array... After the array is online, they show Partition format: MBR: 4K-aligned File sytem type: reiserfs the "unknown" description causes confusion. If it can be determined, it should not say "unknown" Two ways I am aware of are: root@Tower:/# file -s /dev/sdf1 /dev/sdf1: ReiserFS V3.6 block size 4096 (mounted or unclean) num blocks 488378638 r5 hash root@Tower:/# blkid /dev/sdf1 /dev/sdf1: UUID="f48885ea-1ec2-4e02-9a6c-9c569d589547" TYPE="reiserfs" Joe L.
June 16, 201313 yr By the way, this also happens in rc14. You need to stop the array and click on the disk ID under devices to see it.
June 16, 201313 yr This is apparently "normal" with v5 ==> when the array is Stopped, if you click on the drives individually they all show that status !! I wasn't aware of it until I gave it a try after it was noted in a question here.
June 16, 201313 yr Author This is apparently "normal" with v5 ==> when the array is Stopped, if you click on the drives individually they all show that status !! I wasn't aware of it until I gave it a try after it was noted in a question here. It may be "normal" but it is a source of confusion that could be eliminated. In the same way, if a disk is known to be part of the array (matches the serial number expected AND has been formatted in the past), and cannot be mounted, the wording "disk cannot be mounted" is FAR better than "unformatted". Joe L.
June 16, 201313 yr This is apparently "normal" with v5 ==> when the array is Stopped, if you click on the drives individually they all show that status !! I wasn't aware of it until I gave it a try after it was noted in a question here. It may be "normal" but it is a source of confusion that could be eliminated. In the same way, if a disk is known to be part of the array (matches the serial number expected AND has been formatted in the past), and cannot be mounted, the wording "disk cannot be mounted" is FAR better than "unformatted". Joe L. I completely agree Joe => I didn't mean to imply it was "good" ==> only that it's the way v5 currently "behaves" ... and in fact (based on other comments) it's apparently been that way for a while. Since it doesn't show on the Main screen -- you have to click on the drives individually to see it, it's not something we've noticed before.
June 16, 201313 yr ... and I CERTAINLY agree with your suggestion about using "cannot be mounted" instead of "unformatted" !!
June 16, 201313 yr Confirmed: Partition size: 1.953.514.552 KB (K=1024) Partition format: MBR: 4K-aligned File system type: unknown Only when you stop the array.
June 16, 201313 yr Confirmed. Array stopped. MD drive not enabled. Partition 1 size: 3907018532 KB (K=1024) Partition format: GPT: 4K-aligned File sytem type: unknown root@unRAID2:/# ls -l /dev/md1 /bin/ls: cannot access /dev/md1: No such file or directory root@unRAID2:/# /sbin/blkid /dev/sdd1 /dev/sdd1: UUID="9fbf3136-3c0f-4582-aeb1-4e8cf589e3aa" TYPE="reiserfs" I don't have "file" on my server Perhaps emhttp could say unmounted if the md drive is not active anymore. I'm not sure it should turn around and read the physical device right away, but it would be helpful.
June 16, 201313 yr In the same way, if a disk is known to be part of the array (matches the serial number expected AND has been formatted in the past), and cannot be mounted, the wording "disk cannot be mounted" is FAR better than "unformatted". Joe L. ... and I CERTAINLY agree with your suggestion about using "cannot be mounted" instead of "unformatted" !! Should this be a separate issue post?
June 16, 201313 yr Should this be a separate issue post?[/font] I don't think so. Joe mentioned it to emphasize that the "file system unknown" isn't the only confusing thing that's shown with regard to disk status. ... which is really what this thread's all about.
Archived
This topic is now archived and is closed to further replies.