Can Ubuntu Read Xfs From Nas Drive

impossible to get admission to nas disk (raid-ane xfs) with live Ubuntu cd: you have no rights...

  • Thread starter JustTrying
  • Get-go engagement
Feb 14, 2016
23
0
4,510
0
  • #1
Hi anybody,
establish a possible solution here to gain access to my one-time nas-drive (the nas obviously died) by using an Ubuntu live cd. Tried to do then, but when accessing the bulldoze I get the message: "Y'all have no rights to access this drive..."
(Using the nas I tin can however see the users, but non the folders anymore, then I wait the nas is gone.)
No repair utility or something of the kind.
Does anyone have i or more ideas how to get access to the drive over again and get to the data?
Difficult to get info nearly 'the day after....' the nas died.
Thanks for whatsoever help in advance.
Jul 12, 2013
218
0
x,860
55
  • #24
md127 has sdb3 open so you lot need to clear md127 first: sudo mdadm -S /dev/md127
Jul 12, 2013
218
0
ten,860
55
  • #ii
More info is needed to help you. How are y'all accessing the drive? Are you running every bit root? What kind of NAS device do you take? Post the output of... cat /proc/mdstat
Feb 14, 2016
23
0
4,510
0
  • #3
Cheers for your aid - will endeavor to detect more answers.
Here is what I can say now:
Dual Bay Nas-server. Brand unknown. The service doesn't exist anymore (unisupport.net in Denmark), the website is for sale.
Had 3 years of garantee, this is twelvemonth # 4.
The tool to access the nas is NetTool.exe.
The 2 drives have been formatted to XFS.
Set up via web-based direction.
Did use the nas nether a win2k pc and an old laptop. That w2k-motorcar died ii months ago, so I have built a new pc with legal win7.
The laptop was that old and having so many problems that I have bought me a simple new one, with win8 pre-installed.
Cannot meet anything on the raid-disks (continued via sata inside the new pc) with win7.
Following the suggestion somewhere here, I did create an iso disk with Ubuntu 14.04.3.
I am not (yet) a Linux experienced person, and so ran the live cd and tried to get to the files on the disk.
In Ubuntu I could see the disk and a few directories. Entering any of them gave me the info that I had no rights to become in.
Not sure if I ran Ubuntu every bit root. No thought if a simple user of a live cd has any admin rights or non.
The problem is I practise not know which program/system stopped me.
Was information technology Ubuntu? Was is the nas-drive?
Can I make a user with admin rights when running a live cd?
I exercise know the user proper noun and the password for the nas.
If Ubuntu allows me to, I tin create a user with the name of the administrator and give that user the password that I used for the nas.

I do take a backup of the nas from 1 week earlier the nas stopped working.
Created that backup with win7, via the network. Just copying all the stuf.
The basic problem is that my administration data (I am a small trader -an artist- and demand that administration for the tax submittance) from the moment betwixt the backup and the end of the nas-life is non on a backup. Could enter the data one time more, only then a bunch of assistants numbers will be gone. Non funny for taxation employees...

Will try to run the live cd once more shortly.
Suggestions on what to try by then are much appreciated. Will look for cat/ proc/mdstat, whatsoever that may be. I will find it.
Thank y'all in advance.

Feb 14, 2016
23
0
4,510
0
  • #4
Just an extra bit of info: the nas was a stand up-lone machine, stored far abroad from the pc'southward at home, for safety reasons.
Continued via network cable.
It was non a built-in nas, within my pc.
Excuse me for not mentioning.
Jul 12, 2013
218
0
ten,860
55
  • #5
Username root is the super user and gives y'all full permissions. See commands id and sudo. Notation best practice is to make drive images and execute recovery operations on the images to guard against mistakes. See command ddrescue. As the filesystem is XFS information technology's likely that Linux Software RAID was used by your NAS. Encounter control mdadm. When yous run command "cat /proc/mdstat" it shows the condition of your mdadm RAID. But without a basic understanding of Linux it volition exist a challenge for you to recover the Linux way. I advise you first try Windows recovery tools such every bit R-Studio or UFSexplorer which will be safer and easier for you to use.
Feb 14, 2016
23
0
four,510
0
  • #6
