Advertising
- Miscellany
- Friday, September 25th, 2015 at 11:12:51pm UTC
- [ 2907.027256] SGI XFS with ACLs, security attributes, realtime, no debug enabled
- [ 2907.053018] JFS: nTxBlock = 8192, nTxLock = 65536
- [ 2907.122717] ntfs: driver 2.1.32 [Flags: R/O MODULE].
- [ 2907.210089] QNX4 filesystem 0.2.3 registered.
- [ 2907.345154] raid6: sse2x1 gen() 1151 MB/s
- [ 2907.413158] raid6: sse2x1 xor() 1221 MB/s
- [ 2907.481185] raid6: sse2x2 gen() 1529 MB/s
- [ 2907.549216] raid6: sse2x2 xor() 1332 MB/s
- [ 2907.617257] raid6: sse2x4 gen() 2281 MB/s
- [ 2907.685305] raid6: sse2x4 xor() 1392 MB/s
- [ 2907.685308] raid6: using algorithm sse2x4 gen() 2281 MB/s
- [ 2907.685311] raid6: .... xor() 1392 MB/s, rmw enabled
- [ 2907.685314] raid6: using ssse3x2 recovery algorithm
- [ 2907.721449] xor: measuring software checksum speed
- [ 2907.761340] prefetch64-sse: 3489.000 MB/sec
- [ 2907.801361] generic_sse: 3264.000 MB/sec
- [ 2907.801365] xor: using function: prefetch64-sse (3489.000 MB/sec)
- [ 2907.886030] Btrfs loaded
- [ 2908.346409] EXT4-fs (sda2): unable to read superblock
- [ 2908.359786] EXT4-fs (sda2): unable to read superblock
- [ 2908.365837] EXT4-fs (sda2): unable to read superblock
- [ 2908.371542] FAT-fs (sda2): bogus number of reserved sectors
- [ 2908.371557] FAT-fs (sda2): Can't find a valid FAT filesystem
- [ 2908.386375] XFS (sda2): Invalid superblock magic number
- [ 2908.395952] FAT-fs (sda2): bogus number of reserved sectors
- [ 2908.395965] FAT-fs (sda2): Can't find a valid FAT filesystem
- [ 2908.409204] MINIX-fs: unable to read superblock
- [ 2908.436207] attempt to access beyond end of device
- [ 2908.436220] sda2: rw=16, want=3, limit=2
- [ 2908.436227] hfsplus: unable to find HFS+ superblock
- [ 2908.442454] qnx4: no qnx4 filesystem (no root dir).
- [ 2908.447103] ufs: You didn't specify the type of your ufs filesystem
- mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
- >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
- [ 2908.456029] hfs: can't find a HFS filesystem on dev sda2
- [ 2915.619159] EXT4-fs (sda2): unable to read superblock
- [ 2915.623766] EXT4-fs (sda2): unable to read superblock
- [ 2915.628381] EXT4-fs (sda2): unable to read superblock
- [ 2915.633506] FAT-fs (sda2): bogus number of reserved sectors
- [ 2915.633520] FAT-fs (sda2): Can't find a valid FAT filesystem
- [ 2915.648331] XFS (sda2): Invalid superblock magic number
- [ 2915.656955] FAT-fs (sda2): bogus number of reserved sectors
- [ 2915.656975] FAT-fs (sda2): Can't find a valid FAT filesystem
- [ 2915.670290] MINIX-fs: unable to read superblock
- [ 2915.676195] attempt to access beyond end of device
- [ 2915.676212] sda2: rw=16, want=3, limit=2
- [ 2915.676222] hfsplus: unable to find HFS+ superblock
- [ 2915.681753] qnx4: no qnx4 filesystem (no root dir).
- [ 2915.686708] ufs: You didn't specify the type of your ufs filesystem
- mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
- >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
- [ 2915.695854] hfs: can't find a HFS filesystem on dev sda2
- [ 6729.510958] perf interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
- [ 6974.477250] r820t 3-001a: r820t_read: i2c rd failed=-32 reg=00 len=2: c1 30
- [ 6975.076902] r820t 3-001a: r820t_read: i2c rd failed=-32 reg=00 len=2: c1 88
- [ 6975.076991] usb 7-2: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
- [ 7022.514455] rtl2832 2-0010: i2c reg read failed -32
- [ 7022.517187] rtl2832 2-0010: i2c reg read failed -32
- [ 7022.517206] r820t 3-001a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83
- [ 7022.517473] usb 7-2: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)
- [ 7022.520103] rtl2832 2-0010: i2c reg read failed -32
- [ 7022.522891] rtl2832 2-0010: i2c reg read failed -32
- [ 7149.441174] rtl2832 2-0010: i2c reg read failed -32
- [ 7149.443918] rtl2832 2-0010: i2c reg read failed -32
- [ 7149.443972] r820t 3-001a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83
- [ 7149.451532] rtl2832 2-0010: i2c reg read failed -32
- [ 7263.908718] rtl2832 2-0010: i2c reg read failed -32
- [ 7263.908749] r820t 3-001a: r820t_write: i2c wr failed=-32 reg=0c len=1: f0
- [ 7263.911368] rtl2832 2-0010: i2c reg read failed -32
- [ 7263.914964] rtl2832 2-0010: i2c reg read failed -32
- [ 7266.928382] rtl2832 2-0010: i2c reg read failed -32
- [ 7266.928412] r820t 3-001a: r820t_read: i2c rd failed=-32 reg=00 len=4: f0 88 8e f9
- [ 7266.932741] rtl2832 2-0010: i2c reg read failed -32
- [ 7267.935512] rtl2832 2-0010: i2c reg read failed -32
- [ 7267.935543] r820t 3-001a: r820t_read: i2c rd failed=-32 reg=00 len=4: f0 88 8e f9
- [ 7267.941469] rtl2832 2-0010: i2c reg read failed -32
- [email protected]:/home/kodi/workspace# fdisk /dev/sda
- Welcome to fdisk (util-linux 2.25.2).
- Changes will remain in memory only, until you decide to write them.
- Be careful before using the write command.
- Polecenie (m wyświetla pomoc): p
- Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 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
- Disklabel type: dos
- Disk identifier: 0xb40aa0c3
- Device Boot Start End Sectors Size Id Type
- /dev/sda1 * 2048 58511359 58509312 27,9G 83 Linux
- /dev/sda2 1950423038 1953523711 3100674 1,5G 5 Extended
- /dev/sda3 58511360 1950420991 1891909632 902,1G 83 Linux
- /dev/sda5 1950423040 1953523711 3100672 1,5G 82 Linux swap / Solaris
- Partition table entries are not in disk order.
- Polecenie (m wyświetla pomoc): q
advertising
Update the Post
Either update this post and resubmit it with changes, or make a new post.
You may also comment on this post.
Please note that information posted here will not expire by default. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.