@ S Haran - Yes, understand what you are proverb. But I practise want to get for the linux way. Information technology will take a couple of days for me to get into this stuff. Already studied basic info. Not afraid of a command line, that's the way I started in 1985 :) Windows had to be invented at that fourth dimension I think. Norton Commander, lots of printer problems and that kind of stuf.

Like to install an extra drive (for 64bit o/s and for linux installation) and rebuild the nas; the nas-drives are out at present.
Are both drives of a raid-1 absolutely completely identic, or has one of the two some kind of database/fat/whatsoever?
I mean, does it brand a difference the manner I put both drives back into the nas? Both drives are identical and I haven't found any identification which i of them should exist placed in which slot. Well, may equally well try and see what happens.
Effort to create an iso of both drives; sounds a good thought.
You will hear from me in a few days; after the weekend I hope.
Enjoy life.

Feb fourteen, 2016
23
0
4,510
0
  • #vii
Still busy trying to have Ubuntu do what I similar it to do.
Tin can even so access the nas via http://ip-address.
Seems to exist a chance to make a backup, but non clear yet how to deal with that in Ubuntu - having problems with user rights.
Will exist back - cheers for your patience.
Feb 14, 2016
23
0
4,510
0
  • #8
Back once again. Studying the human pages peculiarly for the commands mentioned here.
It is a compassion I have non been able to find more info (yet) about dealing with a harddrive that comes out of an external nas. Many time I read near files on the local deejay where ubuntu resides. These files practise non exist in my instance, which makes understanding a bit confusing.
result for the question before:

joes@film16-linux:~$ sudo cat /proc/mdstat
[sudo] password for joes:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sda3[0](Southward)
976486848 blocks

Working on creating a backup. Fear to accept written anything to disk, so studying many man pages. What a pleasance to get that much basic info. Not easy to abound in, just not impossible either.

Double Commander shows the drive with 'md127' and states 'disk is not available'.
Information technology shows a partition as sda2 after the md127.
In sda2 there is a raidconf file stating:

[RAID]
raid_enable = ane
raid_mode = i
disk_num = two
disk1 = "/dev/sda"
disk2 = "/dev/sdb"
disk3 = ""
disk4 = ""
fstype = 0
raid_vendor = ""

Think this partitioning is on the nas-deejay. See if I can get more info.

joes@film16-linux:~$ sudo mdadm --examine --scan /dev/sda1 /dev/sda2 /dev/sda3

Array /dev/md0 UUID=1120c154:ee458961:c72e49a8:c467befb

joes@film16-linux:~$ sudo fdisk -l

Disk /dev/sda: yard.ii GB, 1000204886016 bytes
255 heads, 63 sectors/rail, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/concrete): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot First End Blocks Id System
/dev/sda1 63 273104 136521 82 Linux swap / Solaris
/dev/sda2 273105 546209 136552+ 83 Linux
/dev/sda3 546210 1953520064 976486927+ 83 Linux

Deejay /dev/sdb: 2000.four GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, full 3907029168 sectors
Units = sectors of i * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x63a924e1

Device Kicking Start End Blocks Id System
/dev/sdb1 63 273104 136521 82 Linux swap / Solaris
/dev/sdb2 273105 546209 136552+ 83 Linux
/dev/sdb3 546210 3907024064 1953238927+ 83 Linux

Deejay /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/runway, 30401 cylinders, total 488397168 sectors
Units = sectors of i * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xdc4da274

Device Boot Start Finish Blocks Id System
/dev/sdc1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sdc2 206848 152115051 75954102 83 Linux

Disk /dev/sdd: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/rail, 7783 cylinders, full 125045424 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: 0xffffffff

Device Boot Beginning Cease Blocks Id System
/dev/sdd1 * 63 125033894 62516916 7 HPFS/NTFS/exFAT

Go on searching and deriving extra info.
Tips speeding the search are welcome.

Jul 12, 2013
218
0
x,860
55
  • #9
You've made some progress. Now lets come across the RAID meta-information on sda3. Post the output of: mdadm -E /dev/sda3
Feb 14, 2016
23
0
4,510
0
  • #ten
joes@film16-linux:~$ mdadm -E /dev/sda3
mdadm: cannot open /dev/sda3: No such file or directory
Jul 12, 2013
218
0
10,860
55
Feb 14, 2016
23
0
four,510
0
  • #12
Cheers. Commencement some other one, don know if that is of any use.

joes@film16-linux:~$ sudo mdadm --examine /dev/sda
mdadm: /dev/sda is not attached to Intel(R) RAID controller.
mdadm: /dev/sda is not attached to Intel(R) RAID controller.
/dev/sda:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.0.00
Orig Family unit : 246f9a7e
Family : 246f9a7e
Generation : 000002cd
Attributes : All supported
UUID : 3270173f:054aff94:06bb56fc:89c2348e
Checksum : 8b25fdf6 correct
MPB Sectors : 1
Disks : 2
RAID Devices : ane

Disk00 Serial : LB46Y49P5W82571M
State : active
Id : 00010000
Usable Size : 125040904 (59.62 GiB 64.02 GB)

[Volume0]:
UUID : 566c593d:e10cd185:0937f7d8:edac600b
RAID Level : 0
Members : 2
Slots : [UU]
Failed disk : one
This Slot : 0
Array Size : 250081280 (119.25 GiB 128.04 GB)
Per Dev Size : 125040904 (59.62 GiB 64.02 GB)
Sector Outset : 0
Num Stripes : 488440
Chunk Size : 128 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Muddied State : make clean

Disk01 Series : 307YEA2M66XEWM6A
State : agile
Id : 00040000
Usable Size : 125040904 (59.62 GiB 64.02 GB)

-----------------
Tried that ane too - no luck.
joes@film16-linux:~$ sudo mdadm -Due east /dev/sda3
mdadm: cannot open /dev/sda3: No such file or directory

Jul 12, 2013
218
0
ten,860
55
  • #13
Your /proc/mdstat says that sda3 is a fellow member of md127. Where did it become?

In whatsoever case see if y'all can find your data with: sudo tetdisk /dev/sda

Feb fourteen, 2016
23
0
4,510
0
  • #xiv
Some more info:
joes@film16-linux:~$ sudo blkid
[sudo] password for joes:
/dev/sda1: LABEL="SSD-60gyg" UUID="6E1CE86D1CE8322F" Blazon="ntfs"
/dev/sdb1: TYPE="swap"
/dev/sdb2: UUID="98f150d5-dfce-4572-8edf-aa830e9ad62d" TYPE="xfs"
/dev/sdb3: UUID="1120c154-ee45-8961-c72e-49a8c467befb" TYPE="linux_raid_member"
/dev/sdc1: Blazon="swap"
/dev/sdc2: UUID="7f51d39c-017c-4ac7-b36c-f101aef20dc9" TYPE="xfs"
/dev/sdc3: UUID="d95747d3-fd97-4840-aff6-40356a926d0d" Blazon="xfs"
/dev/sdd1: LABEL="Door systeem gereserveerd" UUID="A03CE83C3CE80EDA" TYPE="ntfs"
/dev/sdd2: UUID="5a5d8c3a-5039-45da-be93-9719a310a648" Blazon="ext3"

remark: the /dev/sda is a rather pocket-size ssd disk that I use for swapfiles to speed things up - not office of the array deejay.

dorsum to your communication...
searching for files I did get an mistake, having the choice between quit and written report, I chose for report and the program hangs.
Will showtime again. Is there a kind of log at the end?

Feb xiv, 2016
23
0
4,510
0
  • #15
testdisk:
>Disk /dev/sda - 64 GB / 59 Gib - OCZ-VERTEX v1.10
CHS 7783 255 63 - sector size=512
>[keep] [quit]
<p>
>[Intel] Intel/PC sectionalisation (has been detected)
<enter>
[ analyse ]
disk /dev/sda - 64 GB / 59 GiB - CHS 7783 255 63
current partition structure:
partitioning starting time end size in sectors
1 * HPFS - NTFS 0 i 1 7782 254 63 125033832 [SSD-60gyg]
> [ Quick Search ] [ Backup ]
<quick search> try to locate partition
structure: ok
{ quit ] [ deeper search ] [ write ]

Do not want to write partition structure to deejay, since I do not know to which disk that will be; so did quit/go back to the menu for the moment.

[ Advanced ] Filesystem Utils
Not certain which one to choose. Listing looks interesting, merely writes copies to somewhere. No idea if that is rubber for the moment.

Jul 12, 2013
218
0
ten,860
55
  • #16
So information technology looks like sdb3 is now your RAID sectionalization. Post: sudo mdadm -E /dev/sdb3

Y'all might want to experiment with testdisk to recover a spare drive to become an idea how information technology operates.

February 14, 2016
23
0
four,510
0
  • #17
Did a new mdstat:
joes@film16-linux:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdb3[0](S)
976486848 blocks

medico 127 is now an inactive sdb3 instead of sdba
the number of blocks is the same as in the first mdsat: 976486848 blocks
Perhaps had a hickup...
But this shows that sda is not the one, as I already thought.
Back to sdb...

Feb 14, 2016
23
0
4,510
0
  • #eighteen
joes@film16-linux:~$ sudo mdadm -E /dev/sdb3
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.03
UUID : 1120c154:ee458961:c72e49a8:c467befb
Cosmos Time : Thu Jan i 01:05:46 1970
Raid Level : raid1
Used Dev Size : 976486848 (931.25 GiB 999.92 GB)
Assortment Size : 976486848 (931.25 GiB 999.92 GB)
Raid Devices : 2
Total Devices : ii
Preferred Modest : 0

Update Time : Monday February 22 21:28:17 2016
State : clean
Active Devices : ii
Working Devices : ii
Failed Devices : 0
Spare Devices : 0
Checksum : c527268a - correct
Events : 126

Number Major Minor RaidDevice State
this 0 8 19 0 active sync /dev/sdb3

0 0 8 nineteen 0 active sync /dev/sdb3
1 1 viii 3 1 active sync

February 14, 2016
23
0
iv,510
0
  • #19
testdisk sdb:

Partition Start End Size in sectors
> 1 P Linux Bandy 0 i 1 16 254 63 273042
ii P Linux 17 0 ane 33 254 63 273105
iii P Linux 34 0 1 121600 254 63 1952973855

Looks better...

Feb 14, 2016
23
0
iv,510
0
  • #twenty
trying to list the files on the tertiary partition I get the error:

Support for this filesystem hasn't been enable during compilation.

It looks like testdisk is not (yet) set up for reading xfs ?

Jul 12, 2013
218
0
10,860
55
  • #21
That looks better. And then now you lot could try: mdadm --assemble --force /dev/md0 /dev/sdb3

And if all goes well you should be able to mountain /dev/md0 and see your data.

Only I would look at it showtime with: testdisk /dev/sdb3

Feb 14, 2016
23
0
4,510
0
  • #22
joes@film16-linux:~$ testdisk /dev/sdb3
TestDisk six.fourteen, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Unable to open up file or device /dev/sdb3

Sad...

Feb xiv, 2016
23
0
4,510
0
  • #23
joes@film16-linux:~$ sudo mdadm --get together --force /dev/md0 /dev/sdb3
mdadm: /dev/sdb3 is busy - skipping
Jul 12, 2013
218
0
10,860
55
  • #24
md127 has sdb3 open then you lot need to clear md127 first: sudo mdadm -S /dev/md127
Feb fourteen, 2016
23
0
4,510
0
  • #25
joes@film16-linux:~$ sudo mdadm -S /dev/md127
mdadm: stopped /dev/md127
Thread starter Like threads Forum Replies Date
Decaff Storage 4
YTheRolls Storage 2
E Storage 14
Eggz Storage two
HoveringUFO Storage 16
matrix303 Storage 3
derkevevin Storage v
P Storage 5
O Storage one
mrmike16 Storage vi
  • Advertizing
  • Cookies Policies
  • Privacy
  • Term & Atmospheric condition
  • Topics

grasssamissing1973.blogspot.com

Source: https://forums.tomshardware.com/threads/impossible-to-get-access-to-nas-disk-raid-1-xfs-with-live-ubuntu-cd-you-have-no-rights.2601323/

0 Response to "Can Ubuntu Read Xfs From Nas Drive"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel